[xwiki-devs] very fragmented javscript code

Hi, I have noticed that we have javascript files lying at several places in the xwiki web application. Further we seem to be using lot of javascript code developed by many independent OEM vendors. All this makes very hard to understand what all components are present in each js file. I would like to know why we use such fragmented set of js code, where as almost all the functionality could have been achieved by using single ajax toolkit and any additional work could have been done by using plugins on top of these tool kits. Every good ajax toolkits provides ways to extend and there is a good library of useful plugins found for each. In the xwiki application I have found at least 4 ajax toolkits: general toolkits found ---------------------- scriptaculous rico prototype yui Further there are lot of other js code also lying around. Again I am not sure if most of this is extension of one of the above toolkit or again these are independent set of javascript code (ajax/dhtml widgets). other js files found: --------------------- wysiwyg editor --------------- tiny_mce wiki_editor color picker --------------- chwScripts panels wizard ---------------- panelWizard miscelaneous --------------- ajaxSuggest lightbox tablefilterNsort usersandgroups tdwScripts wzToolTip Almost of the functionality present in these javascript file could have been built using just one ajax toolkit. Is there any attempt to clean this stuff. To start with I suggest to keep all the possible js code a one place, probably in scrips directory. Next we can replace code by using agreed toolkit. This way lot of extra js code would be removed and we would have much compact UI. Also can someone mention 1 liners as what is the purpose of each js file we use in xwiki. I am planning to redesign the complete UI using ext-js and jquery and it would help me a lot in knowing how can each be replaced with new component. Like after a lot of hit and trial I found that if I include ext-js and rico together, ext-js does not get loaded. So now I can replace whats being done by rico toolkit with ext-js/jquery equivalent. Let me know what are your opinions on this. Thanks Sachin ----- http://www.assembla.com/wiki/show/sachin_mittal about me: -- View this message in context: http://www.nabble.com/very-fragmented-javscript-code-tp15561552p15561552.ht… Sent from the XWiki- Dev mailing list archive at Nabble.com.