Hi, I have posted some notes on the way I use CRUD with pylons on the wiki : http://pylonshq.com/project/pylonshq/wiki/LaurentsNotes
HTH Laurent Alexandre CONRAD wrote: > > 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. > > I agree. But the documentation for the Pylons-beginners at it's actual > state is enough to get you going IMHO... You start feeling Pylons, see > how it works, understanding how your project is structured into the > different folders, making experiences with controllers and templates, > etc. I was a beginner myself a back at v0.8 (in web development in > general) and already the "getting started" _did_ get me started; well > enough for playing around with little light projects. > > I like Pylons much more than my Django experience but now I was to get > into heavier work with databases. Of course, I don't want to get into > work that I'll have to redo be because I'm not doing it the Pylons-ish way. > > > 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. > > Right. > > > btbytes.com > > 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! > > Yes, that's what I'm doing, sneaking info here and there and try to make > it work together... Although, as I'm not working full time on Pylons > project, when I get back to Pylons, it's kinda hard remembering how it > all fits together. Which makes me regret not having a "keep it under > your pillow" Pylons reference book. > > > 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). > > Yes, I'm aware of this. I meant "minimum redundancy". Of course, I need > to change my model and the validation schema that comes with it. > > > 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) > > It is true that these kind of hidden fileds would show up. But we can > probably get over that by adding some sub class called "class Meta:" in > your model (like in Django) where you could tell which fileds will be > shown are not. We could add even more meta data here to say which field > is destinated to which user or which group. > > > - Different model attributes may have different constraints, so you > > cannot dynamically apply changes from model to validation. > > As I said "I'd like to be able to change my models (and the validation > schema) to see changes dynamicly applied". But my idea is to spend most > of my time coding python controllers rather than myghty templates (or > what ever buffet knows). > > > 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. > > We'll probably come up with some more cool tips and ideas once we get > the CRUD basics clear and nested together. > > Regards, > -- > Alexandre CONRAD - TLV FRANCE > Research & Development --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
