Hi Jeremy,
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. In stead
I've tried to focus on making it more accessible and familiar. I only
recently implemented the TW-based offline feature as a sort of short-
term solution, not really intending to worry about merge conflicts,
but handling renamed tiddler identity. Ultimately, I believe the right
approach is to use HTML5 for local storage, for security reasons. My
approach to client-server interface is classic HTTP posts with replies
in XML form. With a list-based mapping of Python methods to
JavaScript. As for translation, my idea which I haven't yet fully
implemented is to put all translatable strings in double-quotes, and
all other strings in single quotes. Then, in theory, you could easily
build a translation table and with a simple utility apply it to the
source code; with the advantage of more compact code.
I only just discovered interview.tiddlyspace.com, and I really like
it. The automatic transclusion idea is beginning to dawn on me.
Anyway, I'd like to suggest a few more questions: How often, in % of
time, do you work offline? How much of your tiddling is personal, how
much is collaborative, and how much is for publishing?
As for TiddlySpace, I do find a couple of features missing though:
* There is no patteren for discovering who the owner(s) of a space is.
* There is no obvious channel for feedback (comments, talk page, quick-
polls or other).
* There is no apparant way to make a private tiddler public.
* It would be nice if you could pull the content out in the familiar
XML structure of Tiddlywiki, but leaving out all the rest. It would
help importing into giewiki, which is handicapped by App Engine's 1MB
limit on HTTP requests.
And finally, the "<tiddlerName> saved succesfully" message looks to me
like an error ("negative") message, at least on a red background. If
the tiddler closes in response to clicking 'done', surely it should be
safe to assume that your edit //was// saved succesfully!
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-hearted http://en.wikibooks.org/wiki/Tiddlywiki
-particularly now that tw.org is moving away from the familiar
mediawiki form.
And finally, thanks to whoever for the link on TW.com - it seems to
have doubled the effective visiblity of giewiki. I must confess, I
haven't exactly been overwhelmed with feedback like you were, but I
take that only as a sign that the competition has toughened.
Cheers,
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.
