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. Alberto [1] Since using "megawidgets", which I suppose refers to the WYSIWYG editor et al, is no different from a user's POV than using a simple text field. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
