> 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.
> In stead
> I've tried to focus on making it more accessible and familiar.
Yes, I think your vision comes across very clearly.
> 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.
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.
> 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.
In TiddlyWeb we use JSON, to some extent because of issues with
parsing XML on some browsers.
> 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.
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.
> 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?
Thanks very much. I've added those two questions to the space.
> 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.
The convention is that a public SiteInfo tiddler gives information
about a space, which might include the author, owner or responsible
parties. The approach so far has been not to expose the actual space
owners by default. By design, anyone can add anyone else to a space of
which they are a member - there is no confirmation step by the person
being added. This means that you can add me to a space called
"robbingbanks"; we wanted to avoid the situation where it might look
like someone was supporting or contributing a space when they have
merely been added as a member.
> * There is no obvious channel for feedback (comments, talk page, quick-
> polls or other).
Indeed. The social features are fairly opaque. They have been designed
to address the problems that can occur with open comments and feedback
in large groups, and so are somewhat experimental. The central idea is
that the members of a space are sovereign; only they can modify the
content of a space. There is intentionally no facility for visitors to
add or modify content; if people want to join the discussion, they
have to create their own space, rather than borrowing from someone
else. I modify my stuff, you modify yours. If we trust one another
enough, we can become members of the same space and collaborate
freely. In situations where you want to be able to collaborate across
a broad community where you can't have full trust in everyone all the
time, then TiddlySpace's social features let you do so without having
to open up your space as a platform for other people to speak through.
> * There is no apparant way to make a private tiddler public.
In edit mode there are radio buttons under the tiddler title that
allow you to switch the tiddler from private to 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.
I'll let Chris comment, but I believe that that would be a matter of
using a different HTML template in TiddlyWeb. There is some work
underway to externalise TiddlyWiki's JavaScript for TiddlySpace, which
may be enough for your purposes.
> 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!
Yes, the message area is being used very poorly. I think we can now
get rid of the confirmation messages, because we now have overlay
icons to indicate problems saving.
> 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.
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.
> 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.
It is a battle for people's attention but Giewiki is a nicely executed
thing, with broad appeal. I'm sure interest will continue to build as
you keep working on it.
Best wishes
Jeremy
> 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.
>
>
--
Jeremy Ruston
mailto:[email protected]
http://www.tiddlywiki.com
--
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.
