Quoting "Justin Davis" <[email protected]>:
I consider one of the greatest assets of web.py is that it's small enough to read the code and actually understand everything that's going on. It's pretty cool that the render method for forms is less than 20 lines long. It's small enough that you can use it as a starting point for a new render method and not feel like you need to remove unneeded stuff first.
Yes, same for me. I use mainly classes derived web.py Form, but almost all of them with my own render methods. It's pretty easy and all my forms conform to W3C standards. They are very specialised for my application, however. The good thing is, that neither web.py nor my application tend to bloat. (I'm using this on an embedded system, which is why I didn't consider Django.) -- You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en.
