It is covered a bit, but then says to check the source on the book's website to see exactly what was done...of course, the code isn't on the website yet...
Seeing both the code and how it can be organized is very important. Off to the whatwhat trac site I go... Chris On 12/4/06, Jonathan LaCour <[EMAIL PROTECTED]> wrote: > > > Chris Cioffi wrote: > > > 1. Application specific widgets. For instance, if I've got a type of > > record that I need to display on lots of templates, what's the best > > way to proceed? Should I create a widget's package and include the > > widgets like I do forms? Or should I use <?python ...?> and directly > > import the widget? > > The section on WhatWhat Status should cover this fairly well. WhatWhat > uses widgets extensively, and they are pretty much *all* specific to > the application. Widgets help make things like AJAX really really > simple to do, and can help you minimize duplication. > > -- > Jonathan LaCour > http://cleverdevil.org > > > > > -- "A little government and a little luck are necessary in life, but only a fool trusts either of them." -- P. J. O'Rourke --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
