The problem James speaks of has been fixed in the latest release of prototype.
What remains is a pollution of the namespace. Prototype defines classes like 'Effects' or 'Event'. How big is the chance that another library might do the same? Decide if that's a risk you want to take, for a framework, it's not a risk you should take. Now I discussed with the prototype guys to fix that, but the response was not positive, so we decided to switch to dojo. regards, Martin On 4/3/06, Dennis Byrne <[EMAIL PROTECTED]> wrote: > >we were happy with rico & prototype... :) > > You may want to check out James McParlane's blog before you bring > prototype.js or any of it's derivatives into your application. > > http://blog.metawrap.com/blog/WhyIDontUseThePrototypejsJavaScriptLibrary.aspx > > >Mert > > Dennis Byrne > > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
