Thank you. An application from a commenter here is to create some sort of a reverse text recognition: the input is a text file, and the output is an appended page on a notebook with the text converted into pen strokes of a given characters set (an ASCII table of characters in a notebook page format). So the script reads the text, then for each character retrieves its ASCII code, then pulls the corresponding pens strokes from the characters set and keep appending the pen strokes, before adding the result to a new page. And you guessed it: using keyword settings :) Easier said than done, but I think I have all the information needed.
I think I now have enough insights of the pen strokes to test building from scratch a .note file from a string. I need first to create an inventory of pen strokes for all characters of a given font, color and size Then combine the relevant strokes to create the strokes for the string Should be interesting and it opens the door to all sorts of applications. Notes would be able to include both handwritten and replicated typed words (or symbols, shapes) Stay tune!
Ever handwriting quotes from scripture I contacted Supernote to ask if a pdf version of the Bible could be _'recognised'_ as *pen strokes,* because if it could... I could then copy verses as *pen-strokes* just as I sometimes do within my own notes, then paste it in another note. Sure, it would look off seeing what looked like _'typed text'_ among my notes [but was typed text converted into pen-strokes] but boy, would it save allot of time handwriting verses out. I guess there might be a _'copyright issue',_ though I'm not sure as it isn't actually text but would easily be converted into editable text with Supernote's convert-to-text tool. So, currently, i have the whole of the bible on my Supernote in PDF form but am forced to handwrite any desired verse into my notes when needed. I hope that makes sense, I just wondered if I was asking supernote to add a feature that was not possible or was not legal. They are a small team dealing with multiple requests so I'm not at all phased that they aren't considering my request.
Hello there, thank you for your comment and application suggestion. For now, I can modify existing strokes or simulate pen strokes. Simulating pen strokes using a template, in your case a picture of verses from the Bible, is very slow and would require to have the Supernote open on a blank page. But technically speaking, you are right: even without having full transparency on the Supernote format, one could compile for instance the pen strokes for a given font of all the letters of the alphabet. The script would then need to combine these letters into words, while ensuring that they fit within a page frame. I anticipate this would be much faster than simulation. It's a very interesting idea and I may check the feasibility. What font do you think would be good?
@@mujmmb I 'assume' Supernote actually records something at the moment of writing, whereas I'm asking it to in someway _'trace typed text'_ and then record it was hand-written text. The difference them might be better understood if I... A) Was able to brilliantly copy, to the pixel a verse of typed text then... B) Imported the typed text I had copied so magnificently from. Supernote would have recorded the pen-strokes of [A], and I would be able to copy and paste it into any note whenever I needed that verse, but my Supernote would have no data on [B]. It would have to trace [B] in some way... and although my Mac converts text in images to usable text in seconds, it might be asking allot of a Supernote to trace typed text so that it can then be copied and pasted directly into a Note as with [A]. Boox does it, but text copied from documents has to be pasted into a 'text box' within a note, which isn't the same and is fidgety and full of issues. I only asked the Supernote team to consider it as I assume I'm not the only one who is constantly hand writing text copied from documents I already have on the Supernote. Yes I can link to them, but if you are building an argument... jumping to links can be distracting if not impossible once you've exported the document as a PDF with live links. Anyway, thank you for your reply and for taking the time to consider the issue... appreciated.
@@karlmunford7000 , thank you for the feedback and use-case mention. Please take a look at the following screen cast, that shows a full import from text to pen strokes (in this case I used my own "typed" characters, but will probably implement with a font like Arial or Helvetica. Should come to PySN in the near future for everybody to use: app.screencast.com/UxqdvLhoK45fx?conversation=FLfDBYsiuscQIDOmggYhzf&tab=Details
@@mujmmb Gotcha! I was sitting there scratching my head. I'm tracking now! That was pretty clever! Am I correct in assuming that you also worked in a double entendre with a Lean Six Sigma reference there with the "pai-sən?" (The Poisson Distribution).
@@wheelch0ck Glad you liked the name! The pun was mainly intended as a play on 'Python' and 'SN' for Supernote, leading to 'paɪ-sən.' I didn't initially have the Poisson distribution or Six Sigma in mind, but it's interesting that you made that connection! Thanks for the thoughtful interpretation-it's always fun to see how different layers of meaning can emerge
Congratulations with this achievement! I'll be following all applications (and trying to get some ideas for that this could be used for)
Thank you.
An application from a commenter here is to create some sort of a reverse text recognition: the input is a text file, and the output is an appended page on a notebook with the text converted into pen strokes of a given characters set (an ASCII table of characters in a notebook page format). So the script reads the text, then for each character retrieves its ASCII code, then pulls the corresponding pens strokes from the characters set and keep appending the pen strokes, before adding the result to a new page. And you guessed it: using keyword settings :)
Easier said than done, but I think I have all the information needed.
I think I now have enough insights of the pen strokes to test building from scratch a .note file from a string.
I need first to create an inventory of pen strokes for all characters of a given font, color and size
Then combine the relevant strokes to create the strokes for the string
Should be interesting and it opens the door to all sorts of applications. Notes would be able to include both handwritten and replicated typed words (or symbols, shapes)
Stay tune!
Ever handwriting quotes from scripture I contacted Supernote to ask if a pdf version of the Bible could be _'recognised'_ as *pen strokes,* because if it could... I could then copy verses as *pen-strokes* just as I sometimes do within my own notes, then paste it in another note. Sure, it would look off seeing what looked like _'typed text'_ among my notes [but was typed text converted into pen-strokes] but boy, would it save allot of time handwriting verses out.
I guess there might be a _'copyright issue',_ though I'm not sure as it isn't actually text but would easily be converted into editable text with Supernote's convert-to-text tool.
So, currently, i have the whole of the bible on my Supernote in PDF form but am forced to handwrite any desired verse into my notes when needed.
I hope that makes sense, I just wondered if I was asking supernote to add a feature that was not possible or was not legal. They are a small team dealing with multiple requests so I'm not at all phased that they aren't considering my request.
Hello there, thank you for your comment and application suggestion.
For now, I can modify existing strokes or simulate pen strokes. Simulating pen strokes using a template, in your case a picture of verses from the Bible, is very slow and would require to have the Supernote open on a blank page.
But technically speaking, you are right: even without having full transparency on the Supernote format, one could compile for instance the pen strokes for a given font of all the letters of the alphabet. The script would then need to combine these letters into words, while ensuring that they fit within a page frame. I anticipate this would be much faster than simulation. It's a very interesting idea and I may check the feasibility. What font do you think would be good?
@@mujmmb I 'assume' Supernote actually records something at the moment of writing, whereas I'm asking it to in someway _'trace typed text'_ and then record it was hand-written text. The difference them might be better understood if I...
A) Was able to brilliantly copy, to the pixel a verse of typed text then...
B) Imported the typed text I had copied so magnificently from.
Supernote would have recorded the pen-strokes of [A], and I would be able to copy and paste it into any note whenever I needed that verse, but my Supernote would have no data on [B]. It would have to trace [B] in some way... and although my Mac converts text in images to usable text in seconds, it might be asking allot of a Supernote to trace typed text so that it can then be copied and pasted directly into a Note as with [A].
Boox does it, but text copied from documents has to be pasted into a 'text box' within a note, which isn't the same and is fidgety and full of issues. I only asked the Supernote team to consider it as I assume I'm not the only one who is constantly hand writing text copied from documents I already have on the Supernote. Yes I can link to them, but if you are building an argument... jumping to links can be distracting if not impossible once you've exported the document as a PDF with live links.
Anyway, thank you for your reply and for taking the time to consider the issue... appreciated.
@@karlmunford7000 , thank you for the feedback and use-case mention. Please take a look at the following screen cast, that shows a full import from text to pen strokes (in this case I used my own "typed" characters, but will probably implement with a font like Arial or Helvetica. Should come to PySN in the near future for everybody to use: app.screencast.com/UxqdvLhoK45fx?conversation=FLfDBYsiuscQIDOmggYhzf&tab=Details
"Pie-son?" Or Python?...
ˈpaɪ-sən/ (Python for SN, pun intended :) )
gitlab.com/mmujynya/pysn-digest
@@mujmmb Gotcha! I was sitting there scratching my head. I'm tracking now! That was pretty clever! Am I correct in assuming that you also worked in a double entendre with a Lean Six Sigma reference there with the "pai-sən?" (The Poisson Distribution).
@@wheelch0ck Glad you liked the name! The pun was mainly intended as a play on 'Python' and 'SN' for Supernote, leading to 'paɪ-sən.' I didn't initially have the Poisson distribution or Six Sigma in mind, but it's interesting that you made that connection! Thanks for the thoughtful interpretation-it's always fun to see how different layers of meaning can emerge