On 02/27/2014 02:00 PM, Guillaume "Louis-Marie" Delhumeau wrote:
The problem is, prototype and jQuery both share the same $ global variable. How do we deal with it?
jQuery export as "$" is optional, and all code using jQuery is invited (best practice) to use the dollar outside the global namespace in a scope like this : (function($) { // here code that uses the dollar as jQuery. })(jQuery); Using AMD has the same effect of avoiding global names conflicts. Jérôme
2014-02-26 18:57 GMT+01:00 Denis Gervalle <[email protected]>:
On Wed, Feb 26, 2014 at 6:21 PM, Caleb James DeLisle <[email protected]
wrote: Overall I'm generally in favor of migrating away from prototype but I don't know what this vote is about.
This vote is about deprecating prototype.js in favor of jQuery. It means developing any new feature using jQuery and put all the effort we can in migrating existing features to jQuery until the point we can vote the removal of prototype.js, and put it aside, as an possible extension.
Will we still be including prototype in every page load? Will it still be bound to the $ variable? If so then loading jquery for a small widget is a performance issue.
If the vote were to change prototype from holding the $ global variable and only load it on demand (requirejs) and refactor all of our code to deal with it, I'd be in favor of this even though it will break backward compat for the user. If we're not willing to (ever) break backward compat then talking about jquery is silly, we're a prototype shop, that's just our fate.
This vote looks like a sort of non-binding resolution in favor of jquery and disfavor of prototype so for that I'll give a non-binding +1.
Thanks, Caleb
On 02/26/2014 02:15 AM, Marius Dumitru Florea wrote:
On Wed, Feb 26, 2014 at 1:24 AM, Sergiu Dumitriu <[email protected]> wrote:
+1 (both the vote and Marius' suggestions)
But we also need to decide on an OOP framework for jQuery, if we still want to write OOP widgets instead of some raw function hell. +1, otherwise it will be harder to migrate the current object oriented code written in Prototype.js .
Thanks, Marius
On 02/25/2014 05:34 PM, Marius Dumitru Florea wrote:
I would add that we should use it with require.js and that we should make sure the jQuery plugins we pick integrate with require.js
Thanks, Marius
On Wed, Feb 26, 2014 at 12:32 AM, Marius Dumitru Florea <[email protected]> wrote: > +1, most of the mainstream JavaScript frameworks (Angular, Ember, > Backbone) integrate very well with jQuery so we shouldn't have any > problem picking one of these JavaScript frameworks later. > > Thanks, > Marius > > On Tue, Feb 25, 2014 at 10:03 AM, Ecaterina Moraru (Valica) > <[email protected]> wrote: >> Hi devs, >> >> This has been brought into discussion several times so this thread is >> intended for this particular topic. >> >> Thanks, >> Caty -- Sergiu Dumitriu http://purl.org/net/sergiu
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Jérôme Velociter +33 786 993 355 @jvelo Open source e-commerce and marketplaces made simple www.mayocat.org 46cl www.46cl.fr