> Would this likewise facilitate plugin development by being able to > develop in your preferred environment while having your testbed being > "baked" via the browser?
Yes, sort of; cook.js is more about giving TiddlyWiki developers that sort of experience. The specific intention is that plugin authors would be able to work with an exploded TiddlyWiki format, with plugins loaded from external .js files. And then, as you suggest, they would be able to use cook to bake the plugin into a standalone tiddlywiki file. The goal is that plugin authors shouldn't need to be running node.js. Cheers Jeremy > > tb > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" 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/tiddlywikidev?hl=en. > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev?hl=en.
