Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] How to start my plugin when C editor is started?
If the CEditor provides any extension points (it must?), then you could pick one and provide a dummy extension that points to an empty class in your plugin. When the CEditor loads your extension, your class should be instantiated, which should in turn activate your plugin (make sure this option is checked in the MANIFEST.MF).
Loading of extensions is often deferred until they are needed. You would need to pick an extension-point that is activated by the time the CEditor is opened. 

-Andrew

On 11-03-30 01:28 AM, Petri Tuononen wrote:

  That might be tricky, because plug-ins are not usually meant to be
activated like that. However you are able to activate your plug-in as
early as workbench start (not recommended though) by extending
org.eclipse.ui.startup and implement IStartup interface. You must also
call earlyStartup method. More descriptive instructions here:
http://wiki.eclipse.org/FAQ_Can_I_activate_my_plug-in_when_the_workbench_starts%3F
There's always another option which is to replace the C editor with your
own implementation although this might be quite inelegant solution.

Petri

On 03/30/2011 12:33 PM, wooyoung.cho wrote:

I want my plugin to be activated(loaded) not just enabled.
Now the user should press a button. But I'm looking for a way to
activate it automatically when C editor is opened.

---- On Wed, 30 Mar 2011 00:06:37 +0900 *Petri Tuononen
<petri.tuononen@xxxxxxxxx <mailto:petri.tuononen@xxxxxxxxx>>* wrote ----

    When the plug-in is installed the feature is enabled. The
    additions should then be visible on C editor.

    Petri

    On 29.3.2011 14:50, wooyoung.cho wrote:

    Hi,
    I'm writing my own plugin which depends on CDT. It adds
    additional functionality to C editor, so it needs to be started
    while C editor is started.
    Is there an appropriate extension point provided by CDT for this
    purpose?
    Or any other suggestions?

    Thanks,
    Cho.


    _______________________________________________ cdt-dev mailing
    list cdt-dev@xxxxxxxxxxx <mailto:cdt-dev@xxxxxxxxxxx>
    https://dev.eclipse.org/mailman/listinfo/cdt-dev


    _______________________________________________
    cdt-dev mailing list
    cdt-dev@xxxxxxxxxxx <mailto:cdt-dev@xxxxxxxxxxx>
    https://dev.eclipse.org/mailman/listinfo/cdt-dev



_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev




_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

Back to the top