> 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.
Yes, that makes sense. Currently, the new parser is text/x-tiddlywiki and the old parser is text/x-tiddlywiki-old. Parenthetically, I'm very hopeful that we will be able to engineer pretty good converters that convert tiddlers from old to new format, pretty much by judicious insertion of additional line breaks. If that is possible, I'll include it in the TW5 import engine, and we may want to explore building a little 'upgrade my space' app for TiddlySpace. > * 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. Yes, likewise, that sounds sensible. > 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. Currently TW5 packs tiddlers in the same <div> format as TW2. I plan to introduce a new, preferred JSON-in-a-script-tag format which should be a bit easier in terms of encodings and so on. > * 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. I've not done it yet, but the plan is to have lazy loading built into TW5, very much along the lines that we've discussed in the past: optionally pack skinny tiddlers in the HTML file, and reach out over HTTP to get the content on first access. Image references to lazily loaded tiddlers would just generate a <img> tag with the src pointing to the URL of the image, which I think would be useful for TiddlySpace too. > @dash and @mosaic[3] do similar things. I've been watching these developments with interest. > 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. Yes, exactly that. TW5 is all the stronger for not having to worry about serious HTTP serving issues. Hopefully I'm skating towards the same puck as you. Best wishes Jeremy > [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. > -- Jeremy Ruston mailto:[email protected] -- 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.
