Thanks Jeremy, thanks Eric > to create skinny wrappers around the platform's native webview control
I wonder what the "wrapper" means. I mean, if I decide to write this by myself, I have no idea where to look and what does this do (with which libraries interacts etc); neither any idea of what native webview control is and wether this thing is present in legacy mobile platforms like Windows Mobile 5 in my case. > FireFox is NOT Webkit-based Oops. Now I know this :) probably I misread something in Wikipedia. > then transcribed back into HTML syntax when the file is saved As I understand this can be handled by adding a "semi-save" function which would write the state from the store object into DOM, but as long > Firefox is the only browser [I know] that uses a snapshot of the current DOM > for file/save is true this is of no use. And > character-set conversions, discarding of comments, collapsing of whitespace, > etc makes also some problems, especially character-set conversions. One more question: what do you know guys about the Local Storage? I mean, should it be hidden by browser from manual access? Developers say that Zetakey implements Local Storage so I wonder if the work on handheld can be done in the following manner: I work with TW, and the alternations are kept in Local Storage. Than I copy my Local Storage content from handheld to computer, apply some saving engine there, et voila - here I have a TiddlyWiki, like as if I saved changes on the mobile device. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
