On May 10, 2:54 pm, "Edward K. Ream" <[email protected]> wrote:
> I think of this as "knowing where the bodies are buried." An > essential part of these documents will be explaining why some things > are, and likely must be, complex. Here is a brief overview: There are other bodies :-) I promise you, I'll uncover them all: I intend to discuss all of Leo's core modules and Leo's main gui modules, one by one. Comments and questions will be welcome any time on this thread. In fact, I encourage them. They will be the best way of clarifying subtle issues. I should briefly mention here the wrapper classes needed for communication between Leo's core and the gui plugins. I know that Ville is (rightly) concerned with this complexity. Besides the text wrappers, there are various base classes in leoFrame.py that get subclassed for each gui. There are two schools of thought here. It would indeed be possibly to eliminate some pretty complex code by using only the Qt gui. Otoh, the rigorous separation of Leo's core code from Leo's gui code has some benefits. And its safer. Who can say what gui will be dominant 5 or 10 years from now? Edward -- 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.
