I'm curious what others think is the TurbogearsBOB practice here ;)
When using widgets that get pulled into templates, how do you organize
the id and class tree and where do you put these?
Do you make divs in the page template and then call the widget? Or do
you put the id tags that will get used for dom swapping in the widget? I
seem to be suffering from too many layers of pointless divs right now
and am trying to clean house a bit.
Is this the Crustimony Proceedcake?
( in template )
<div id="block_cart">${cart_widget()}</div>
( in js )
- download new rendered widget via ajaxy goodness
- swapDOM or replace innerHTML of $("block_cart")
I notice the above means I have a bit of divitis going on, but maybe
that is neither here nor there. Would be interested in hearing thoughts
on what people have found best for organizing this kind of stuff.
Working my way through the new book, I feel pretty swamped with choices
of how to layout. Which is cool, but notes from the field would be good.
=)
Thanks
Iain
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
