On 2/4/06, Max Ischenko <[EMAIL PROTECTED]> wrote: > > > > Another thing: the widget itself is no longer automatically > > provided to the template namespace. > > -1 on this change. I think widget.something is both cleaner (makes it > clear to the template's author where the variable come from) and > simpler (doesn't force developer to write trivial update_data method). > > But on the other hand, if it's needed for threadsafety...so be it.
Actually, because of the instance locking mechanism, threadsafety probably isn't a valid enough concern. The other plus that came out of this plan (which is not yet implemented, but also not hard) is the ability to override everything at display() time. Of course, many things simply don't need to be overridden at display() time. I haven't been certain about this change all along, so I'm willing to put widget back in the namespace. Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
