Thanks PMario... I should've remembered from your last post with respect to TagSearchPlugin ...which I haven't touched yet. I guess, it would be nice to do that in an automated fashion, e.g. a "check compatibility" script or plugin of sorts that would skimm through all tiddlers tagged systemConfig and list all those with conflicting code. Perhaps that would be a good thing to realease with each new tw... a CompatibilityTestPlugin the sole puprose of which is to display to an end user who wants to upgrade whether or not there are any conflicting plugins and due to which changes exactly. It would be even better to be able to load this kind of test-suite via some InstantBookmarklet.
I would think that Eric is the most literate on all kinds of these deprecated functions and the likes ...perhaps you could write and provide such a TestEnvironment in it's most basic form? Perhaps with a Test definition Tiddler that reads somewhat like this... !Version a.b.c TestPattern1:InfoMessage1 TestPattern2:InfoMessage2 !Version a.b.d TestPattern3:InfoMessage3 etc... of course, in a cumulative fashion This could even be used to test all kinds of things, not necessarily js in systemPlugins. Cheers, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki?hl=en.
