On Nov 3, 8:17 am, "Ville M. Vainio" <[EMAIL PROTECTED]> wrote:
> > Compromise is not an option. The qt plugin must pass all unit tests, > > and many of those test require full integration of headlines with > > Leo's core. This is the difference between prototype and finished > > code. > > It's always a tradeoff - simplicity vs. code reuse. Both are > defendable arguments, but personally I always go for simplicity > (because less code => less stuff that can break, faster operation, and > more graceful scaling to toolkit upgrades and new features). This is not a question of code reuse; it is a question of the qt plugin supporting Leo. There is, in fact, no choice: all unit tests must pass. Happily, as I've just reported in another thread, the fix involved a substantial simplification of hopeless code. It was hopeless because it involved state variables that are *never* valid in event-driven code. 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 -~----------~----~----~----~------~----~------~--~---
