Official Tiddler versioning support - consistency

[Ash]

Are there any plans to make versioning (i.e. a tiddler's change
history) part of core TiddlyWiki.

At the moment there are two incompatible versioning for the two main
server-side TW implementations (TiddlyWeb/TiddlySpace and GieWiki) and
no plain offline TW that support versioning.

If it was made a standard supported part of TW then hopefully
TiddlyWeb & GieWiki would implement it in the new standard manner and
we could export a TiddlySpace wiki, edit it completely offline (i.e.
no need to sync with server), import it into Giewiki and have changes
maintained.

--
Any thought?
Ash

[PMario]

This may be of interest.

http://homepages.kcbbs.gen.nz/tonyg/projects/synchrotron.html
http://hg.opensource.lshift.net/synchrotron/raw-file/default/tiddlywiki/tiddlydvcs.html

If something like this is part of the core, it would make the TW file
just bigger. Plugins work nice for that.

I didn't test it but it looks promising.

-m

[HansBKK]

On Friday, July 1, 2011 5:46:17 PM UTC+7, Ash wrote:

no plain offline TW that support versioning.
 

If you haven't been following the list lately, you might have missed this thread:

https://groups.google.com/d/msg/tiddlywiki/VkSfqHqo1M8/oS8aSFRuhhcJ

including my comment about using regular version control systems to do the job:

https://groups.google.com/d/msg/tiddlywiki/VkSfqHqo1M8/qd2S7Hio6IoJ


I haven't done much research on the existing tools available for import/export of tiddler sets to external files, say generic CSV, but pending Jeremy doing something like this for core, I'd really love in the meantime to see a plugin that allows me to set up a MatchTags-selected tiddler set - "click" they're out in the filesystem, then "click" they're back in, maybe set up a hidden unique-key field for matching on the way back in (if there's nothing like that already in the datastore) since title may change while the tiddlers are out. Or I suppose cleaner to just delete on the way out - I don't think TiddlerTweaker handles booleans?

That sort of thing would open huge possibilities, not only for very flexible version control, but database processing, CMS integration (any Drupal fans out there?). . .

I see TW as an excellent data-entry front-end for gathering and organizing data, and also as a superb distribution/presentation medium - easier integration with the non-Tiddly world would leverage those strengths into a host of new environments. . .

Sorry for waffling on, I just get so excited! 8-)

[Eric Shulman]

> I haven't done much research on the existing tools available for
> import/export of tiddler sets to external files, say generic CSV, but

Both of these plugins can write tiddler data (including custom fields)
to CSV files:

http://www.TiddlyTools.com/#ExportTiddlersPlugin
http://www.TiddlyTools.com/#SaveAsPlugin

...and, both of these plugins can *read* CSV tiddler data:

http://www.TiddlyTools.com/#ImportTiddlersPlugin
http://www.TiddlyTools.com/#LoadTiddlersPlugin

enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios

Help support TiddlyTools:
http://www.TiddlyTools.com/#Donate (paypal)
TiddlyWiki consulting:
http://www.TiddlyTools.com/#ELSDesignStudios
http://www.TiddlyTools.com/#Contact

[PMario]

On 1 Jul., 21:02, HansBKK <hans...@gmail.com> wrote:
> If you haven't been following the list lately, you might have missed this
> thread:

I followed this thread at the beginning. But I just think, TiddlySpace/
TiddlyWeb can handle all of this just fine. Without all the needed
workarounds for Dropbox.

> including my comment about using regular version control systems to do the
> job:
>
> https://groups.google.com/d/msg/tiddlywiki/VkSfqHqo1M8/qd2S7Hio6IoJ

I was thinking about using GIT with the TiddlyWeb text store. But it
turns out, that I don't need the whole history. Just some tiddler
revisions, which will work with plain TiddlyWeb too.

It seems that everyone want's to hack around with local file system.
Export, Import ... But it's all there.
TiddlySpace / TiddlyWeb can handle it just fine.

I created a Hoster=TiddlyWeb publishing workflow, that would let
someone, contribute to my TeamWork [1] place.
See the video [2] if you are interested. Note, that TiddlySpace wasn't
working well at the time the video was done.

-m

[1] http://hoster.peermore.com/recipes/TeamWork/tiddlers.wiki
[2] http://www.youtube.com/watch?v=WzHRHLd7tyk

[PMario]

> ...Note, that TiddlySpace wasn't

> working well at the time the video was done.

I wanted to say. TiddlySpace was alpha or beta at the time the video
was done :)

I really miss the edit button ...
-m

[HansBKK]

I'm enjoying, I'm enjoying! Looks like these are just the ticket - but of course I've got questions. . .

Assuming I'm importing "all" from the {previously exported then externally modified set of tiddlers}, is the process of matching those tiddlers coming back in with the ones left in the TW file based on the title only? IOW if the titles have been modified while outside, would these be seen as new incoming, creating dupes?

In which case I'm thinking I'd need to delete from TW as part of the export workflow. . .  Or can you suggest a way to allow them to remain in both places, possibly modified in both (including titles), but still be recognized as"matching" somehow, leaving the ability to use the "merge" feature on import?

And I take it that while SaveAs does allow for MatchTags boolean selects, LoadTiddlers doesn't - not complaining or requesting, just checking. . .

[Ash]

[Moving discussion over to TiddlyWikiDev]

It would be nice to see the concept of versions built-in to core TW.
In other words, to define a set format. I would suggest referencing
each version by a hash that represents the contents at that time git-
style.

To work on synchrtron looks interesting (although a few years old)
but it seems to assume a merging strategy which is far above what I
was suggesting. I was merely looking for a standard version format for
embedding versions into a TW so that there is some compatibility
between server-side solutions (almost all of which offer versioning).
The server-side specific plugin would still take care of merging and
diffing as each server has their own concept of users.

Is there any way we could settle on a client-side version format?

all the best,
Ash

On Jul 1, 4:10 pm, PMario <pmari...@gmail.com> wrote:
> This may be of interest.
>

> http://homepages.kcbbs.gen.nz/tonyg/projects/synchrotron.htmlhttp://hg.opensource.lshift.net/synchrotron/raw-file/default/tiddlywi...

[Ash Irus]

[Moving discussion over to TiddlyWikiDev properly now that I have joined that group]

On Jul 8, 5:09 pm, Ash <ashiru...@gmail.com> wrote:
> [Moving discussion over to TiddlyWikiDev]
>
> It would be nice to see the concept of versions built-in to core TW.
> In other words, to define a set format. I would suggest referencing
> each version by a hash that represents the contents at that time git-
> style.
>
> To work on  synchrtron looks interesting (although a few years old)
> but it seems to assume a merging strategy which is far above what I
> was suggesting. I was merely looking for a standard version format for
> embedding versions into a TW so that there is some compatibility
> between server-side solutions (almost all of which offer versioning).
> The server-side specific plugin would still take care of merging and
> diffing as each server has their own concept of users.
>
> Is there any way we could settle on a client-side version format?
>
> all the best,
> Ash
>
> On Jul 1, 4:10 pm, PMario <pmari...@gmail.com> wrote:
>
>
>
>
>
>
>
> > This may be of interest.
>

> >http://homepages.kcbbs.gen.nz/tonyg/projects/synchrotron.htmlhttp://h......