Ext is a full featured component library. The only issue with it (for some) is going to be fact that it's a commercial product more than it is open source (you can use it for free but only if you are releasing your stuff as open source). If you are building a major browser based application intended to run as a single page, long running app (think full featured desktop-like app in the browser), and you are planning to make money with it or are in an enterprise setting and can't release your app as open source, then Ext is (as I said) MORE than worth the VERY small price they are charging.
Trust me, whoever said it's nothing more than an abstraction layer is a) wrong and b) just not using Ext to its fullest potential. Prototype is an abstraction layer (OO and cross browser DOM manipulation). Ext _can_ be used with many other frameworks/libraries, including prototype. If you use it in this manner, Ext _does_ smartly utilize facilities from those libraries, assuming that that is why you chose to use both. If all you want are a couple of semi rich widgets to go into a low or no budget project, that you or your client are trying to make money with, don't use Ext. If you are building a full blown browser app that needs to have a polished look, work across browsers, and that looks and feels like a desktop app, than don't use anything other than Ext (it's by far your best choice). nuff said :) On 6/17/08, Ken Snyder <[EMAIL PROTECTED]> wrote: > > On Tue, Jun 17, 2008 at 5:42 PM, Franck PORCHER <[EMAIL PROTECTED]> > wrote: > >> ... >> >> In a few words, and in whatever spare time you Core guys might have, >> what is the story behind these 2 frameworks, if any, how do they compare in >> the long run of javascript programming (if any kind of comparison was ever >> attempted), and how do you foresee the future of both. >> >> Franck PORCHER >> www / smartech / pf >> > > A good friend of mine uses Ext because he writes applications that must > work with YUI, dojo, /and/ Prototype. Using Ext allows him to write code > that will work with any of those libraries. He describes it as an > abstraction layer above a framework. As an abstraction, it makes sense that > each Ext feature would be limited by the library with the weakest > implementation of that particular feature. > > - Ken Snyder > > > > -- Ryan Gahl Manager, Senior Software Engineer Nth Penguin, LLC http://www.nthpenguin.com -- WebWidgetry.com / MashupStudio.com Future Home of the World's First Complete Web Platform -- Inquire: 1-920-574-2218 Blog: http://www.someElement.com LinkedIn Profile: http://www.linkedin.com/in/ryangahl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
