On Mon, Oct 10, 2011 at 10:29 AM, Terry Brown <[email protected]> wrote:
>> One idea would be to define **interface classes** that define the >> desired api's. > > I thought you'd sort of tried to do that, with some tendrils of gui > specific stuff leaking through here and there because it's hard to > avoid. The api's leak a little. What I am wanting to avoid is a bunch of do-nothing methods in base or intermediate classes. Really, Leo's core uses one, and only one, text-widget interface. I would like to eliminate or or two middle-men. That's about all. 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.
