> I think is definitely a good direction to take cook in. I presume one > of your goals is to avoid having to manually save TiddlyWiki to > generate the RSS file. I can also see other benefits of cook and > TiddlyWiki being able to share code.
Exactly that, we should be able to do better splash screen generation, too. Conversely, TiddlyWiki itself can re-use the cook process for saving changes, obviating the current read of the tiddlywiki file that precedes saving it. I'm refactoring it furiously now that I've got it working and have something stable to test against. Best wishes Jeremy -- 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.
