> I haven't been keeping up with the new implementation, but the"old" tiddly > wiki has a wikitext field that can be set to a different wiki formatter. > It's how plugins with alternative syntax have worked in the past.
In TW5 the mime type of a tiddler is used to indicate its format, which determines how it is parsed and rendered. > I would add that I agree that even the default markup should be a plugin. I > wonder if the markup could be made even more modular- the idea being that a > new formatter can easily clone specific markup functions from another > formatter. An example would be to make a creole formatter "clone" the macro > syntax from the default tiddly formatter. The wikitext parser in TW5 is just a loadable module that knows how to parse text in the format 'text/x-tiddlywiki'. The macro support in TW5 lives within the store, rather than being embedded in the parsing and rendering code. It is designed that way to make it easy to add macros to other parsers (macros within SVG images would be useful, for instance). Furthermore, the wikitext parser itself is split up into discrete "rules" that can be loaded independendently and augmented. (This is also true of the current TiddlyWiki wiki text parser). > It's important to allow the cloning or copying of a format function, so that > a plugin author can trust that the function cloned is kept up to date (as > opposed to copying the actual code implementation from the default > formatter, which requires that the developer constantly maintain the copied > code) I think all of this is comes pretty much for free from the design using JavaScript modules judiciously. Here it's a matter of ensuring that functions such as macros can be invoked directly from JavaScript code. Best wishes Jeremy > > On Dec 25, 2011 6:32 AM, "PMario" <[email protected]> wrote: >> >> Hi Martin, >> I think, it isn't necessary to extend TW syntax with WikiCreole >> syntax, it would make it possible to mix both and create a new syntax, >> that is incompatible to any of them. >> >> So I'd say. Please don't. >> >> TW syntax should be a plugin. >> Creole can be a plugin too. >> >> Since Jeremy parses the TW syntax into a "basic internal" JSON >> sturcture, it should be possible, to write converters from/to any >> other format. This will be a hard job, but it can be done. I'd vote >> for convertes as plugins, so every user can decide, which syntax s/he >> wants to use. >> >> If a syntax, that is defined with a tiddlers "type" field, is not >> active, the core could just render it as plain text. >> >> -m >> >> >> -- >> 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. -- 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.
