answering my own question, firebug is working great for this. On Wed, Oct 6, 2010 at 8:06 PM, David Young <[email protected]> wrote: > was that wikiformat field a custom field applied to each tiddler (like > in the html div elements)? > > Also, wondering what is the best way to get the html output from the > parsers; a simple firefox "view source" is giving me the contents of > empty.html and not the dynamic contents of the tiddlers. > > On Wed, Oct 6, 2010 at 4:29 PM, PMario <[email protected]> wrote: >> hi david >> I'd go for solution 2). In my opinion this would be the cleanest way. >> I wouldn't care about 9 kByte for the new formatter. Compared to an >> jpg image, this is allmost no overhead. >> >> There is a custom field "wikiformat" in getParser. As I understand the >> code, if you set this field to your newParserName it will also use >> your custom parser. This way you have the possibillity to use tags >> only for tagging. >> >> _But_ you have to hijack the saveTiddler function and define a custom >> field "wikiformat". >> >> @coreDevs >> Where would be the best place to do this? >> >> have fun! >> mario >> >> On Oct 6, 7:48 pm, David Young <[email protected]> wrote: >>> OK, back from the real-world work break and ready to get cracking with this. >>> >>> These formatter plugins from martinswiki are great, but I'm seeing 2 >>> different paradigms. >>> >>> 1) is to actually change config.formatters globally. >>> >>> 2) is to make a new formatter and then tag every tiddly in that format >>> (e.g. example formatter will interpret tiddlys with the tag >>> ExampleFormat with the plugin, otherwise default to tiddlywiki). >>> >>> 2 is less destructive to existing tiddlywikis; but it adds the extra >>> memory overhead of a new formatter (instead of just chopping up the >>> global one). The formatter tag method also looks like it is the >>> "supported" method for doing this sort of thing (getParsers in the >>> core will check for tags before setting the formatter). 2 also adds >>> the extra step of tagging every tiddler with the desired format. >>> >>> Any thoughts on these 2 options? >>> >>> >>> >>> On Mon, Sep 20, 2010 at 8:56 AM, PMario <[email protected]> wrote: >>> > In addition to FNDs links I'd suggest martinswiki [1] >>> > I think it would be a good starting point for a new formatter. >>> >>> > insideTW is "the" source (for me) to see what happens inside TW :) >>> > Eric has nicely sniped out the main code, to get a good overview [2] >>> > about the repexp which is used. >>> >>> > I think the new regexp for filtering will be the most challenging >>> > part. If you need info about this. see regular-expressions.info [3]. I >>> > found many other sites, but for me this one was the best, because it >>> > also talks about the different implementaions and what's different in >>> > JS. >>> >>> > -mario >>> >>> > [1]http://www.martinswiki.com/#ExampleFormatterPlugin >>> > [2]http://www.tiddlytools.com/insideTW/#config.formatters >>> > [3]http://www.regular-expressions.info/reference.html >>> >>> > On Sep 20, 11:04 am, FND <[email protected]> wrote: >>> >> > I'd like for tiddlywiki to support my favorite markup language, >>> >> > txt2tags. I've decided to do this via a tiddly plugin. >>> >>> >> Great! >>> >>> >> > is it possible for me to iterate the array and replace individual >>> >> > members in objects? [...] I don't know if the objects are mutable >>> >>> >> They are indeed mutable - some samples can be found >>> >> here:http://svn.tiddlywiki.org/Trunk/contributors/MartinBudden/formatters/... >>> >>> >> A simple example might be this >>> >> one:http://svn.tiddlywiki.org/Trunk/contributors/FND/formatters/Paragraph... >>> >>> >> > I also have some general concerns about code execution and complexity >>> >>> >> I guess the best way to proceed is create a prototype and see how it >>> >> performs rather than trying to predict behavior. >>> >>> >> -- F. >>> >>> > -- >>> > 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 >>> > athttp://groups.google.com/group/tiddlywikidev?hl=en. >>> >>> -- >>> David Young >> >> -- >> 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. >> >> > > > > -- > David Young >
-- David Young -- 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.
