Hi Alex, Hmm. the way I see it, the book comprises 2 aspects: a) The Pylons-manual stuff, like chapter 1 - 5, for example... this aspect is important for Pylons-beginners b) The Pylons-"best practices" stuff, like "Common action layout" in chapter 7 or "Configuring SQLAlchemy with CRUD" in 8, for example. This part is more interesting for users who already have some Pylons-experience.
Personally, I think that in the end the "best practices"-stuff is at least equally important as the manual part, because it gives you guidance how to really go ahead in a project. That's why I think it is also important that Pylons-users write about their experiences and how they implemented things. A nice example is: btbytes.com (I can't reach the site at the moment, but it is a good pylons blog) You can read examples like these and learn from other peoples programming experience in general. I hope that more Pylons developers are going to do things like that, because it is really interesting! About your second part (the redundancy avoidance): I know what you mean, but I don't think it is possible at the moment to actively tie model, validation schema and form together (in such a way, that when you change one, the other change as well). What is more, I don't think that it makes sense to tie these together completely, because: - Not every attribute of your model class needs to appear in your form (for example an attribute "creationDate", which the controller might set automatically) - Different model attributes may have different constraints, so you cannot dynamically apply changes from model to validation. However, I think that form creation and validation are relatively close. I really miss a tool, that gives me the easy validation power of formencode and simplifies form creation (+validation error feedback) at the same time. On the other hand, I shouldn't complain, because formencode already does validation and error feedback... the form creation part might be annoying, but when you use webhelpers, you can reduce the amount of work. Cheers, Martin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
