Comments on: I Spy Menus

By: Wim Jongman

Wim Jongman — Sun, 07 Jun 2009 16:19:02 +0000

Very good. Thanks!

By: marc

marc — Thu, 19 Mar 2009 11:24:37 +0000

Chris, copy-n-paste menu URIs would be sweet. Anything the platform can do to help me answer the question “How do I put something [in this place]?”, where place is a menu, a toolbar, etc, is a big productivity enhancement.

thanks for the great work.

By: Madhu

Madhu — Thu, 19 Mar 2009 03:01:46 +0000

Hello Chris,

This is an excellent functionality. Many times in my eclipse coding life, I felt I wanted a similar functionality.

Regards,
Madhu

By: Chris Aniszczyk

Chris Aniszczyk — Wed, 18 Mar 2009 16:39:23 +0000

Marc, that is exactly the idea. WIthout the spy, the fastest information is generally to source plugin.xml files or source code. As of right now, the spy should give you all the information you need to populate a menu-related plugin.xml entry. I think it would be interesting to possibly supply menu URIs in the popup that you could just copy and paste…

Eugene, please file a bug against PDE and I’ll see what I can do.

Frederic, I’ve seen that project before but it operates a bit differently than the spy. I don’t think it displays the information in a friendly manner and if you’re looking for things like help context identifiers… it’s very difficult to find that using the tool.

By: Frederic Conrotte

Frederic Conrotte — Wed, 18 Mar 2009 15:25:21 +0000

Hi Chris,

Is this spy somehow equivalent to RCP Inspect ?

http://rcpinspect.sourceforge.net ?

Fred

By: Eugene Kuleshov

Eugene Kuleshov — Wed, 18 Mar 2009 14:51:32 +0000

Any chance to package an update site, so it could be used with Eclipse 3.4?

By: marc

marc — Wed, 18 Mar 2009 14:28:39 +0000

nice! So just to clarify for myself (a relative eclipse n00b), the idea here is that you’re a plugin developer and you want to contribute something to some other plugin’s menu. You can then use the menu spy to easily get the context identifier for use in your own plugin.xml. Is that the idea? Without the menu spy, what’s the fastest way to the same information?

And does the menu spy give you *everything* you need to know to correctly populate your plugin.xml?

The reason I ask is that I think stuff like this is *extremely* helpful especially for newer plugin programmers as it aids in their understanding of how everything fits together; but it’s less helpful if it only gives enough information such that an experienced plugin programmer would know what to do with it but an inexperienced plugin programmer would only be getting part of the info they need.

just a thought.