On Mon, Oct 6, 2008 at 9:00 AM, Ville M. Vainio <[EMAIL PROTECTED]> wrote:
> I guess my point is - this issue is not worth thinking too much about > at the moment...it's better to...concentrate to more crucial things of getting > the Qt plugin working properly in the first place (tree updates, key > handling, menus, icons...) I agree completely. > Yeah, we'll see what works best. However, I wouldn't start shoehorning > the leo completion system to scintilla until it is evident that it's > actually needed. Again, it's better to let other people write code for > us and enjoy the flow ;-) Any gui plugin, including the Qt plugin, provides all of Leo's features merely by providing the adapter classes. In other words, one would have to change Leo's core *not* to get the default autocompletion behavior. Gui plugins know nothing about Leo's core, but they enable all of the core's features. This separation took a bit more than a year to accomplish. 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 -~----------~----~----~----~------~----~------~--~---
