I've now up and running a --makeplugin command module.
My setup is as follows:
- src/ ... contains the unified tiddler storage wiki; contains empty(!)
tiddlywiki.info.
- tiddlers/ ... used by the (hierarchical) fs adapter
- editions/
- develop/ ... only contains tiddlywiki.info setup; pulls in the
hierarchical fs adapter and otherwise references the src/ tiddlywiki.
- package/ ... does not pull in any fs adapter and is used solely for
packaging; again, it references the src/ tiddlywiki. Will probably use it
twofold: for packaging and releasing an example edition demonstrating the
plugin.
So I only need a simple (shell) script to package and release. I can do
development both online and offline as I need to do depending on situation.
Syncronizing with the repo is clean and simple as there is only exactly one
repo tiddler tree mirroring the TW5 tiddler contents. No need to remember
different locations for my tiddlers depending on whether they belong into
the plugin or are demonstration and external documentation.
If that is considered swimming against the flow, I'm happy with it.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.
