On Mon, 11 Jun 2012, Jeremy Ruston wrote:
We'd also need to figure out a way for TiddlySpace users to configure which wikitext parser they're going to get. Having worked with the new parser for a week or so, I'm finding that it leads to much cleaner, more spacious, easier to read wikitext -- mainly by adopting the markdown convention of double-newline to end a paragraph, and treating single newlines as whitespace. And of course it's much, much nicer to style than the old <br> tags.
I've been thinking about this as well. There are a few variables which can control that: * The rendering subsystem of TiddlyWeb can apply different render() methods to a tiddler to make it into HTML based on the 'type' attribute on the tiddler. At the moment if this is "None" or a few variations on that theme, it is considered tw2 wikitext. The other currently supported type is markdown. So, if your new wikitext is of a different type, then applying a different renderer is no problem: Server side configuration pointing to a handler. I think your code does something a bit like this, but I may be mis-remembering the glance I made through it. * A space ought to be able to declare which renderer it uses for the same type. ServerSettings can be extended to do that[1]. So, if the wikitext type is the same, but people might prefer a different rendering engine (wikklytext, twikifier, tw5ikifer, etc) they ought to be able to declare that. It's not (yet) clear whether the new text has a different type, so which way it goes will have to wait and see.
Anyway, I remain very keen to get TW5 on TiddlySpace, and hope I can get those bits done swiftly.
Getting tw5 at large (the entire thing/concept, not just a renderer) onto TiddlySpace ought not be too much of an ordeal. Again there are a few different possible directions: * Do something akin to the tw2 serialization: push tiddlers into an HTML doc which is the tiddlywiki5 thing. * Do something akin to the /_tiddlywiki[2] app which is on TiddlySpace. That is: load a kernel, and then calculate (based on the URI) which tiddlers to load in. @dash and @mosaic[3] do similar things. The latter seems in keeping with what it has sounded like your goals may be. It's also in keeping with the goals we have for TiddlySpace: a host for tiddlers with lots of different tools that work with them. Some of those tools work with aggregations of tiddlers, others with just one. This ought to mean that tw2, tw5 and other tools can cooperate over the same corpus. [1] It has recently been extended to allow setting an 'editor' for the space. [2] http://apps.tiddlyspace.com/_tiddlywiki.txt (It's a tiddlwiki cooked up to bootstrap itself with server side stuff) [3] http://dash.tiddyspace.com/ http://mosaic.tiddlyspace.com/ -- Chris Dent http://burningchrome.com/ [...] -- 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.
