Before I voice my view (from the bottom), let me say I've developed an application which uses prototype.js, script aculo, and the "windows" extension. I've also made use of Event Selectors and the "debug.js" which is offered by the "windows" group. I have an investment beyond academic interest.
Our choice to develop with prototype.js resulted in a clean deliverable and a development time which exceeded (in a good way) my expectations. That said, I have concerns similar to others voiced in this thread. Prototype.js is still on a "pre" release 1.5 (unless I missed a release?), and I have never witnessed any participation from the developer. Instead, there is what appears to be a closed-door stance, resulting in zero-visibility conditions of upcoming releases. Worse, the lack of a "full" 1.5 release suggests prototype.js has been abandoned in some way, in the best case for 2.0 development, which has no announced beta date. This is a regretful set of circumstances given the satisfaction, and the investment I have in prototype.js. The author may surprise us with prototype.js 2.0, next week, next year, or not at all. (Does anyone know?) In the meantime, the persistent uncertainty in prototype.js support has led me to reluctantly look at the alternatives. I do not look forward to rewriting our application because the foundation library (prototype.js) has a lack of support. My confidence in prototype.js would improve if there were any developer interaction.. At a bare minimum, planned release dates would be a real confidence boost. Better yet, some interaction in this forum. No feedback, in addition to a languishing "pre" release, is unacceptable. Sam (C) _______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
