Is there a possibility to "label" tiddlers revisions

9 views
Skip to first unread message

PMario

unread,
Jun 28, 2010, 4:21:17 AM6/28/10
to TiddlyWeb
Hi,
It would be great to mark/label tiddler revisions and/or the whole
bag. Eg: with the TeamWork [1][2] TW I manually saved xxx002,
xxx003 ... to keep different states of an evolving plugin. It would be
easier to mark and recall different revisions.

At the moment, there is a diff, which shows the difference between 2
revisions. I would like to have a side by side view, similar to
ListNav_vs_testPlugin [3].

regards Mario
PS: Is there an existing installation/experiment to git a whole
tiddlyWeb instance?

[1] http://hoster.peermore.com/recipes/TeamWork/tiddlers.wiki#ColorfulToolbarPlugin
[2] http://hoster.peermore.com/recipes/TeamWork/tiddlers.wiki#testPlugin
[3] http://hoster.peermore.com/recipes/TeamWork/tiddlers.wiki#ListNav_vs_testPlugin

FND

unread,
Jun 28, 2010, 4:53:52 AM6/28/10
to tidd...@googlegroups.com
> It would be great to mark/label tiddler revisions

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.

Jeremy Ruston

unread,
Jun 28, 2010, 5:23:42 AM6/28/10
to tidd...@googlegroups.com, tidd...@googlegroups.com
As Fred notes, it's kind of cool that things like the adoption of a convention for using extended fields to store revision notes doesn't need direct core support in either TiddlyWeb or TiddlyWiki. In this case, I also agree that it's very useful to be able to annotate the revision history.

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.
>

PMario

unread,
Jun 28, 2010, 1:03:19 PM6/28/10
to TiddlyWeb
Hi Fred,
On Jun 28, 10:53 am, FND <F...@gmx.net> wrote:
> > It would be great to mark/label tiddler revisions
>
> 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%2F...
>
> (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.
Thanks for your info.

I had to adjust EditTemplate, and the RevisionsCommandPlugin [1] (2
lines of code) and some description. Have a look at the plugins
revisions. I think the information that is now provided, is much
better, than to know, that you have eg: 35 revisions starting from
2009 till now.

I am not happy with the EditTemplate. I think, I'll hijack the edit
and save commands instead.

regards mario
[1] http://hoster.peermore.com/recipes/TeamWork/tiddlers.wiki#RevisionsCommandPlugin

FND

unread,
Jun 28, 2010, 1:44:59 PM6/28/10
to tidd...@googlegroups.com
> I had to adjust EditTemplate, and the RevisionsCommandPlugin [1] (2
> lines of code) and some description.

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.

PMario

unread,
Jun 28, 2010, 5:34:34 PM6/28/10
to TiddlyWeb

On Jun 28, 7:44 pm, FND <F...@gmx.net> wrote:
> > I had to adjust EditTemplate, and the RevisionsCommandPlugin [1] (2
> > lines of code) and some description.
>
> 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);
>
> //}}}
cool. this is for the accurate user, who is willing to write comments
on his own.

I was thinking about a prompt [1] :) But there is still the
possibility to hit [enter] or [cancel] which writes an empty comment.

[1] http://hoster.peermore.com/recipes/TeamWork/tiddlers.wiki#RevisionsCommandEditSaveHj
-m
Reply all
Reply to author
Forward
0 new messages