Hi, short reply on Chris's message inline
On Nov 18, 2:21 pm, [email protected] wrote: > On Fri, 18 Nov 2011, tiddlygrp wrote: > > Additionally I propose to add an optional journal or history field > > analogous to Ward's federated wiki ( > >https://github.com/WardCunningham/Smallest-Federated-Wiki/wiki/Story-... > > ). > > If you put the journal in the tiddler, then when trying to reconcile > a lot of forks you need to merge up the journal. My proposal is at first just to reserve the field name and keep the use optional. Then we can start experimenting with tiddler history. I think the history should be kept in the tiddler primarily. Because the tiddlers can be forked etc., it will be like a DVCS. This needs development of a good ui to actually use the history and development of the code. This is non trivial and I would not burden all uses of tw with it. Maybe this can be best done with a plugin and/or serverside. But the important thing is there is a standard field for it. Obviously we also need to think about dropping part of the history (maybe through server persistence), otherwise tiddlers can get too large. > > That's non-trivial. And what does it get? > It get's us distributed authoring of tiddlers, e.g. distributed building of documentation. We can have distributed todo lists. Imagine one of MonkeyPirateTiddlyWiki, mGSD,D-Cubed, TeamTasks, TiddlyPackingList, tbGTD used by a team, online and offline and optionally distributed by email. Imagine mix-match-patch writing of stories. -- 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.
