On Fri, Apr 25, 2008 at 12:15 PM, Wojciech Malinowski <[EMAIL PROTECTED]> wrote: > > Florent Aide wrote: > > On Fri, Apr 25, 2008 at 3:23 PM, Wojciech Malinowski <[EMAIL PROTECTED]> > wrote: > > >> Do you think authors of FormBuild or FormAlchemy chose a better > >> approach? Did I miss any other similar project? > >> > >> I will be really grateful for all feedback as I'm now planning the > >> future of this package and would like to know if there are people > >> interested in using it. I believe what you really want is toscawidgets, that is the library on which dbsprockets is build and it's very very similar to your sample. In fact tw.forms is almost the same except that in the model each tw form has it's own template so you do only form.display() and what you are doing in your template you do it on the forms template. other than that your package and toscawidgets are different in syntax.
> > > > Did you take a look at dbsprockets ? > > > > http://code.google.com/p/dbsprockets/ > > I took a quick look at the docs trying to find a very simple usage > example. I found this: > http://code.google.com/p/dbsprockets/wiki/DBSprocketsAPI but it looks > like too much magic for me. yes it is, that's it's purpose although most can be overridden just by plugin-in your own also dbmechanic is too much magic but it all can be overridden that is one of it's design goals. > It seems to completely take over the > rendering of the form and positioning of elements and I'd like to keep > these completely separate from form definition and request parsing. this is not quite true, all you need is to change the template. > > Also - the only place where I want the database model to meet the view > (template) is in the controller action - by explicit assignments. That's > why I'm going to integrate SQLAlchemy into pydecforms by using code > generation (probably paster plugins) and not by introspecting SQLAlchemy > objects in the runtime of the application. > that is the approach most toolkits use and to be honest I have found that the runtime generation is better, because you don't want to worry about your stuff being in sync. > Thank you for the link though. I've found DBSprockets integration with > FormEncode very similar to mine. I'll take a deeper look into the > sourcecode for inspiration. > > Regards, > Wojciech > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
