The ext.js blog also mentioned a number of other "server side" projects.
http://extjs.com/blog/2008/01/22/ext-growth-and-server-side-community-projects/ I know a lot of us would love to see some good server-side+widget side stuff happen in TurboGears ;) I just haven't (and probably won't for a while) had time to look much into doing something interesting in that area. But as I said earlier, I'll definitely support those who do. --Mark Ramm On Jan 22, 2008 6:31 PM, Luciano G. Panaro <[EMAIL PROTECTED]> wrote: > > Maybe some ideas could be taken from here: > http://inside.glnetworks.de/2008/01/18/announcing-ext-scaffold-generator-plugin-for-rails/ > > I just saw this and haven't tried it yet but it reminded me of this > thread. > > On Jan 19, 10:12 pm, "Daniel Fetchinson" <[EMAIL PROTECTED]> > wrote: > > > > Here are (some of) the fully functional examples which do cover remote > > > > data access of all shapes and sizes using Stores, Proxies, Readers, > > > > etc, etc via JSON and/or XML: > > > > > >http://extjs.com/deploy/dev/examples/form/custom.html > > > >http://extjs.com/deploy/dev/examples/form/xml-form.html > > > >http://extjs.com/deploy/dev/examples/form/forum-search.html > > > >http://extjs.com/deploy/dev/examples/grid/edit-grid.html > > > > > Thanks. This helps somewhat, but for me it does not replace a systematic > > > documentation of the concepts and ideas behind the data handling, when > > > and why and how to use the different stores and proxies and readers. Can > > > you point me to anything helpful here? Also, some classes such as > > > JsonStore aren't covered in these examples. > > > > The best way I think is first starting > > withhttp://extjs.com/learn/Tutorial:Introduction_to_Ext_2.0General > > concepts of data handling (Stores, Proxies, Readers, etc) are > > herehttp://extjs.com/learn/Manual:Dataand when you got through all of > > that the API documentation athttp://extjs.com/deploy/dev/docs/is not > > > that frightening any more :) > > For example it will be clear that JsonStore is just a Store with a > > reader that knows how to read JSON. You could write your Store and > > Reader by yourself but since it's such a common case you have > > JsonStore for convenience. > > > > There is of course a learning curve but in this case I think it's > > fully justified because the design is great with several (necessary) > > layers of abstraction. More layers, more learning, but it pays off. > > The alternative would be a "It's so easy to use" framework with no > > abstraction at all but that would not scale and would be difficult to > > maintain. > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
