On Mar 10, 12:45 pm, Jeremy Ruston <[email protected]> wrote: > > Absolutely. You may find, I admit, that I haven't been as dilligent in > > keeping strings separate, avoiding namespace pollution, etc. And > > obviously not bothered to preserve the codebase untouched. > > I wondered about that; it would certainly be cool if we could engineer > things so that giewiki is getting the latest tiddlywiki core.
It //would// be nice, but I figured that tiddlywiki was approaching a sort-of steady-state where important fixes and enhancements could be ported over manually. I made it a fork in order to peel away all that I didn't need and make room for what I wanted to add. > I'm not such a fan of local storage for storing user data. I feel more > confident if I can see my data in a file, rather than hidden away in > an invisible cache that is tied to one browser. Your choice, but my creed is that you should keep your content in the cloud and only take it offline when you have to. It has tremendous advantages when you work on several different devices, local or remote, more or less at the same time. > So that would mean that applying a translation would be a build step? > That would constrain all users of a server to see the same language, > I'm not sure if that's an important limitation. Well, the content would typically be kept in one language anyway. I'm not a fan of sites that try to offer partial translations. If you want to offer multiple languages versions, install them separately on app engine. > > As for collaborative effords, I think it might be a good idea to try > > and create a book, in contrast to this rather nerdy forum, perhaps in > > the forum of the still very > > half-heartedhttp://en.wikibooks.org/wiki/Tiddlywiki > > -particularly now that tw.org is moving away from the familiar > > mediawiki form. > > You're proposing a collaborative effort to write a book about > TiddlyWiki? Interesting idea! I'm rather drawn towards eating my own > dogfood, and using TiddlyWiki rather than a conventional book, but > it's definitely an interesting idea. Rather than see someone else write the book for profit, we should write it for free. I'm not sure if it should lean towards the evangelical or the handbook - that'll mostly be up to those who volunteer. I also would be tempted to write in my own private environment, but once it's perfectly clear what a page or chapter is about, I believe wikibooks would be an excellent medium. It certainly has the advantage that professional-looking output can be generated by the built-in PDF engine - ready to print and pass around. Happy tiddling, Poul -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki?hl=en.
