For the last several days I have been wondering whether it would possible to remove many of Leo's so-called official ivars. LeoDocs.leo has details, in case you are wondering what they are. The idea was that removing them might simplify Leo's too-complex startup code.
This morning I even took a close look at pyzo's ivars. They are simpler than Leo's, and pyzo's code that instantiates various gui elements is simpler than Leo's. But on my walk I saw that, Doh!, Leo is a scripting environment! Ivars such as c.frame.body.wrapper are *necessary* and *useful *for many scripts. It would be folly to remove them. So I appear to have been suffering an unnecessary case of pyzo envy :-) The lesson, for *all* of Leo's devs, is that quite a bit of Leo's complexity arises because, yes, Leo does a lot more than pyzo. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/827795d6-41c8-4daa-a793-ef1b5ad246c1%40googlegroups.com.
