[news.eclipse.tools] Re: -> Extension point mechanism (general concept q

["Martin Kersten" <martin.kersten@xxxxxxxxxxxxxxxxxxxxxxxx>]

> If you haven't already, you should look at some plugin.xml files from some
> of Eclipse's plugins. They contain the most concrete examples you'll find,
> particularly for your Q2.
I ran the box view and the multi editor page examples. I will do what
you suggested.

> Basically, the idea is that a plugin defines an extension point like
"View"
> and provides functionality that uses those extension points (like the
> ability to open views via the "Window->Show View" dialog). To tie into
that
> functionality, 3rd parties define an extension (a "View") and fulfill the
> required contract (such as implementing an interface). The plugin which
> defines the extension point can query the platform for all extenders at
> runtime and instantiate them (the platform can present the user with all
> defined Views).

Well that makes sence.

> Hope that helps,
Yes of cause.


Bye

Martin

> - Jared
>
> Martin Kersten wrote:
>
> > Hi there,
> >
> >     while studying the documentations and digging into the api's,
> > I seam to miss the big picture about the extension point mechanism.
> >
> > What I believe to know about:
> >
> > - The extension points are named 'connectors'.
> > - Every plugin specifies a xml-file about itself.
> > - Everytime the workbench starts it evaluates its plugin folder.
> > - A plugin is 'installed' within the system by reading its xml-file.
> > - The plugin xml-file is called manifest thouse describing the plugin.
> >
> > My Guesses:
> >
> > - Plugins naming the same extension point are grouped up
> >    by the system.
> > - A extension point must be unique within the system. To ensure this,
> >    including package names are best.
> >
> > My Questions:
> >
> > Q1: How does the plugin mechanism work for a concret example.
> >       Lets say, a view named an extension point of an editor.
> >       First scenario: The editor exsists while the view is opened.
> >       Second scenario: The editor does not exsists.
> >       What happens during startup and first run of the plugin?
> > Q2: A plugin wants to definie its own extension point. What is to do?
> >        What are the requirements?
> > Q3: Are there additional resources available I might have miss?
> >        I read the articles and the documentations about plugin.
> >
> > My Reason:
> >
> >     I just want to understand how the concept works. I just want to
> > add the concept to my every days knowledge.
> >
> >
> > Thanks,
> >
> > Martin
>