Hi Danielo

> Recently I started to use the Node.js edition of tiddlywiki. I find
extremely useful having the tiddlers in separate files rather than in a
single standalone one.

Great, glad you've been able to make it all work.

Your questions all seem to relate to the scenario of working on an offline
snapshot of a client-server wiki, and subsequently synchronising changes.
It's not a use case that is particularly well supported at the moment, but
the intention is to fully support it.

> BUT, I have a couple of doubts that I want to resolve.

>
> Firs of all: How can I get an offline version of my wiki? I mean, a real
> standalone version. The instructions here
> <http://tiddlywiki.com/#How%20to%20build%20a%20TiddlyWiki5%20from%20individual%20tiddlers:%5B%5BHow%20to%20build%20a%20TiddlyWiki5%20from%20individual%20tiddlers%5D%5D>
>  describes
> how to do something similar.
>

If you want to work on the same wiki content as both a standalone wiki and
a client-server wiki, then the best approach is to use two different wikis,
as you see with tw5.com and tw5.com-server in the TW5 repo.

The idea is to keep your content in a wiki that contains the correct
plugins for standalone use, and then create a separate wiki for
client-server use that includes it, using the "includeWikis" property of
the tiddlywiki.info file. See:

http://tiddlywiki.com/#TiddlyWikiFolders

BUT all the server menus and plugins are included. I want to get rid of
> those. I noticed there is a button to get an offline version on the server
> tab menu. That's exactly what I want, but from command line. I tried this
> with no luck, I just get an empty file:
>
> tiddlywiki tiddlyTest/ --rendertiddler $:/editions/server/download-offline
> test1.html text/plain
>

The following works OK for me:

tiddlywiki editions/tw5.com-server/  --rendertiddler
$:/editions/server/download-offline offline.html text/plain

I'd expect a blank file if the tiddler
"$:/editions/server/download-offline" were missing, as would happen if you
attempted this command with a wiki that doesn't include the
tiddlywebadaptor plugin.


> 2. If I import a wiki file to the node version for the first time
> everything works fine. So far so good. But If I edit some of the imported
> tiddlers in the node.js version and then I import again the same file my
> changes are overwritten. This makes no sense to me. One would expect to
> import only the newest version of each tiddler. Is there a way to fix this?
> With this you can carry you wiki in a Usb stick and import it automatically
> when you arrive home without any worry of get overwritten information.
>

It would be useful to be able to have an option for the `--load` command to
only import newer tiddlers - perhaps your first pull request for the
Node.js edition?


> 3. Is possible to tell the core to export a new offline snapshot every
> time a new tiddler is created?
>

I guess you mean each time a tiddler is modified? Anyhow, no, that isn't
directly supported at the moment, although it would be straightforward to
write a module to do it. Writing the offline snapshot is a time-consuming
operation; you'd probably want to have some throttling so that the snapshot
generation only occurs every 60 seconds (say).

Best wishes

Jeremy


>
> Thank you all!
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/tiddlywiki.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jeremy Ruston
mailto:[email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Reply via email to