Paul says: "I guess I'm saying I can live with loss of backwards compatibility with external libraries introduced by plugins and as with other similar clashes, and think the onus is on the plugin author to resolve such clashes, not TiddlyWiki."
I disagree. The clash with $ is much more severe than the clash with String and Date extensions (and those extensions are historical - we wouldn't do them now). There might be a case for accepting clashes if it was really difficult to avoid them, but it is not. It's easy to avoid clashes, so we should do so. My favoured option is to defer the decision and use jQuery. If we really want to resolve the issue then my next favourite option is to use $j. Martin 2009/4/21 FND <[email protected]>: > >> not just 'eval'... custom macro handlers, toolbar handlers, hijacks, >> etc... can also get invoked within the scope of a locally-declared $ >> (...) alias > > I don't believe this is correct - please take a look at this test case: > http://fnd.lewcid.org/tmp/alias_scope.html > > It boils down to the following: > --------------- > var $ = "lorem ipsum"; > var foo; > > (function($) { > > foo = function() { > console.log(typeof $); // prints "function", referencing jQuery > }; > > // hijack > foo_orig = foo; > foo = function() { > foo_orig.apply(this, arguments); > console.log(typeof $); // prints "string", referencing custom $ > }; > > foo(); // prints both "function" and "string" > --------------- > > Am I missing something? > > > -- 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 at http://groups.google.com/group/TiddlyWikiDev?hl=en -~----------~----~----~----~------~----~------~--~---
