You are indeed very right. However as a Joomla integrator I don't always have the luxury to choose the libraries I work with. Let me give you an example:
1) Joomla basic installation already has (older) JQuery and Mootools installed. They get loaded in the <head> by the Joomla head tag. In fact, there is a script I use to deactivate one or the other or both, since JQuery is used in the front end by default, but Mootools is only used in the backend administration, so by and large deactivating it in the front end should not present a problem unless... 2) Many third party add-ons for Joomla use either the built in JQuery and/or mootools to work. Some will use the default, some use their own version. Often is not up to me choosing to use an extension. A large part of my business is helping Joomla web site owners integrate their own site and I get called in the middle of the development when these extensions are already installed and an integral part of the web site. 3) When I can choose to install my own extensions, I generally try to pick those that will present the least JS issues. However, that's not always possible if the client is bent of having a certain functionality as in the case of the one that needs the superfish menu. In that case superfish is really the only option I have short of building my own menu (which at some point I did but it was hell to maintain and I could not upgrade it to Joomla 1.5.x) Ideally, I'd like Joomla to use either the latest version of JQ and MT (as they are planning to do in Joomla 1.6) or, even better, give the users a choice to upgrade the version. That would be a whole new ball of wax, but they could use the libraries only in the backend and give us a choice of library for the front end. Meaning not making any front end feature rely on a specific library. Even better it would be if the library guys really tested their product against the other major libraries a bit better. I pretty much suspect that it is impossible to really troubleshoot a problem inside the core code of any library without breaking it. However, I am still trying to figure out where I can learn how to do it anyway. I hate when I don't understand things and it would be really nice to have some step by step tutorial on some general procedures. I'd really like to see someone working on a site with several JS errors (especially in IE) and see how they go about fixing them. I think a lot of people could benefit from such a tutorial. I think watching something like that would be a real "Gotcha" moment for me. On Jul 29, 2:26 pm, alfonsoml <[email protected]> wrote: > On Jul 29, 4:28 am, conticreative <[email protected]> wrote: > > > > > I have been trying to learn how to troubleshoot JS errors in Firebug > > and IE forever but I am really stumped and don;t know how to proceed. > > > For instance, I have several Joomla sites where the default Mootools > > and JQuery files in Joomla throw errors in firebug and IE8. Now, these > > are the default JS files, not something I added and when I try to > > trace the error (which is at best obscure in both FB and IE) often I > > get to the Mootools or JQuery code but once I am there I have no idea > > on how to proceed. IN IE I often cannot even get there. > > > Clearly, I am missing something big and I suspect that may be partly > > due to my ignorance in JS and the DOM. I know how they work, but I > > certainly cannot troubleshoot them. > > > Now, the same was true for a lot of other stuff but usually I can > > research things and eventually they start making sense. JS > > troubleshooting, especially in IE has me completely stumped. If there > > was someone offering a course online I would take it. > > > If any JS and DOM guru is reading this, I would love it if you point > > me in the right direction on where to start in understanding this. Do > > I need to take a tutorial on the DOM? Do I need more JS Knowledge > > (that'd be obvious, but I have 10 JS books and none really go into > > troubleshooting). > > > Any help and pointers would be greatly appreciated. > > If you are using in the same page different libraries like jQuery and > MooTools, there are high changes that you'll have a big headache, and > you should just forget about it. Stick to one library, avoid adding > new libraries to the mix because some of them modify some internal > behaviors that are quite difficult to understand at a simple gaze, and > then the other library will try to also do its changes and now it > depends on how lucky you are. > I think that currently the libraries are trying to avoid these > problems, but if you are forced to use older versions, then it will be > hard to fix the problem by yourself. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" 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/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
