A quick update that might be appropriate, is that raphaelJS is not up to the task i want it to do. You can create SVG style vector graphics with it ok, but you cannot 'load' an external SVG natively, at least without some pretty heavy regexp style screwing about.
The option i am looking into now is the SVG plugin for JQuery http://plugins.jquery.com/project/svg It might also be a better fit as a core module, as JQuery is part of the Tiddlywiki infrastructure IIRC. Tim. On Jul 14, 5:13 pm, Paul Downey <[email protected]> wrote: > Hi Eric! > > >> Anyway, for TiddlySpace I've created the simplest possible plugin and > >> example: > > >> http://raphaeljs.tiddlyspace.com > > >> and I'm hoping to use TiddlySpace to cook standalone TiddlyWikis, so > >> this may work for you, too. > > > Except for the use of a much more up-to-date release of RaphaelJS, > > Paul's "new" plugin is exactly the same as my existing plugin: > > http://www.TiddlyTools.com/#RaphaelPlugin > > > You can use TiddlyTools' RaphaelPlugin precisely the same way as Paul > > has done, by writing a separate, dependent plugin to programmatically > > invoke RaphaelJS API. > > Yeah, I linked to that in the Space GettingStarted tiddler ;-) > > > The *only* difference in my plugin is that I've included documentation > > and embedded some sample code using InlineJavascriptPlugin (which is > > NOT *required* in order to use RaphaelPlugin within your documents.) > > Yeah, I don't like the inline JavaScript, and that may not be > appropriate for TiddlySpace. > > > Of course, I should have updated the RaphaelPlugin long ago to keep it > > current with the latest stable release of Dmitry's excellent work. > > It's a problem in general to keep such things up to date. I have a > similar issues with TiddlyProcessing. At least we can use the space to > save people having to update their own copies. > > > One (minor) concern is that the newer RaphaelJS library is *not* > > completely backward-compatible with the older version, so that anyone > > who is using the current TiddlyTools RaphaelPlugin will either remain > > 'orphaned' on that older library, or will have to re-write their > > scripts to match the updated API. > > Oh, I wonder if in our case we should allow people to include a > version of a space. Of course they can hit a revision of the tiddler > via the URI: > > http://raphaeljs.tiddlyspace.com/bags/raphaeljs_public/tiddlers/rapha... > > > Nonetheless, updating the embedded library code in RaphaelPlugin is > > the appropriate course. Naturally, when I update the library in the > > plugin, I will also need to revise some of the example code in the > > documentation in order for them to continue to operate properly. > > Yes, I'd encourage you to do that as your plugin is complementary to > the one on TiddlySpace. > > Best! > -- > Paul (psd)http://blog.whatfettle.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.
