On Mon, Oct 6, 2008 at 1:30 AM, Ville M. Vainio <[EMAIL PROTECTED]> wrote:
>> This is useful, but it doesn't solve the real problem, namely >> discovering the list of completions. Everything except that problem > > Finding completions for minibuffer is trivial. > > As far as completions for body pane go, it is probably best done by > scintilla (do not reinvent the wheel..). We must be talking about different things, or I am missing something really important. I just looked at the links that you gave recently: QQQ It seems Scintilla relies on externally generated api description files to provide autocompletion. Links that may be of interest" http://www.riverbankcomputing.co.uk/static/Docs/QScintilla2/classQsciAPIs.html#b0f824492bb0f3ca54edb4d46945a3de http://www.burgaud.com/scite-java-api/ http://scintilla.sourceforge.net/tags2api.py http://www.koders.com/python/fid7000B9C96CF2C6FB5BCE9DF700365C5B2A1F36A7.aspx?s=gtk#L53 QQQ These are interesting, and will be useful. I certainly agree that we want to use the Scintilla form of behind-the-scenes data. I wouldn't call implementing them trivial, though, especially if Leo is going to update information in the background in a separate thread. Moreover, it would be good for autocompletion to do the following: 1. Resolve the meaning of 'self'. For this the autocompleter code must know in what class the present node appears, which requires a scan of ancestor nodes, apparently. 2. Work in the presence of incomplete or syntactically incorrect functions or classes. Autocompletion is indeed much easier in the presence of 'live' objects on which to introspect. These objects are available in the IPython command loop, but they don't come nearly so easily in an editor. 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 -~----------~----~----~----~------~----~------~--~---
