> I see. What about storing some extra data in the file? I mean, the > description of the links graph? It would make the file bigger for > sure; yet names of tiddlers can be replaced with their numbers in the > storeArea in a saved file and calculated on startup.
Persisting the extra data in the file could certainly be done, but I've found arrangements like that to be too brittle: it's too easy for the metadata and the data to fall out of sync with one another. > I have one more question. I'm writing quite big and consistent manual > for TW (along with many thoughts on interface, styling, navigation > etc) but I'm afraid it would be of little use if TW5 would be very > different from TW2. Can you comment this somehow? (I'm writing the > thing in russian initially, so I can send it right now; also, I need > to think of the multilangual approach for it) I'd always favour maintaining tight standards of backwards compatbility as we move to successive versions of TiddlyWiki, and I'd hope that we could add and extend features in a way that encourages people to upgrade to newer versions. > Also, the same thing with development: I was planning to study the dev > part of TW in the next term, but if core changes considerably, would > it good enough to start with TW2? Definitely start with TW2. Any subsequent developments to TiddlyWiki will always be strongly related to the current code base. > And one more note about TW5: as for now, the approach looks very good > for handheld - I mean the buttons etc, this is even close to WYSIWYG > possibilities of Word Mobile (and "office", not plain text processors > are of big value for mobile, esp. for older devices and OSs) - keep > this in mind. But I haven't tested it yet (and even don't know if TW5 > is available for download), so I can't say anything about navigation > (while usual tree of folders serves quite ok). Also, speaking about > mobile, I'll notice some subtleties with saving. For example after > some seacrch about [1] I've got a comment from a friend of mine who > said that it can be the Opera which doesn't support Java because it is > oriented on on-line work through their servers. Each page you open is > downloaded by them, processed somehow and compressed and sent to you - > and this practice seems to be popular (as I understand, SkyFire also > works so). I'll probably report on this when I find the solution. > Ofcourse, let me know if this is already known and solved. That sounds like Opera Mobile. Confusingly, Opera have two different mobile browsers: http://www.opera.com/mobile/ Anyhow, in the mobile space, there is no good cross-platform solution for TiddlyWiki to save changes. I think that the best bet for many platforms is to use apps - little wrapper apps that encapsulate the stock TiddlyWiki HTML file and extend it with native saving capabilities. On the iPad and now the iPhone there is TWMobile and TWEdit: http://itunes.apple.com/gb/app/twmobile/id381945222?mt=8 http://itunes.apple.com/gb/app/twedit/id409607956?mt=8 And for Android phones there is AndTidWiki: http://mgsimon.de/android/andtidwiki/ Best wishes Jeremy > [1] > https://groups.google.com/group/tiddlywiki/browse_thread/thread/d405d4cd6c559cf3 > > -- > 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. > > -- Jeremy Ruston mailto:[email protected] http://www.tiddlywiki.com -- 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.
