Thread: [Boa Constr] code-completion feature requests
Status: Beta
Brought to you by:
riaan
From: Tim D. <ti...@re...> - 2004-04-16 07:49:42
|
------------------------------------------------------ Code completion for a class object currently doesn't pick up: * attributes assigned & declared in the class body: class MyClass(object): =09string=3D"" =09shared_list=3D[] * attributes from parent classes (in other modules, even if those modules are loaded into the shell). ------------------------------------------------------ Code completion for module-level scope doesn't pick up: * modules imported under a different name import mymodule as mymod import Tkinter as tk (hah! why would you do that in boa (see below)*) * names imported from a module (or modules imported from a package) from mymodule import myfunction from mymodule import MY_CONSTANT from mymodule import * (except where mymodule is a wx package...) from mypackage import mymodule (import mypackage.mymodule as mymodule) ------------------------------------------------------ NB: I use boa for editing tk-based guis, because once you've got used to an a good ide, you don't want to switch, do you? |
From: Riaan B. <riaan@e.co.za> - 2004-05-04 13:25:33
|
Hi Tim, Tim Diggins wrote: > ------------------------------------------------------ > Code completion for a class object currently doesn't pick up: > > * attributes assigned & declared in the class body: > > class MyClass(object): > string="" > shared_list=[] > > * attributes from parent classes (in other modules, even if those modules > are loaded into the shell). Yes, unfortunately class attributes aren't handled by pyclbr and it is very tricky to add support for them. (They are currently supported only directly after the class statement so that Boa can pick up _custom_classes) It would be a *very* welcome patch if someone could add this to moduleparse.py > > ------------------------------------------------------ > Code completion for module-level scope doesn't pick up: > > * modules imported under a different name > > import mymodule as mymod Yes, this is a feature request on the SourceForge site too. I hope to get to it soon. > import Tkinter as tk (hah! why would you do that in boa (see below)*) > > * names imported from a module (or modules imported from a package) > > from mymodule import myfunction This works. > from mymodule import MY_CONSTANT This works. > from mymodule import * (except where mymodule is a wx package...) This will never work. > from mypackage import mymodule (import mypackage.mymodule as mymodule) This works. Not sure what your problem is with the above? The parser correctly picks up those names as imported names. It does not know their types or deeper info about them (so cannot provide completion on attrs or methods) if that is what you are actually referring to? > ------------------------------------------------------ > NB: I use boa for editing tk-based guis, because once you've got used to > an a good ide, you don't want to switch, do you? Nope! Boa wan't to be tk friendly, honest! It even supports debugging tkinter apps. Cheers, Riaan. |