Ed Leafe wrote:
On Jun 7, 2006, at 1:18 PM, Paul McNett wrote:
This is a big problem, because we are basically relying on
introspection of live objects, and introspection can hog a lot of
resources, resulting in an unresponsive editor. Also, anything goes
with Python's dynamic objects, so there may always be cases of
infinite loops and unexpected behavior.
We might be able to define these at the class level, and cache those
definitions. I do that in the Class Designer: when a class is
instantiated for the first time, save off all its default values into a
dict with the class as the key; this only has to be done once per class
per the life of the app. We could make the editor 'smarter' by
pre-loading the most common properties, such as 'Form', and interpreting
others, such as 'Parent', 'Children', etc., individually instead of
relying on introspection every time to figure out what 'Parent' refers to.
I was thinking along those lines too. Perhaps this is another job for
embedded sqlite usage.
--
Paul McNett
http://paulmcnett.com
http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
