Hi people, I'm reading this conversation and I thought this might interest a few of you Pylonauts and form projects starters.
FormAlchemy is actually running into a core redesign phase. A few ideas have been exchanged for now on the list (mostly about the API). I'm looking how things are being done around, what's lacking and what people like. Feel free to join the list and provide how you see things. Jonathan Vanasco wrote: > I don't see why you need to integrate with sqlalchemy at all though > > Something that I would like to see is to see good support defaults > > In my mind, defaults come from 2 places: > a- validated get/post data that is redisplayed > b- application generated info ( db pull? ) FormAlchemy is meant to reflect SQLAlchemy objects into HTML. Although, I'm thinking of doing things the other way around. FormAlchemy becomes harsh when it comes to non DB fields as it was not design with that in mind. So I'd like to do forms well, with a cool API à la SA for manipulating forms, then add native SQLAlchemy comprehension for SA models. Form frameworks are a big thing these days but none seem to have fully pleased users. This is not advertising for you to use FormAlchemy as I have not much to offer right now. Everyone likes to do their own form receipt and these merging form frameworks with different designs and philosophy can only bring richness and diversity to the community. Regards, -- Alexandre CONRAD --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
