Publish Tiddlers for collection by other tiddlyWiki's

[Anthony Muscio]

Good people,

I continue to be transfixed by tiddleywiki and have grand plans, and
lots's of sophisticated features already in a GTD for my self, I hope
someday to publish it.

I am very keen to build something very powerful and I cant quite find
the tools, though have come close. First I will state what detail I am
currently trying to overcome, then I will describe why, so it may help
you understand where I am coming from. If it works I will tell you all
my grand plan.

I want a TiddlyWiki, be it on a server or on a shared file system to
allow the owner of the AliceWiki to add various content. Then when the
AliceWiki is saved, dump the "rendered content" of selected tiddlers
to files (possibly html). These files if consistently named can then
be displayed within another TiddlyWiki BobWiki. The user of the source
AliceWiki should not undertake any action different to a normal user
of a tiddlyWiki. Tiddlers could have tags such includeDump and
ExcludeDump or another tiddler could contain the list of tiddlers to
dump, perhaps as found in a foreachtiddler macro (As rendered).

Given my experience with the Archive, Snapshot rss features/plugins it
seems as if the work has been done but not quite meeting these
requirements. Archive saves the tiddlers automatically but not in a
rendered form, snapshot saves the rendered output, but requires
interaction (or when using the macro includes itself in the output),
rssGenerate dumps the whole lot and in an unrendered form.

It needs a guru to resolve it.

If the output was purely the rendered form of a specifically tagged
tiddler, named from the permalink it would be great, If it also
contained the tags at the time it was rendered even better. The
BobWiki will have a view into the AliceWiki (only via the external
file) as if it were a live tiddler, but based on the data last changed
in the ALiceWiki. If the BobWiki could import the rendered data and
retain it, until it can collect an update, it could be "checked out"
like on tiddlyspot as a local file, used and modified then returned
where it now receives the updated tiddlers from AliceWiki. This can of
course work both ways from the second to the first.

One final feature would be allow one tiddlywiki to trawl a file
subfolder below anothers to find any number of "rendered" or
optionally unrendered tiddlers to include as external tiddlers.

Why would I do this ?
It seams to me that with the above we can get the best of both the
online and portable nature of tiddlyWiki, It would allow us to create
Template TiddlyWiki's you could hand around, which each participate in
a loosely coupled network database, can be taken off line for
reference purposes, or checked out when working from home (offline) on
the tiddlywiki content. The relationships will be many to many and
integrity guaranteed at a point in time for each participating wiki
where the come back to the shared file system or can contact the
server.

I Think using RSS and XML to hold the data is the best way, and
keeping it compatible with RSS wise, however our wiki needs to retain
the imported tiddlers and a version or date check. It may also be
possible to allow links to be included as longs as they contain the
absolute path wikifilename/#tiddler or tiddlerfilename (if a DUMPed
tiddler).

I hope I have been clear and not wasted you time, I hope you can see
my vision which is in the vain of tiddlywiki big things from small
carefully defined components.

Thanks allot Tony

[RichShumaker]

I am looking into something similar.
The two directions I have been pointed are
RippleRap
and RSSAdaptor
From FND to me to you
* RippleRap's SharedNotesPlugin:
http://tinyurl.com/5o3vzb
(http://svn.tiddlywiki.org/Trunk/contributors/PaulDowney/plugins/
Share...)
* RSS adaptor:
http://tinyurl.com/5erjah
(http://svn.tiddlywiki.org/Trunk/contributors/JonathanLister/
adaptors/...)

Also TiddlyWikiWeb is coming out in the future as well. This may have
some or all of the features you are looking for.
I am an end user or i would give you some more information. As I get
more I will post it up.
Rich Shumaker

[BenTremblay]

On Jun 25, 7:28 am, Anthony Muscio <Anthony.Mus...@gmail.com> wrote:
> [...]

>
> I want a TiddlyWiki, be it on a server or on a shared file system to
> allow the owner of the AliceWiki to add various content. Then when the
> AliceWiki is saved, dump the "rendered content" of selected tiddlers
> to files (possibly html). These files if consistently named can then
> be displayed within another TiddlyWiki BobWiki. The user of the source
> AliceWiki should not undertake any action different to a normal user
> of a tiddlyWiki. Tiddlers could have tags such includeDump and
> ExcludeDump or another tiddler could contain the list of tiddlers to
> dump, perhaps as found in a foreachtiddler macro (As rendered).

Without pretending to reply to the material of your post, I think you
and I are on the same page here.

Just yesterday (I had missed this post) I created "Cordon Blue"
http://groups.google.com/group/TiddlyWikiDev/browse_thread/thread/6562d68583b31eb7

The idea is a central repository for Tiddlers / Plugins that would
allow custom builds.

==
"A repository where TWs could be built from scratch using the groups
aggregated resources." [I've found that Import often fails on Tws that
have some very fine Plugins]

"For e.g. [having saved TWs that are populated by Plugins I want; the
editor on http://www.giffmex.org/webviewtwexample.html is a case in
point] I upload the empty.html's that I've collected.
Those go into a directory and get ginsu'd.
A menu is generated.
I select from that collection and the chimera is produced [using Cook
in the background?] for me to download. "
==

If we're on different pages, then that's fine.
If we're on the same page, maybe we can start a topic on Dev Wiki.

cheers
--bentrem

[Marc J. Cawood]

Hi Tony
I'm not clear why you would want 2 TW files (Alice and Bob) to share
_rendered_ tiddler content.
If you have AliceWiki.html and BobWiki.html in the same folder they
both have access to _unrendered_ tiddler content in the folder
archive/. That way you can share tiddlers with the ArchivePlugin.
The PublishMacro allows you to export tiddlers rendered or unrendered
in any format but there is no functionality for importing them again
because of the problems in getting back to WikiText from HTML.
Can you provide examples, with WikiText of what you want to achive?
Cheers
Marc

[Anthony Muscio]

Marc,

Alice and bob may share a file folder when they are together and
online but when one or both is taken away on a usb drive I want them
to take a published copy of selected tiddlers from each other. For
example alices tiddlyWiki may have a project tiddler which summarises
all the contacts related to the project including there phone numbers.
this project tiddler was constructed from variouse macros, and
tiddlers found only in Alice. If Alice can publish this rendered
project tiddler, and Bob can include it in bobs wiki, then when bob
goes to the customers premises he can look up the Alice Project
tiddler (rendered version) and find out the contact for the Project
manger (for example). bob does not own this infomation, cant change it
but he can look it up when offline.

Does that example help ?

I am thinking I could use the IncludePlugin for this but it is still
not clear to me.

In a way I want to save externaly a tiddler, with it's fields, its
tags it's tiddler name (still as a tiddler), however it's content is
rendered rather than the source. Bob can elect to import this
(rendered tiddler, it would look as if it would in Alice without all
the dependancies.

One could Save the tiddler like the archive plugin but with the
rendered HTML inside it, thats why I have asked you because I think
you already know everything that would be required to do so.

Perhaps you would call such a plugin archiverenderedtiddlersPlugin.

Finally ideally the modified date would be valid in the archive
tiddler such that bob's include would only bring in an updated tiddler
from alice.

Thanks for taking the time to consider this.

tony