Thanks so much for a perfect answer Jeremy. May I suggest that something addressing this issue be posted to the main website, perhaps even mentioned and linked to in/from "Hello There"?
And just to show my hubris knows no bounds, here's my top wishlist item<http://groups.google.com/forum/#%21msg/tiddlywiki/VkSfqHqo1M8/qd2S7Hio6IoJ>in the "external tiddler" family, I think it's pretty "low-hanging fruit" with a huge series of follow-on benefits: I imagine something in core that would allow for the flexibility of these guys from Eric: - CreateTiddlersFromCSV<http://www.tiddlytools.com/#CreateTiddlersFromCSV> - TemporaryTiddlersPlugin<http://www.tiddlytools.com/#TemporaryTiddlersPlugin> with feature/UI ideas from these as well - ImportTiddlersPlugin <http://www.tiddlytools.com/#ImportTiddlersPlugin> - LoadTiddlersPlugin <http://www.tiddlytools.com/#LoadTiddlersPlugin> I'm currently on a kick of "plain text rules", not only for future-proofing the data itself, but also in line with the *nix philosophy - Write programs that do one thing and do it well. - Write programs to work together. - Write programs to handle text streams, because that is a universal interface. Beyond the immediate benefits of data sharing, replication, version-control, accessibility to your-local-toolset progs and script etc, * any* database/server-based solution can obviously work with plaintext, so that's a "multi-engine" path from core to server-based even before implementing a plug-in architecture for data-storage. Enough enough I know I know. . . And thanks again for your game-changing contribution to open-source knowledge management. . . -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/OJXr19DUA9UJ. 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.
