On Jan 26, 1:39 pm, Terry Brown <[email protected]> wrote: > Not really sure how the fundamentals of OO arose from fixing Leo's menus :-)
The path is direct: I've spent most of the last week dumping Leo's key-related data structures (mostly dicts). It's not enough to know that a dict is a dict: I've got to know what the keys and values are, and if the values are lists, I had better know exactly what the types of list elements are. Worse, "overloading" the keys by "sneaking" in extra information just needlessly complicates everything. The code has to have special cases for keys such as '_hash' and '*entry-commands*'. It's a horror: in effect, the *value* of the key becomes an anonymous "type". In essence, the dicts are too low level: they should be instances of classes. Edward P.S. The task now is to demonstrate that Leo actually overrides settings properly. This is pretty hairy if the only data are the various dicts, but that's what I have just now. Later, after the tests pass, I'll revise the code (and the tests) to demonstrate that the improved code still works. EKR -- You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor?hl=en.
