Thanks for this. I fall into the target audience (hand coder?, hmm.. sounds incriminating..) Appreciate the not diving in, but giving context first.
Feedback, fwiw, after just reading, haven't had a chance to try yet (minor niggles or typos). - in a tutorial wouldn't the long form of commands be more explanatory? i.e. instead of paster create -t Pylons TWTutorial use paster create --template=TEMPLATE Pylons TWTutorial - 'the kind of form CSS fan-boys usually love' - remove this. I'am all for humor, but this just seems a little jarring. - 'I hope the above hints one' -> missing 'at' -> 'I hope the above hints at one'... - could you add a bit relating the html to the code here? Not being an expert, I'm curious to know if things such as 'class="even"' come from the ListForm class and/or whether this is fixed html output and/or expecting a related css. At the end of the tutorial you mention in the coming next: 'How to tweak the form's template to precisely control its layout.' So maybe just say that here, i.e. add a paragraph above 'Using the form in your application' that says: The layout of the form can be customized. 'How to tweak..' will be the subject of a following tutorial. - 'This is due a limitation' -> missing 'to' -> 'This is due to a limitation' - I condider -> I consider Other than that, this is a great help. Thanks again! > -----Original Message----- > From: [email protected] > [mailto:[EMAIL PROTECTED] On Behalf Of Alberto Valverde > Sent: Tuesday, October 23, 2007 3:01 PM > To: [email protected] > Subject: Re: UNS: Re: cleaner "ToscaWidgets" > > > Alberto Valverde wrote: > > Mike Orr wrote: > >> On 10/22/07, Max Ischenko <[EMAIL PROTECTED]> wrote: > >>> On 10/23/07, Mike Orr <[EMAIL PROTECTED]> wrote: > >>>>> Glad to hear this. :) So maybe I should reduce the > initial scope > >>>>> of the docs I have in mind and not dive directly into custom > >>>>> widgets but concentrate on how existing widgets are used? > >>>> Yes. Think in terms of somebody who has used another > Python form > >>>> library or has handcoded all their forms, and just wants > to use the > >>>> standard widgets at first. They'll be curious about any special > >>>> widgets TW provides such as a date picker, WSIWYG editor, combo > >>>> box, enhanced file uploader, etc -- things they've had > to struggle > >>>> with or do without in their other libraries. They don't want to > >>>> build custom widgets yet; they just want to build forms > that work. > >>> I'd say that even tutorial for a simple form (2-5 > fields, nothing > >>> fancy) would work if it highlights how TW is different from other > >>> approaches, like handcoding, and what it can give you. > >> Good point. Level 1: what Max said. Level 2: TW's megawidgets. > >> Level 3: making your own widgets. Level 4: making your > own composite > >> widgets (if that is different). > >> > > > > Ok, sounds good... I'll post in this thread a draft level 1&2 [1] > > tutorial later today. > > Until I can log on to the wiki I've posted the tutorial at my blog: > http://albertovalverde.es/twforms_tutorial1.html > > Feedback welcomed! :) > > Alberto > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
