On Mon, Jan 14, 2008 at 08:35:31AM -0800, Mike Orr wrote: > On Jan 14, 2008 4:57 AM, Lawrence Oluyede <[EMAIL PROTECTED]> wrote: > > > It seems that the complexity overcame the reason why extjs exists. > > BTW extjs is too big to be included in pylons and does a hell lot more > > than the standard developer needs (which is basically dom > > manipulation, css selectors and Ajax). > > Am I right? > > Yes. People need to update parts of a page, and some want colorful > special effects, the more the better. > Also, some Javscripts make JS more like Python, which helps in programming it. > > Well, JQuery is by far the most popular on the list, and moderately > more popular in the wiki poll, so let's assume we'll be adding it > alongside Prototype/Scriptaculous. We'll need a maintainer to package > it up for WebHelpers, and also to help decide the common Python > interface to all these libraries.
I think a generic interface that translates to library-specific Javascript commands is really the best way. Let's support: - jQuery - YUI - scriptaculous/prototype If we can agree on some high-level API (I have no idea how to design that yet) then I'll happily (co-)maintain the API-to-jQuery functions. > Are there any important features not in JQuery that we should have? Mainly UI elements. ui.jquery.com still has some sharp edges. But for the colorful basics and AJAX jQuery is more than sufficient and very light-weight and fast. > Robert Leftwich offered to maintain YUI. It has some popularity among > Pylons users so we might as well. It appears like the most reasonable choice if you need a few widgets and don't intend to surrender to ExtJS. > Let's have the JS maintainers and those who wish to help design the > Pylons Javascript API subscribe to pylons-devel, and we can discuss it > there. I'm there. Let the games begin. :) > ExtJS can be added later if enough people clamor for it. (I think > Mark Ramm was the only person who said he likes it.) Ben Bangert dumped ExtJS onto me on IRC when we talked about Javascript libraries. :) And he's right - the basic selectors are basically identical to jQuery. But there the similarities end. > But I was struck > by Christoph Haas' comment, "[With ExtJS] you will write your > application in 90% Javascript and 10% pylons." Somebody who's writing > a 90% Javascript application probably does not need Pylons, just a > static webserver and something for database queries. Or even (bear with me) a few cheap PHP scripts baked together. Pylons has so many great tools that create HTML, validate forms, support AJAX calls, handle JSON, use sessions... it would be a shame not to use that. Talking about it with a few people (e.g. the maintainer of the "ingrid" grid plugin in jQuery or even newcomers in #extjs) I heard more voices about ExtJS. Most people say that ExtJS is an impressive library and a proof-of-concept what's possible in the web 2.0 <cough> world. But not just does the 90%/10% relation still seem to be true but the Javascript needed to define the widgets is a hell to look up in the API reference and create working code from it. The learning curve is pretty flat. For a current project where I tried it I've now dumped it and gone back to jQuery. Looks like the makers of ExtJS have taken classic UI concepts (event handlers control everything) and mixed them with bloat. ;) Cheers Christoph -- [EMAIL PROTECTED] www.workaround.org JID: [EMAIL PROTECTED] gpg key: 79CC6586 fingerprint: 9B26F48E6F2B0A3F7E33E6B7095E77C579CC6586 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
