On Sunday, January 12, 2014 11:14:03 PM UTC+7, Jeremy Ruston wrote: > > Hi BJ > > Thank you, and apologies once again for my slow progress with pull > requests and forum messages this week. > > In an earlier iteration of TW5 I included TWC parser support just by > transliterating the TWC code to generate parse tree nodes instead of DOM > nodes. I'd still be wondering if that solution isn't best when one is > aiming for as much fidelity as possible. > > I like the idea of reusing rules between the tw5 and twc parsers. > > It looks like your TWC parser inherits TW5 paragraph behaviour, is that > right? > its using the same block parsing, so I guess the answer would be yes.
> With that in mind, if I've understood the paragraph handling behaviour of > your TWC parser, it's value might be as a transition tool, allowing people > to gradually migrate content. > > hmm, maybe this will be an interesting problem to solve. > Anyhow, all of this relates to another issue we've discussed in the past: > introducing the concept of a vocabulary specifier which can accompany the > MIME type of a tiddler (ie, "text/vnd.tiddlyiki; vocab=xxxxx"; see > http://www.w3.org/Protocols/rfc1341/4_Content-Type.html for details of > the format). We could define vocabularies as either referencing a full URL > (eg, "http://vocabs.tiddlywiki.com/standard.json";), or just a single > tiddler (eg, "$:/jeremy_custom_vocab") that is defined in the current wiki. > The vocabulary would identify which parse rules should be applied, and > perhaps specify options for some of them. > > I played with this a bit in TWC using tagging to select different formatters, as this support is built into TWC (after defining the formatters in a pluggin) but what you are suggesting is more flexible. Do you mean that "vocab" would be added to the TW5 language? > Then we could establish standard vocabularies that helped people to > interchange content. > > I think there's a good chance that we're aiming at the same thing, what do > you think? > > yes, I think so. There will probably be other uses as well, I defined a subset of TW5 wikiparser without out the html and marcos, and some other stuff, then put $$$text/reducedtw>text/html into tiddlers from tiddlywiki.com that I want to edit visually, then manually copied the rendered text back into the textarea. you can see the results here http://vtw5proofofconcept.tiddlyspot.com/ > Best wishes > > Jeremy > > > > > On Fri, Jan 10, 2014 at 3:26 PM, BJ <[email protected] <javascript:>>wrote: > >> (TW5) Adding Support for variant wikiparsers >> >> I have seperated the bulk of wikiparser into a abstract base class >> (without rules). This is then inherited and made concrete by providing >> rules to the constructor. >> >> https://github.com/buggyj/TiddlyWiki5/tree/wikiparser506 >> The targets from bld.sh seem to look the same. >> >> This new structure allows for other types of wikiparsers to be build from >> the same mechanism. >> Here I have started the support for the text/x-tiddlywiki parser: >> >> https://github.com/buggyj/TiddlyWiki5/tree/wikiparserclasic506 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "TiddlyWikiDev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/tiddlywikidev. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Jeremy Ruston > mailto:[email protected] <javascript:> > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/groups/opt_out.
