> I would highly appreciate a simple way to go to the javascript layer for > highly optimized filters and keep the basics simple. > > So we can keep the 80% of usecases and users happy with a powerfull but > simple wiki like syntax. For the 20% "special cases" we use the built in > javascript engine, where the browser vendors do the heavy lifting an > development. > > For the "inconsistencies" that stay in the syntax, we just need more > examples, that show how the fiters work. >
I'm keen to avoid having inline JavaScript until we're able to safely interpret content from untrusted sources. We can make the system more robust for the future by encapsulating JavaScript logic in modules (which is possible today). Best wishes Jeremy -- Jeremy Ruston mailto:[email protected] -- 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.
