|
Re: Struggling with IEditorInput [message #285666 is a reply to message #285665] |
Sun, 22 May 2005 19:27 |
Eclipse User |
|
|
|
Originally posted by: stephan.vern.chem.tu-berlin.de
Mike wrote:
> I'm just starting my first attempt at building an Eclipse plugin and after
> a few minor issues have hit a wall with the IEditorInput parameter to my
> IEditorPart.init implementation. The interface itself supplies no useful
> methods. In the debugger I can see that I'm actually being given a
> FileEditorInput which _does_ have useful methods, but despite what the
> debugger and docs say, I can't get at either an
> org.eclipse.ui.IFileEditorInput or an org.eclipse.ui.part.FileEditorInput
> - they don't show up in my workbench.jar dependency and attempts to import
> them into a .java file are reported as errors.
As far as I know IFileEditorInput is part of the
org.eclipse.core.resources .
So you must have a plugin dependency to this plugin, if you want to use
it. You can add an entry to the dependencies, if you edit your
plugin.xml.
Stephan Michels.
|
|
|
|
|
Re: Struggling with IEditorInput [message #285675 is a reply to message #285668] |
Mon, 23 May 2005 06:35 |
Eclipse User |
|
|
|
Originally posted by: bob.objfac.com
Mike wrote:
> Got it - it IS in the org.eclipse.ui{.part} PACKAGE, but I needed a
> dependency on the org.eclipse.ui.ide PLUGIN. My newbie mistake was
> assuming that there was some correlation between packages and plugin
> jars, whereas in fact the classes in a given package seem to be randomly
> scattered all over the place.
>
> Is there some straightforward way to find this kind of information,
> short of grepping the whole plugins directory tree? (Which is what I
> ultimately resorted to.)
Simplest way is to import all the installed plugins as projects (well,
that part isn't so simple, but a plugin developer should do it anyway)
then Open Type on the class and Show in Explorer.
That will show you the plugin the class is actually in.
Bob Foster
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02368 seconds