>>> yary <not.com@...> seems to think that:
[ ... ]
>On Mon, May 12, 2008 at 6:06 PM, Ming-Wei Chang <mchang21@...> wrote:
>> I have tried the python support in cedet, and I think that it requires
>> more work.
>Speedbar does a good enough job of finding classes and methods. For
>example, it knows that "save2AltXML" is a method of "class VarLog" in
>file "VarLogDef.py" - however it took me a while to discover I needed
>C-c , J (shift-J) and not C-c , j to find a tag in any file- thought
>the batch parse hadn't worked out.
Hmm. That keeps coming up. If anyone has a suggestion on how to bind
the keys for this, let me know. Just because I pick something for a
keybinding doesn't mean it has to stay that way.
>The good thing is that semantic-complete-jump tells me that there are
>four "save2AltXML" methods in two files, whereas find-tags wouldn't
>tell me that. True, the autocomplete doesn't work much in this
>project, and semantic can't tell me which save2AltXML method will be
>called (not even sure if that's possible before runtime), but I'll
>live with that for now.
You have run into an interesting problem I don't have a good
user-facing story for. The semantic-complete-jump routines will find
any symbol most anywhere, and if you press TAB, it will show you which
symbol you have selected if there is a choice.
In the semantic-ia.el file, there are routines that use the analyzer
to get more information. In there is semantic-ia-fast-jump. This
will analyze the current context, and find exactly which of the 4
methods it might be, and jump there. This routine, however, does not
support typing in random names.
There is probably a happy middle ground somewhere, though I'm not sure
on how to get it coded up for a clear user interface.
I've tended to focus on getting the back end stuff parsing, storing,
and analyzing correctly. Many of the user interfaces in Semantic
right now just expose some corner of the more difficult logic. Making
a good user interface is time consuming to build and maintain, like
ECB. There is no way I could manage the back ends, and something as
complex as ECB. I would expect that the ultimate jump to a symbol
function could be similarly complex. Studying user patterns, how to
get to different goal destinations in the least number of keystrokes,
what symbology to use in the completion prompt, and keep it language
independent and dependent at the same time.
The confusion between the functions in CEDET that do this is
understandable, and Emacs will need a single super-jump/complete
function since this is a common new user issue.
Eric Ludlam: eric@...
Siege: http://www.siege-engine.com Emacs: http://cedet.sourceforge.net