Mike, > You might find some inspiration from the code here > http://www.strm.us/tw/examples_twgg/ijstaskmanager.html#TaskManagerPl...
Yes, very interesting. > setup as a plugin, to automatically create tiddlers at startup > (silently) Ideally it would only create a new tiddler when the URI included the appropriate values, not automatically. I can image two (2) scenarios based on a version of this code: 1. Tolerable scenario: my TiddlyWiki would be a "slop bucket", used exclusively to receive these "chunks" as they come along, always creating a new tiddler whenever opened. I would have to move the content amongst other TiddlyWikis after-the-fact. Of course, I could use http://www.tiddlytools.com/#ExternalTiddlersPlugin to access these chunks from the other TiddlyWikis. However, this multiple-TiddlyWiki arrangement isn't conducive to searching, grouping, and filtering content. 2. Perfect scenario: my TiddlyWiki would support a hijacked #newTiddler: paramifier or a completely new one (#newMegaAwesomeConfigurableTiddler) that would support: * template selection, i.e. newTiddler, newHTML, newScript, newPlugin, newContact, newBookmark, etc. * title, defaulted to whatever parameter was passed but with the option of including (prepend, append) a configuration string that could include date and time * none, one, or more tags applied to the tiddler - presented as a multi-select listbox from choices available in the TiddlyWiki and with the option to add new * content (body) applied to the tiddler - from clipboard only (for now - no sense getting crazy with my Christmas wish list) * possibly even support for custom field values: ** if newContact *** firstname=prompt *** lastname=prompt *** etc. ** if newBookmark *** description=description *** url=clipboard * possibly support ReminderPlugin or something similar so that new content is automatically presented the next time the TiddlyWiki is opened normally This paramifier would fire when prompted in the URI but not be required. The core paramifiers, newTiddler and newJournal, would not be modified. I'm suggesting a framework that would be extensible, piggybacked on the core: * For those GTD lovers amongst us, this kind of UI could allow for pushing To Do items into the TiddlyWiki * With a little automation effort, a "monitor" UI could fire off entries into a TiddlyWiki as it registered events, e.g. create tiddlers of RSS feed entries, Twitters, LinkedIn updates, new SlideShare presentations (YouTube, Google Video, etc.) based on search criteria * For the truly courageous and ingenious amongst us, the framework could be used to push CHANGES to tiddlers, not just create new ones: ** Update a status in GTD ** Complete and/or delete a To Do item ** Revise a custom field value (update a Contact telephone number) ** Modify or delete one or more tiddlers based on tag values (fET) Ok, I'm going to stop now. > if you want to do it so that the tiddler opens in edit mode you could > adapt the new task script here: (similar to the plugin > above)http://www.strm.us/tw/examples_twgg/ijstaskmanager.html#ProjectTemplate The problem I have with http://www.strm.us/tw/examples_twgg/ijstaskmanager.html#ProjectTemplate is converting the code to work through the URI. Mike, thank you for your suggestions. Craig -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
