On Sat, Oct 4, 2008 at 9:59 PM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
> Here are some technical notes while they are still fresh in my mind: > The Window class must eventually migrate to the other gui classes. ... > Eventually I will probably have to shuffle the code to other classes, > or at the very least assign "official" ivars like c.frame, c.frame.tree, > c.frame.body to entities created in the Ui_MainWindow class. Almost immediately after writing this I realized that there is a better way. As Ville says, the Ui_MainWindow class should be left alone, and its own file. In the past, the only choices (I saw) for classes like leoQtTree were to "be" a qt tree or to "have" a qt tree. But there is another choice: to "refer" to a qt tree. This makes leoQtTree a two-way adapter class. It has two interfaces: one to Leo's core, the other to Ui_MainWindow. This Aha will decrease the work: there is no need to refactor the code produced by the gui designer. It greatly simplifies the actual code in the adapter classes, and it provides a new design pattern for Leo's gui plugins. 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 -~----------~----~----~----~------~----~------~--~---
