>The
fact
TG/TW
widgets
being
long-lived
singletons
is
something
that
>has
bugged
me
for
some
time...
it
does
complicate
much
some
things,
>eg,
disabling
fields
on
a
per
request
basis,
being
unable
to
store
This reminds me of something I noticed recently in TG1.0.3. My app contained a
set of similar list widgets which varied along 3 orthogonal dimensions:
- type of object being viewed
- type of security access required (read/write)
- single select or multiselect
I wrote a function which could generate a widget on the fly, but it didn't
work. In fact, if I took an existing, working widget class and returned it from
a function, it too ceased to work. Is there something about the current design
of TG widgets which prevents creating the classes on the fly?
Barry
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
