Yes they are… the MSM in action, you see? 😊
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
January 16, 2009 7:35pm
Subscribe [24]#31 / Jan 21, 2009 6:23am
Yes they are… the MSM in action, you see? 😊
#32 / Jan 22, 2009 7:17am
Am i right that when jQuery-module comes along with v2.0, we “normal” users can use all jquey-plugins available? And that EE then updates the jQuery when it updates itself (now it’s 1.3, das jquery.min)
Well anycase, time goes by and soon this dark winter its starting to change to spring and im happy, as always =)
#33 / Jan 28, 2009 1:31pm
Regarding the integrated jQuery Framework, though I think it is a great idea, we should have the option of what framework should be used. I understand many developers use jQuery but not all. I prefer prototype over jQuery and I know many other developers who do as well.
I’m not requesting that Prototype be shipped with EE but that there be a way to use prototype if I want to. Perhaps there can be a $DSP method that loads the JavaScript Libraries and it takes a parameter which determines the library. If no parameter then it loads jQuery.
This way I can easily extend the control panel using prototype without worrying about conflicts.
EDIT:
I just realized that what I am asking is impossible. The entire EE control panel will use jQuery so I will not be able to use my preferred library. That’s a bummer.
Can it at least use jQuery.noConflict(); ?
Or will I now be forced to learn jQuery just so I can continue to develop on EE?
#34 / Jan 28, 2009 1:42pm
The Control Panel will use (uses) jQuery, however there is absolutely no need for you to use it on your site. If you choose to, you can use jQuery from EE, or do as I do on my site and load it remotely from Google, or include files, or simply use another library. There are no downsides to this from a web development perspective.
#35 / Jan 28, 2009 1:51pm
The Control Panel will use (uses) jQuery, however there is absolutely no need for you to use it on your site. If you choose to, you can use jQuery from EE, or do as I do on my site and load it remotely from Google, or include files, or simply use another library. There are no downsides to this from a web development perspective.
I understand that. However, half of my sites run custom modules, extensions and plugins. bbook.com for example, is a highly customized EE setup. Lots of modules, extension and plugins. It likely will not upgrade to EE 2.0 as it would require a whole source refactoring and I will have to learn jQuery from scratch.
I have nothing against jQuery. I just don’t know it enough to translate all my modules and extensions from prototype.