deform looks cool.
Regarding
form
libraries:
I think approaches like tw.forms are indeed much too magically,
if you want to generate just a few forms.
However, if you are building a CRUD application, these libraries
provide
the necessary abstractions.
By the way, of course CRUD applications can (
On Apr 20, 2010, at 2:45 AM, Martin Stein wrote:
> For me, the main reasons why I like Django's forms are:
>
> a) html widgets (without having to maintain my own mako form widgets
> library, as in Mike's approach)
> b) I mostly understand the source code
> c) well documented
>
> Also, I've never
On Apr 20, 2:34 am, Ben Bangert wrote:
> On Apr 19, 2010, at 7:27 PM, cd34 wrote:
>
> > I looked at that, but, when you're developing a webapp that has 315
> > forms, that lack of automation seems to fly in the face of why I chose
> > a framework.
>
> Framework's don't automate programming for t
FormAlchemy and formencode are two things.
Have a look at FormAlchemy, it's quite nice, it has a set of default widgets
while you can extend it. It's originally mapped to SQLAlchemy objects, but
now works for CouchDB schemas, Zope.schema, and some others. It even has a
Pylons automatic admin inter
For me, the main reasons why I like Django's forms are:
a) html widgets (without having to maintain my own mako form widgets
library, as in Mike's approach)
b) I mostly understand the source code
c) well documented
Also, I've never really felt comfortable with formencode. I can't
really explain i
On Apr 19, 2010, at 7:27 PM, cd34 wrote:
> I looked at that, but, when you're developing a webapp that has 315
> forms, that lack of automation seems to fly in the face of why I chose
> a framework.
Framework's don't automate programming for the web, they provide a structure
around it. Framewo
On Apr 19, 5:59 pm, Ben Bangert wrote:
> I'm using the formlib approach that Mike Bayer wrote about
> here:http://techspot.zzzeek.org/?p=28
>
> I'm really rather liking it. It's substantially faster than toscawidgets or
> the formencode htmlfill method (it still uses Formencode for validation /
On Apr 19, 2010, at 2:29 PM, cd34 wrote:
> What is the attraction for using django forms? While I don't
> particularly like the ToscaWidgets method, and I semi-like the
> formencode method, I've always wondered what the fascination with the
> django forms was. I didn't really find it to be bette
On Apr 19, 8:32 am, Martin Stein wrote:
> Thanks for the hint. I've already read about Marcus' way of using
> Django forms (which is really nice), but his method means that you
> have the complete Django project as a dependency. I think some people
> might like a more light-weight approach. That's
Thanks for the hint. I've already read about Marcus' way of using
Django forms (which is really nice), but his method means that you
have the complete Django project as a dependency. I think some people
might like a more light-weight approach. That's why I'm trying to
extract the forms part only.
Might want to take a look at this thread:
http://groups.google.com/group/pylons-discuss/browse_thread/thread/2e88433546d97410
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to pylons-disc...@googlegroups.com
Hi all,
Recently, I've begun trying to extract Django's forms from Django
itself. I'd like to create a library that is usable in Pylons (and
elsewhere) without importing the rest of Django.
Can someone give me a hint on how to solve the i18n part? I have to
rip out Django's own translation stuff,
12 matches
Mail list logo
