The problem comes from the multiplication of the modules which use these scripts.
So in the long term, the members will be able to select and to keep their theme in their profile, I think that these scripts must be in a folder specific to the root of the Web site.
Why not to make a package “jseffects” with lightbox, thickbox, greybox, dojo, etc… then the webmaster will add just the bonds in the theme
ok, I see your point of view and also dislike the multiplication of un-necessary code throughout the system, when only one instance of it can be used by other components of xoops.
A similar example of this multiplication problem is what's happening to all the wyswig editors, after installing 10 modules you will see that you have at least 6 or more koivi's in your system, because besides the one you install in the class folder, there's phppp's xoopseditor pack, plus some modules also bring the editor inside them, I don't see that practical ....and well it wouldn't be nice for that to start happening with these light-grey-thick box extra effects.
Will the module developers take this in consideration? (it's something unrelated to the core )
It would be really great if there were some planning so that these extra components are found in one place, and that it be a standard to access these resources from there. This would serve as a clear guide for theme and module developers know with what tools they count with, how to implement them in their works following a standard, and ideas on which new ones can be implemented without interfering with the core and making easier their maintenance and upgrades.
This could be like a new category in the downloads section where these basic resources are found and are not necessarily modules, ex: xoopseditor, frameworks, smartobject, + these new js/ajax effects