To all: thank you very much for the encouraging positive feedback. I'm glad that my idea has not taken (mostly) clear shape and is better to understand.
@PMario: I'll yet need to, erm, *dive* (I almost hate to use that word, but then ... oh well) into the Node.js infrastructure in order to cut off the rough edges. At least you now made me understand why Jeremy's shell scripts use tiddlywiki.js directly instead of relying that the command is present. @Jeremy: There is no online copy yet. Unfortunately, I found a problem in the way my "--build release" configuration works and where I need some help. There is another idea hidden inside my plugin: during release I'm disabling the hierarchicalfilesystem sync adapter and then I pack the plugin. After that, I dump the demo TIddlyWiki. Now, the demo TiddlyWiki is basically the development TW but without any plugin source tiddlers. How do I exclude the source tiddlers from being rendered? I'm basically throwing out all those tiddlers which also have a shadow tiddler which is of same creation and modification data and type. I'm also throwing out my own ThirdFlow plugin itself -- unless it's source code is present. The rationale is that plugin developers usually don't want the ThirdFlow plugin to be released as part of their demo TWs. Yet, I need to release it as part of my demo TW. The problem now is that I'm currently relying on wiki.getShadowSource(). Trouble is, I'm packing the plugin (tiddler) after TW has booted and all (enabled) plugins have been enabled. So TW doesn't notice that there is change in the plugin. My [is[shadowinsync]] is universal in that it should work both when I'm releasing the ThirdFlow demo TW as well as plugin users releasing their plugin demo TWs. In order to work correctly and without further configuration of the template tiddlers shadowinsync and thus TW would need accurately updated shadow information. At first, I simply called $tw.wikireadPluginInfo() (v1.0.0 release). In this situation the release of my own demo TW works as expected. Unfortunately, I only noticed late after release that this does not properly throws out the ThirdFlow plugin when a plugin developer releases his demo TW. So I added a call to $tw.wiki.unpackPluginTiddlers() ... which is most surely not the, erm, best thing to do. Kind of brute force ... or taking the door into the house as we like to say over here. Now, I can't correctly release my own demo TW, but users now can. A long story cut short ... as one idea: what about an additional boot(?) method that allows us to update a specific package at least with respect to correctly current shadow and plugin information? I've seen that the boot code hides and protects the corresponding shadowTiddlers and pluginInfo objects. Or is there another way I missed in both correctly dumping a recently packed plugin but without the source tiddlers when there are also the exactly same source tiddlers available while dumping all source tiddlers that are differing from their plugin shadows? So far, I couldn't come up with any filter expression that achieves this without the need to explicitly code in specific plugin titles... Best regards, -- TheDiveO -- 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.
