While I am generally a proponent of edit summaries, this has not been
implemented in TiddlyWebWiki because it didn't seem to fit the usual
TiddlyWiki workflow or mindset.
However, it should be fairly simple to provide an additional input field
in the EditTemplate, storing its value in a custom field. An overview of
revisions could display the message stored in this field if available.
An optional plugin could provide this extended functionality without
raising any compatibility issues.
> mark/label [...] the whole bag
I'm afraid I don't know what you mean by that.
Bags already have descriptions, is this what you're after?
> At the moment, there is a diff, which shows the difference between 2
> revisions. I would like to have a side by side view
Improved diff views would be great, but it's not currently a priority.
FWIW, the TiddlyWeb differ plugin provides a side-by-side view as static
HTML page:
http://fnd.tiddlyspace.com/diff?rev1=bags%2Ffnd_public%2Ftaskboard%2F6&rev2=bags%2Ffnd_public%2Ftaskboard%2F7&format=horizontal
(This is linked from comparison tiddlers in more recent versions of
TiddlyWebWiki - thought we're not quite sure whether that's a really
good idea.)
> Is there an existing installation/experiment to git a whole
> tiddlyWeb instance?
You can already do that (provided you're using the file-based text
store) - though I'm not sure what your expectations are.
This might be of interest:
http://trac.tiddlywiki.org/ticket/815
-- F.
Cheers
Jerm
--
http://jermolene.com
http://tiddlywiki.com
http://osmosoft.com
> --
> You received this message because you are subscribed to the Google Groups "TiddlyWeb" group.
> To post to this group, send email to tidd...@googlegroups.com.
> To unsubscribe from this group, send email to tiddlyweb+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/tiddlyweb?hl=en.
>
That's looking pretty good!
If I find the time, I'll see about refactoring the
RevisionsCommandPlugin to allow for easier extensibility so you don't
have to override it.
> I am not happy with the EditTemplate. I think, I'll hijack the edit
> and save commands instead.
You might do something like this:
//{{{
(function($) {
var _handler = config.macros.edit.handler;
config.macros.edit.handler = function(place, macroName, params,
wikifier, paramString, tiddler) {
if(params[0] == "text") {
$('<input type="text" edit="revsummary" />').appendTo(place);
}
return _handler.apply(this, arguments);
};
})(jQuery);
//}}}
(lacking an label element for this new input field, only because that
would go beyond a minimal sample, StyleSheet etc. - also, I called the
field "revsummary" here, for no particular reason)
-- F.