Ok, so you used prototype version X.X (doesn't matter, I'm still using 1.4)... and you've built a clean toolkit or componenet set or application around it and it works great. What is the rush to get a new version of prototype? My applications are world class medical systems (cardiology data collection and reporting) used in hospitals around the country, and I'm still using proto 1.4 with no immediate plan or need to upgrade to 1.5pre or 2.0 or 12.6. As far as general support, this is the place, man. We in this list are the support for both proto and scriptaculous and we're damn good at that.
As I've said, all avenues for moving proto forward have NOT been exhausted...
Thomas, please can we get some official statement on this matter as far where _you_ are on it? I'm assuming you're behind us, so can we formally put together some sort of action plan? Clearly you have connections, so are you privvy to some information that's not being generally shared in the community about the immediate future of prototype?
On 7/20/06, Sam <[EMAIL PROTECTED]> wrote:
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
_______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
