Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » IMP » Eclipse 3.3.0 report
Eclipse 3.3.0 report [message #14616] Fri, 26 October 2007 14:50 Go to next message
Martin Schnabel is currently offline Martin SchnabelFriend
Messages: 17
Registered: July 2009
Junior Member
Hi there,
I am a student very interested in IMP. I working on a small project for
ActionScript 2 and now 3 (ASDT) as a hobby.

"IMP doesn't quite work under Eclipse 3.3 as of yet. We .. encourage
people to pitch in by doing things like testing IMP under 3.3 and
submitting bug reports, if not submitting patches."

I think working in 3.3 saves lots of time because of Mylyn and I also
think its also a great tool too encourage community and participations (I
love the context and focus). So I try to identify some problems an maybe
some solutions.

I run Ubuntu 7.10 with java-6-sun-1.6.0.03 JVM and Eclipse 3.3.0 as a test
Platform with code from today's head rev. I also evaluated IMP with WinXP
on Eclipse 3.2.2. As long as there is no bugzilla component for IMP I just
put it here.

-- missing HTMLTextPresenter
org.eclipse.imp.editor.UniversalEditor uses
org.eclipse.jdt.internal.ui.text.HTMLTextPresenter that moved to
org.eclipse.jface.internal.text.html.HTMLTextPresenter but is not
accessible because of plugin package restrictions (internal..)

In this case one can easily add the HTMLTextPresenter and the four
required Readers to the IMP codebase (same license).

-- invalid thread access on start-up
That is very easy fixed by wrapping the language registration in a
Runnable executed by the default display in
org.eclipse.imp.runtime.RuntimePlugin.earlyStartup().

org.eclipse.swt.SWTException: Invalid thread access
..
at
org.eclipse.imp.language.LanguageRegistry.registerLanguages( LanguageRegistry.java:208)
at
org.eclipse.imp.runtime.RuntimePlugin.earlyStartup(RuntimePl ugin.java:78)
..
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

-- (minor) default key binding conflict with subversive
ALT+CTRL+R is set to org.eclipse.imp.xform.findReplace and
org.polarion.team.svn.ui.command.CompareWithRevisionCommand

-- getAllPlugins()
org.eclipse.pde.internal.core.PluginModelManager.getAllPlugi ns is missing.
however there is a method getAllModels() with the same return type. no
solution because of the next problem.

-- use of internal packages
org.eclipse.imp.metatooling (especially org.eclipse.imp.extensionsmodel)
are using classes in the package org.eclipse.pde.internal.core. The
problem is internal should not be used by others. Since 3.3 Eclipse
started to use OSGi enforced package restriction. That means if not
explicit exported, the package will be inaccessible from other plug-ins.
Maybe this can be resolved by using the corresponding public interfaces
and a custom implementation. But I stop right here for today, I obviously
cant test any of the wizards without the extensionsmodel working.

Best regards
Martin Schnabel
Re: Eclipse 3.3.0 report [message #14649 is a reply to message #14616] Mon, 29 October 2007 12:21 Go to previous messageGo to next message
Robert M. Fuhrer is currently offline Robert M. FuhrerFriend
Messages: 294
Registered: July 2009
Senior Member
Hi Martin,

Thanks a lot; this is extremely helpful! With this sort of assistance,
we'll be up on 3.3 in no time! :-)

Martin Schnabel wrote:
> Hi there,
> I am a student very interested in IMP. I working on a small project for
> ActionScript 2 and now 3 (ASDT) as a hobby.
>
> "IMP doesn't quite work under Eclipse 3.3 as of yet. We .. encourage
> people to pitch in by doing things like testing IMP under 3.3 and
> submitting bug reports, if not submitting patches."
>
> I think working in 3.3 saves lots of time because of Mylyn and I also
> think its also a great tool too encourage community and participations
> (I love the context and focus). So I try to identify some problems an
> maybe some solutions.
>
> I run Ubuntu 7.10 with java-6-sun-1.6.0.03 JVM and Eclipse 3.3.0 as a
> test Platform with code from today's head rev. I also evaluated IMP with
> WinXP on Eclipse 3.2.2. As long as there is no bugzilla component for
> IMP I just put it here.
>
> -- missing HTMLTextPresenter
> org.eclipse.imp.editor.UniversalEditor uses
> org.eclipse.jdt.internal.ui.text.HTMLTextPresenter that moved to
> org.eclipse.jface.internal.text.html.HTMLTextPresenter but is not
> accessible because of plugin package restrictions (internal..)
>
> In this case one can easily add the HTMLTextPresenter and the four
> required Readers to the IMP codebase (same license).

You're right. We'll probably just copy the code over as you suggest.

> -- invalid thread access on start-up
> That is very easy fixed by wrapping the language registration in a
> Runnable executed by the default display in
> org.eclipse.imp.runtime.RuntimePlugin.earlyStartup().
>
> org.eclipse.swt.SWTException: Invalid thread access
> .
> at
> org.eclipse.imp.language.LanguageRegistry.registerLanguages( LanguageRegistry.java:208)
>
> at
> org.eclipse.imp.runtime.RuntimePlugin.earlyStartup(RuntimePl ugin.java:78)
> .
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

As you say, a trivial fix. Thanks for this one.

> -- (minor) default key binding conflict with subversive
> ALT+CTRL+R is set to org.eclipse.imp.xform.findReplace and
> org.polarion.team.svn.ui.command.CompareWithRevisionCommand

Yes, IIRC I put that binding in a long time ago to help while
testing the AST searching (which is still half-baked). We can
certainly remove this.

> -- getAllPlugins()
> org.eclipse.pde.internal.core.PluginModelManager.getAllPlugi ns is
> missing. however there is a method getAllModels() with the same return
> type. no solution because of the next problem.
>
> -- use of internal packages
> org.eclipse.imp.metatooling (especially org.eclipse.imp.extensionsmodel)
> are using classes in the package org.eclipse.pde.internal.core. The
> problem is internal should not be used by others. Since 3.3 Eclipse
> started to use OSGi enforced package restriction. That means if not
> explicit exported, the package will be inaccessible from other plug-ins.
> Maybe this can be resolved by using the corresponding public interfaces
> and a custom implementation. But I stop right here for today, I
> obviously cant test any of the wizards without the extensionsmodel working.

Obviously we're aware of this one. We've been trying to avoid simply
copying the PDE's plugin/extension model code, which provides a higher-
level means of manipulating plugins, but the PDE doesn't provide enough
API yet. We'll see what we can do to remove the internal package
dependencies.

Thanks again!

Cheers,
-- Bob

--------------------------------
Robert M. Fuhrer
Research Staff Member
Programming Technologies Dept.
IBM T.J. Watson Research Center

IMP Team Lead (http://eclipse-imp.sourceforge.net)
X10: Productivity for High-Performance Parallel Programming
(http://x10.sf.net)
Re: Eclipse 3.3.0 report [message #14771 is a reply to message #14649] Thu, 01 November 2007 19:59 Go to previous messageGo to next message
Martin Schnabel is currently offline Martin SchnabelFriend
Messages: 17
Registered: July 2009
Junior Member
Robert M. Fuhrer schrieb:
> Thanks a lot; this is extremely helpful!
You're welcome.

> Obviously we're aware of this one. We've been trying to avoid simply
> copying the PDE's plugin/extension model code, which provides a higher-
> level means of manipulating plugins, but the PDE doesn't provide enough
> API yet.
You might need an overview where these internal packages are used and
what for. I looked through the projects and wrote a list.

*org.eclipse.imp.analysis*
org.eclipse.imp.analysis.type.constraints.fastrep.BindingKey uses
org.eclipse.jdt.internal.core.util.KeyKind and
org.eclipse.jdt.internal.core.util.KeyToSignature to parse binding keys.
Since it is basically a light utility parser for binding key signatures
its not hard to implement a new one without dependencies to org.eclipse.jdt.

*org.eclipse.imp.preference*
org.eclipse.imp.preferences.wizards.NewPreferencesDialogWiza rdPage and
org.eclipse.imp.preferences.wizards.NewPreferencesSpecificat ionWizardPage
have a method getSchema(), that returns the restricted type
org.eclipse.pde.internal.core.schema.Schema. However it is only checkt
whether the schema exists so the method could be changed to boolean
hasSchema () { return fSchema != null; }

*org.eclipse.imp.prefspecs*
org.eclipse.imp.prefspecs.compiler.PrefspecsCompiler uses
org.eclipse.pde.internal.core.bundle.WorkspaceBundleModel to parse the
manifest.mf files.

*org.eclipse.imp.runtime*
org.eclipse.imp.language.LanguageRegistry uses
org.eclipse.ui.internal.registry.EditorRegistry, the IEditorRegistry
does not let you change or save the mappings. related:
org.eclipse.ui.internal.registry.EditorDescriptor,
org.eclipse.ui.internal.registry.FileEditorMapping

org.eclipse.imp.editor.ProblemsLabelDecorator uses
org.eclipse.jdt.internal.ui.viewsupport.ImageDescriptorRegis try and
org.eclipse.jdt.internal.ui.JavaPluginImages. related:
org.eclipse.jdt.internal.ui.JavaPlugin and
org.eclipse.jdt.internal.ui.viewsupport.ImageImageDescriptor

org.eclipse.imp.preferences.ProjectPreferencesTab uses
org.eclipse.jdt.internal.ui.preferences.ProjectSelectionDial og and all
detail dialogs in org.eclipse.imp.preferences.fields.details extend
org.eclipse.ui.internal.dialogs.ProductInfoDialog.

org.eclipse.imp.preferences.AdaptedProjectSelectionDialog accesses
org.eclipse.jdt.internal.ui.JavaPlugin getDialogSettings().

org.eclipse.imp.wizards.NewProjectWizardFirstPage uses
org.eclipse.jdt.internal.ui.wizards.NewWizardMessages for text messages
and org.eclipse.jdt.internal.ui.preferences.NewJavaProjectPrefer encePage.

org.eclipse.imp.wizards.NewProjectWizardSecondPage uses
NewWizardMessages as well and
org.eclipse.jdt.internal.corext.util.JavaModelUtil,
org.eclipse.jdt.internal.ui.util.CoreUtility,
org.eclipse.jdt.internal.ui.wizards.ClassPathDetector for java project
configuration.

*minor*
org.eclipse.imp.java.outliner.JavaOutliner uses
org.eclipse.jdt.internal.ui.JavaPluginImages for jdt images.
org.eclipse.imp.lpg.wizards.NewLanguageSupportWizardPage has an used
import to a pdt internal package.

I hope it will help a bit. I think many of these dependencies can be
implemented very easy. The only thing that seems to be a problem is the
EditorRegistry.

Best regards
Martin Schnabel
Re: Eclipse 3.3.0 report [message #16703 is a reply to message #14771] Sat, 23 February 2008 03:22 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: psanampu.cisco.com

hi,
did anybody resolved these issues ? Does anybody have imp working with
eclipse 3.3 yet ?

thanks
Prasad


"Martin Schnabel" <mb0@mb0.org> wrote in message
news:fgdb6g$te4$1@build.eclipse.org...
> Robert M. Fuhrer schrieb:
>> Thanks a lot; this is extremely helpful!
> You're welcome.
>
>> Obviously we're aware of this one. We've been trying to avoid simply
>> copying the PDE's plugin/extension model code, which provides a higher-
>> level means of manipulating plugins, but the PDE doesn't provide enough
>> API yet.
> You might need an overview where these internal packages are used and what
> for. I looked through the projects and wrote a list.
>
> *org.eclipse.imp.analysis*
> org.eclipse.imp.analysis.type.constraints.fastrep.BindingKey uses
> org.eclipse.jdt.internal.core.util.KeyKind and
> org.eclipse.jdt.internal.core.util.KeyToSignature to parse binding keys.
> Since it is basically a light utility parser for binding key signatures
> its not hard to implement a new one without dependencies to
> org.eclipse.jdt.
>
> *org.eclipse.imp.preference*
> org.eclipse.imp.preferences.wizards.NewPreferencesDialogWiza rdPage and
> org.eclipse.imp.preferences.wizards.NewPreferencesSpecificat ionWizardPage
> have a method getSchema(), that returns the restricted type
> org.eclipse.pde.internal.core.schema.Schema. However it is only checkt
> whether the schema exists so the method could be changed to boolean
> hasSchema () { return fSchema != null; }
>
> *org.eclipse.imp.prefspecs*
> org.eclipse.imp.prefspecs.compiler.PrefspecsCompiler uses
> org.eclipse.pde.internal.core.bundle.WorkspaceBundleModel to parse the
> manifest.mf files.
>
> *org.eclipse.imp.runtime*
> org.eclipse.imp.language.LanguageRegistry uses
> org.eclipse.ui.internal.registry.EditorRegistry, the IEditorRegistry does
> not let you change or save the mappings. related:
> org.eclipse.ui.internal.registry.EditorDescriptor,
> org.eclipse.ui.internal.registry.FileEditorMapping
>
> org.eclipse.imp.editor.ProblemsLabelDecorator uses
> org.eclipse.jdt.internal.ui.viewsupport.ImageDescriptorRegis try and
> org.eclipse.jdt.internal.ui.JavaPluginImages. related:
> org.eclipse.jdt.internal.ui.JavaPlugin and
> org.eclipse.jdt.internal.ui.viewsupport.ImageImageDescriptor
>
> org.eclipse.imp.preferences.ProjectPreferencesTab uses
> org.eclipse.jdt.internal.ui.preferences.ProjectSelectionDial og and all
> detail dialogs in org.eclipse.imp.preferences.fields.details extend
> org.eclipse.ui.internal.dialogs.ProductInfoDialog.
>
> org.eclipse.imp.preferences.AdaptedProjectSelectionDialog accesses
> org.eclipse.jdt.internal.ui.JavaPlugin getDialogSettings().
>
> org.eclipse.imp.wizards.NewProjectWizardFirstPage uses
> org.eclipse.jdt.internal.ui.wizards.NewWizardMessages for text messages
> and org.eclipse.jdt.internal.ui.preferences.NewJavaProjectPrefer encePage.
>
> org.eclipse.imp.wizards.NewProjectWizardSecondPage uses NewWizardMessages
> as well and org.eclipse.jdt.internal.corext.util.JavaModelUtil,
> org.eclipse.jdt.internal.ui.util.CoreUtility,
> org.eclipse.jdt.internal.ui.wizards.ClassPathDetector for java project
> configuration.
>
> *minor*
> org.eclipse.imp.java.outliner.JavaOutliner uses
> org.eclipse.jdt.internal.ui.JavaPluginImages for jdt images.
> org.eclipse.imp.lpg.wizards.NewLanguageSupportWizardPage has an used
> import to a pdt internal package.
>
> I hope it will help a bit. I think many of these dependencies can be
> implemented very easy. The only thing that seems to be a problem is the
> EditorRegistry.
>
> Best regards
> Martin Schnabel
Re: Eclipse 3.3.0 report [message #20056 is a reply to message #16703] Fri, 30 May 2008 21:14 Go to previous message
Stan Sutton is currently offline Stan SuttonFriend
Messages: 121
Registered: July 2009
Senior Member
Yes, IMP is working with Eclipse 3.3 and also (we believe) with 3.4 M5.
If you have not yet, please see the post of 28 May. This includes the
latest "trunk" code in the IMP SVN repository on Eclipse.org--and the
latest release through the IMP update site on Eclipse.org.

Regards,

Stan Sutton


prasad wrote:
> hi,
> did anybody resolved these issues ? Does anybody have imp working with
> eclipse 3.3 yet ?
>
> thanks
> Prasad
>
>
> "Martin Schnabel" <mb0@mb0.org> wrote in message
> news:fgdb6g$te4$1@build.eclipse.org...
>> Robert M. Fuhrer schrieb:
>>> Thanks a lot; this is extremely helpful!
>> You're welcome.
>>
>>> Obviously we're aware of this one. We've been trying to avoid simply
>>> copying the PDE's plugin/extension model code, which provides a higher-
>>> level means of manipulating plugins, but the PDE doesn't provide enough
>>> API yet.
>> You might need an overview where these internal packages are used and what
>> for. I looked through the projects and wrote a list.
>>
>> *org.eclipse.imp.analysis*
>> org.eclipse.imp.analysis.type.constraints.fastrep.BindingKey uses
>> org.eclipse.jdt.internal.core.util.KeyKind and
>> org.eclipse.jdt.internal.core.util.KeyToSignature to parse binding keys.
>> Since it is basically a light utility parser for binding key signatures
>> its not hard to implement a new one without dependencies to
>> org.eclipse.jdt.
>>
>> *org.eclipse.imp.preference*
>> org.eclipse.imp.preferences.wizards.NewPreferencesDialogWiza rdPage and
>> org.eclipse.imp.preferences.wizards.NewPreferencesSpecificat ionWizardPage
>> have a method getSchema(), that returns the restricted type
>> org.eclipse.pde.internal.core.schema.Schema. However it is only checkt
>> whether the schema exists so the method could be changed to boolean
>> hasSchema () { return fSchema != null; }
>>
>> *org.eclipse.imp.prefspecs*
>> org.eclipse.imp.prefspecs.compiler.PrefspecsCompiler uses
>> org.eclipse.pde.internal.core.bundle.WorkspaceBundleModel to parse the
>> manifest.mf files.
>>
>> *org.eclipse.imp.runtime*
>> org.eclipse.imp.language.LanguageRegistry uses
>> org.eclipse.ui.internal.registry.EditorRegistry, the IEditorRegistry does
>> not let you change or save the mappings. related:
>> org.eclipse.ui.internal.registry.EditorDescriptor,
>> org.eclipse.ui.internal.registry.FileEditorMapping
>>
>> org.eclipse.imp.editor.ProblemsLabelDecorator uses
>> org.eclipse.jdt.internal.ui.viewsupport.ImageDescriptorRegis try and
>> org.eclipse.jdt.internal.ui.JavaPluginImages. related:
>> org.eclipse.jdt.internal.ui.JavaPlugin and
>> org.eclipse.jdt.internal.ui.viewsupport.ImageImageDescriptor
>>
>> org.eclipse.imp.preferences.ProjectPreferencesTab uses
>> org.eclipse.jdt.internal.ui.preferences.ProjectSelectionDial og and all
>> detail dialogs in org.eclipse.imp.preferences.fields.details extend
>> org.eclipse.ui.internal.dialogs.ProductInfoDialog.
>>
>> org.eclipse.imp.preferences.AdaptedProjectSelectionDialog accesses
>> org.eclipse.jdt.internal.ui.JavaPlugin getDialogSettings().
>>
>> org.eclipse.imp.wizards.NewProjectWizardFirstPage uses
>> org.eclipse.jdt.internal.ui.wizards.NewWizardMessages for text messages
>> and org.eclipse.jdt.internal.ui.preferences.NewJavaProjectPrefer encePage.
>>
>> org.eclipse.imp.wizards.NewProjectWizardSecondPage uses NewWizardMessages
>> as well and org.eclipse.jdt.internal.corext.util.JavaModelUtil,
>> org.eclipse.jdt.internal.ui.util.CoreUtility,
>> org.eclipse.jdt.internal.ui.wizards.ClassPathDetector for java project
>> configuration.
>>
>> *minor*
>> org.eclipse.imp.java.outliner.JavaOutliner uses
>> org.eclipse.jdt.internal.ui.JavaPluginImages for jdt images.
>> org.eclipse.imp.lpg.wizards.NewLanguageSupportWizardPage has an used
>> import to a pdt internal package.
>>
>> I hope it will help a bit. I think many of these dependencies can be
>> implemented very easy. The only thing that seems to be a problem is the
>> EditorRegistry.
>>
>> Best regards
>> Martin Schnabel
>
>
Re: Eclipse 3.3.0 report [message #568663 is a reply to message #14616] Mon, 29 October 2007 12:21 Go to previous message
Robert M. Fuhrer is currently offline Robert M. FuhrerFriend
Messages: 294
Registered: July 2009
Senior Member
Hi Martin,

Thanks a lot; this is extremely helpful! With this sort of assistance,
we'll be up on 3.3 in no time! :-)

Martin Schnabel wrote:
> Hi there,
> I am a student very interested in IMP. I working on a small project for
> ActionScript 2 and now 3 (ASDT) as a hobby.
>
> "IMP doesn't quite work under Eclipse 3.3 as of yet. We .. encourage
> people to pitch in by doing things like testing IMP under 3.3 and
> submitting bug reports, if not submitting patches."
>
> I think working in 3.3 saves lots of time because of Mylyn and I also
> think its also a great tool too encourage community and participations
> (I love the context and focus). So I try to identify some problems an
> maybe some solutions.
>
> I run Ubuntu 7.10 with java-6-sun-1.6.0.03 JVM and Eclipse 3.3.0 as a
> test Platform with code from today's head rev. I also evaluated IMP with
> WinXP on Eclipse 3.2.2. As long as there is no bugzilla component for
> IMP I just put it here.
>
> -- missing HTMLTextPresenter
> org.eclipse.imp.editor.UniversalEditor uses
> org.eclipse.jdt.internal.ui.text.HTMLTextPresenter that moved to
> org.eclipse.jface.internal.text.html.HTMLTextPresenter but is not
> accessible because of plugin package restrictions (internal..)
>
> In this case one can easily add the HTMLTextPresenter and the four
> required Readers to the IMP codebase (same license).

You're right. We'll probably just copy the code over as you suggest.

> -- invalid thread access on start-up
> That is very easy fixed by wrapping the language registration in a
> Runnable executed by the default display in
> org.eclipse.imp.runtime.RuntimePlugin.earlyStartup().
>
> org.eclipse.swt.SWTException: Invalid thread access
> .
> at
> org.eclipse.imp.language.LanguageRegistry.registerLanguages( LanguageRegistry.java:208)
>
> at
> org.eclipse.imp.runtime.RuntimePlugin.earlyStartup(RuntimePl ugin.java:78)
> .
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

As you say, a trivial fix. Thanks for this one.

> -- (minor) default key binding conflict with subversive
> ALT+CTRL+R is set to org.eclipse.imp.xform.findReplace and
> org.polarion.team.svn.ui.command.CompareWithRevisionCommand

Yes, IIRC I put that binding in a long time ago to help while
testing the AST searching (which is still half-baked). We can
certainly remove this.

> -- getAllPlugins()
> org.eclipse.pde.internal.core.PluginModelManager.getAllPlugi ns is
> missing. however there is a method getAllModels() with the same return
> type. no solution because of the next problem.
>
> -- use of internal packages
> org.eclipse.imp.metatooling (especially org.eclipse.imp.extensionsmodel)
> are using classes in the package org.eclipse.pde.internal.core. The
> problem is internal should not be used by others. Since 3.3 Eclipse
> started to use OSGi enforced package restriction. That means if not
> explicit exported, the package will be inaccessible from other plug-ins.
> Maybe this can be resolved by using the corresponding public interfaces
> and a custom implementation. But I stop right here for today, I
> obviously cant test any of the wizards without the extensionsmodel working.

Obviously we're aware of this one. We've been trying to avoid simply
copying the PDE's plugin/extension model code, which provides a higher-
level means of manipulating plugins, but the PDE doesn't provide enough
API yet. We'll see what we can do to remove the internal package
dependencies.

Thanks again!

Cheers,
-- Bob

--------------------------------
Robert M. Fuhrer
Research Staff Member
Programming Technologies Dept.
IBM T.J. Watson Research Center

IMP Team Lead (http://eclipse-imp.sourceforge.net)
X10: Productivity for High-Performance Parallel Programming
(http://x10.sf.net)
Re: Eclipse 3.3.0 report [message #568783 is a reply to message #14649] Thu, 01 November 2007 19:59 Go to previous message
Martin Schnabel is currently offline Martin SchnabelFriend
Messages: 17
Registered: July 2009
Junior Member
Robert M. Fuhrer schrieb:
> Thanks a lot; this is extremely helpful!
You're welcome.

> Obviously we're aware of this one. We've been trying to avoid simply
> copying the PDE's plugin/extension model code, which provides a higher-
> level means of manipulating plugins, but the PDE doesn't provide enough
> API yet.
You might need an overview where these internal packages are used and
what for. I looked through the projects and wrote a list.

*org.eclipse.imp.analysis*
org.eclipse.imp.analysis.type.constraints.fastrep.BindingKey uses
org.eclipse.jdt.internal.core.util.KeyKind and
org.eclipse.jdt.internal.core.util.KeyToSignature to parse binding keys.
Since it is basically a light utility parser for binding key signatures
its not hard to implement a new one without dependencies to org.eclipse.jdt.

*org.eclipse.imp.preference*
org.eclipse.imp.preferences.wizards.NewPreferencesDialogWiza rdPage and
org.eclipse.imp.preferences.wizards.NewPreferencesSpecificat ionWizardPage
have a method getSchema(), that returns the restricted type
org.eclipse.pde.internal.core.schema.Schema. However it is only checkt
whether the schema exists so the method could be changed to boolean
hasSchema () { return fSchema != null; }

*org.eclipse.imp.prefspecs*
org.eclipse.imp.prefspecs.compiler.PrefspecsCompiler uses
org.eclipse.pde.internal.core.bundle.WorkspaceBundleModel to parse the
manifest.mf files.

*org.eclipse.imp.runtime*
org.eclipse.imp.language.LanguageRegistry uses
org.eclipse.ui.internal.registry.EditorRegistry, the IEditorRegistry
does not let you change or save the mappings. related:
org.eclipse.ui.internal.registry.EditorDescriptor,
org.eclipse.ui.internal.registry.FileEditorMapping

org.eclipse.imp.editor.ProblemsLabelDecorator uses
org.eclipse.jdt.internal.ui.viewsupport.ImageDescriptorRegis try and
org.eclipse.jdt.internal.ui.JavaPluginImages. related:
org.eclipse.jdt.internal.ui.JavaPlugin and
org.eclipse.jdt.internal.ui.viewsupport.ImageImageDescriptor

org.eclipse.imp.preferences.ProjectPreferencesTab uses
org.eclipse.jdt.internal.ui.preferences.ProjectSelectionDial og and all
detail dialogs in org.eclipse.imp.preferences.fields.details extend
org.eclipse.ui.internal.dialogs.ProductInfoDialog.

org.eclipse.imp.preferences.AdaptedProjectSelectionDialog accesses
org.eclipse.jdt.internal.ui.JavaPlugin getDialogSettings().

org.eclipse.imp.wizards.NewProjectWizardFirstPage uses
org.eclipse.jdt.internal.ui.wizards.NewWizardMessages for text messages
and org.eclipse.jdt.internal.ui.preferences.NewJavaProjectPrefer encePage.

org.eclipse.imp.wizards.NewProjectWizardSecondPage uses
NewWizardMessages as well and
org.eclipse.jdt.internal.corext.util.JavaModelUtil,
org.eclipse.jdt.internal.ui.util.CoreUtility,
org.eclipse.jdt.internal.ui.wizards.ClassPathDetector for java project
configuration.

*minor*
org.eclipse.imp.java.outliner.JavaOutliner uses
org.eclipse.jdt.internal.ui.JavaPluginImages for jdt images.
org.eclipse.imp.lpg.wizards.NewLanguageSupportWizardPage has an used
import to a pdt internal package.

I hope it will help a bit. I think many of these dependencies can be
implemented very easy. The only thing that seems to be a problem is the
EditorRegistry.

Best regards
Martin Schnabel
Re: Eclipse 3.3.0 report [message #569669 is a reply to message #14771] Sat, 23 February 2008 03:22 Go to previous message
prasad is currently offline prasadFriend
Messages: 22
Registered: July 2009
Junior Member
hi,
did anybody resolved these issues ? Does anybody have imp working with
eclipse 3.3 yet ?

thanks
Prasad


"Martin Schnabel" <mb0@mb0.org> wrote in message
news:fgdb6g$te4$1@build.eclipse.org...
> Robert M. Fuhrer schrieb:
>> Thanks a lot; this is extremely helpful!
> You're welcome.
>
>> Obviously we're aware of this one. We've been trying to avoid simply
>> copying the PDE's plugin/extension model code, which provides a higher-
>> level means of manipulating plugins, but the PDE doesn't provide enough
>> API yet.
> You might need an overview where these internal packages are used and what
> for. I looked through the projects and wrote a list.
>
> *org.eclipse.imp.analysis*
> org.eclipse.imp.analysis.type.constraints.fastrep.BindingKey uses
> org.eclipse.jdt.internal.core.util.KeyKind and
> org.eclipse.jdt.internal.core.util.KeyToSignature to parse binding keys.
> Since it is basically a light utility parser for binding key signatures
> its not hard to implement a new one without dependencies to
> org.eclipse.jdt.
>
> *org.eclipse.imp.preference*
> org.eclipse.imp.preferences.wizards.NewPreferencesDialogWiza rdPage and
> org.eclipse.imp.preferences.wizards.NewPreferencesSpecificat ionWizardPage
> have a method getSchema(), that returns the restricted type
> org.eclipse.pde.internal.core.schema.Schema. However it is only checkt
> whether the schema exists so the method could be changed to boolean
> hasSchema () { return fSchema != null; }
>
> *org.eclipse.imp.prefspecs*
> org.eclipse.imp.prefspecs.compiler.PrefspecsCompiler uses
> org.eclipse.pde.internal.core.bundle.WorkspaceBundleModel to parse the
> manifest.mf files.
>
> *org.eclipse.imp.runtime*
> org.eclipse.imp.language.LanguageRegistry uses
> org.eclipse.ui.internal.registry.EditorRegistry, the IEditorRegistry does
> not let you change or save the mappings. related:
> org.eclipse.ui.internal.registry.EditorDescriptor,
> org.eclipse.ui.internal.registry.FileEditorMapping
>
> org.eclipse.imp.editor.ProblemsLabelDecorator uses
> org.eclipse.jdt.internal.ui.viewsupport.ImageDescriptorRegis try and
> org.eclipse.jdt.internal.ui.JavaPluginImages. related:
> org.eclipse.jdt.internal.ui.JavaPlugin and
> org.eclipse.jdt.internal.ui.viewsupport.ImageImageDescriptor
>
> org.eclipse.imp.preferences.ProjectPreferencesTab uses
> org.eclipse.jdt.internal.ui.preferences.ProjectSelectionDial og and all
> detail dialogs in org.eclipse.imp.preferences.fields.details extend
> org.eclipse.ui.internal.dialogs.ProductInfoDialog.
>
> org.eclipse.imp.preferences.AdaptedProjectSelectionDialog accesses
> org.eclipse.jdt.internal.ui.JavaPlugin getDialogSettings().
>
> org.eclipse.imp.wizards.NewProjectWizardFirstPage uses
> org.eclipse.jdt.internal.ui.wizards.NewWizardMessages for text messages
> and org.eclipse.jdt.internal.ui.preferences.NewJavaProjectPrefer encePage.
>
> org.eclipse.imp.wizards.NewProjectWizardSecondPage uses NewWizardMessages
> as well and org.eclipse.jdt.internal.corext.util.JavaModelUtil,
> org.eclipse.jdt.internal.ui.util.CoreUtility,
> org.eclipse.jdt.internal.ui.wizards.ClassPathDetector for java project
> configuration.
>
> *minor*
> org.eclipse.imp.java.outliner.JavaOutliner uses
> org.eclipse.jdt.internal.ui.JavaPluginImages for jdt images.
> org.eclipse.imp.lpg.wizards.NewLanguageSupportWizardPage has an used
> import to a pdt internal package.
>
> I hope it will help a bit. I think many of these dependencies can be
> implemented very easy. The only thing that seems to be a problem is the
> EditorRegistry.
>
> Best regards
> Martin Schnabel
Re: Eclipse 3.3.0 report [message #570795 is a reply to message #16703] Fri, 30 May 2008 21:14 Go to previous message
Stan Sutton is currently offline Stan SuttonFriend
Messages: 121
Registered: July 2009
Senior Member
Yes, IMP is working with Eclipse 3.3 and also (we believe) with 3.4 M5.
If you have not yet, please see the post of 28 May. This includes the
latest "trunk" code in the IMP SVN repository on Eclipse.org--and the
latest release through the IMP update site on Eclipse.org.

Regards,

Stan Sutton


prasad wrote:
> hi,
> did anybody resolved these issues ? Does anybody have imp working with
> eclipse 3.3 yet ?
>
> thanks
> Prasad
>
>
> "Martin Schnabel" <mb0@mb0.org> wrote in message
> news:fgdb6g$te4$1@build.eclipse.org...
>> Robert M. Fuhrer schrieb:
>>> Thanks a lot; this is extremely helpful!
>> You're welcome.
>>
>>> Obviously we're aware of this one. We've been trying to avoid simply
>>> copying the PDE's plugin/extension model code, which provides a higher-
>>> level means of manipulating plugins, but the PDE doesn't provide enough
>>> API yet.
>> You might need an overview where these internal packages are used and what
>> for. I looked through the projects and wrote a list.
>>
>> *org.eclipse.imp.analysis*
>> org.eclipse.imp.analysis.type.constraints.fastrep.BindingKey uses
>> org.eclipse.jdt.internal.core.util.KeyKind and
>> org.eclipse.jdt.internal.core.util.KeyToSignature to parse binding keys.
>> Since it is basically a light utility parser for binding key signatures
>> its not hard to implement a new one without dependencies to
>> org.eclipse.jdt.
>>
>> *org.eclipse.imp.preference*
>> org.eclipse.imp.preferences.wizards.NewPreferencesDialogWiza rdPage and
>> org.eclipse.imp.preferences.wizards.NewPreferencesSpecificat ionWizardPage
>> have a method getSchema(), that returns the restricted type
>> org.eclipse.pde.internal.core.schema.Schema. However it is only checkt
>> whether the schema exists so the method could be changed to boolean
>> hasSchema () { return fSchema != null; }
>>
>> *org.eclipse.imp.prefspecs*
>> org.eclipse.imp.prefspecs.compiler.PrefspecsCompiler uses
>> org.eclipse.pde.internal.core.bundle.WorkspaceBundleModel to parse the
>> manifest.mf files.
>>
>> *org.eclipse.imp.runtime*
>> org.eclipse.imp.language.LanguageRegistry uses
>> org.eclipse.ui.internal.registry.EditorRegistry, the IEditorRegistry does
>> not let you change or save the mappings. related:
>> org.eclipse.ui.internal.registry.EditorDescriptor,
>> org.eclipse.ui.internal.registry.FileEditorMapping
>>
>> org.eclipse.imp.editor.ProblemsLabelDecorator uses
>> org.eclipse.jdt.internal.ui.viewsupport.ImageDescriptorRegis try and
>> org.eclipse.jdt.internal.ui.JavaPluginImages. related:
>> org.eclipse.jdt.internal.ui.JavaPlugin and
>> org.eclipse.jdt.internal.ui.viewsupport.ImageImageDescriptor
>>
>> org.eclipse.imp.preferences.ProjectPreferencesTab uses
>> org.eclipse.jdt.internal.ui.preferences.ProjectSelectionDial og and all
>> detail dialogs in org.eclipse.imp.preferences.fields.details extend
>> org.eclipse.ui.internal.dialogs.ProductInfoDialog.
>>
>> org.eclipse.imp.preferences.AdaptedProjectSelectionDialog accesses
>> org.eclipse.jdt.internal.ui.JavaPlugin getDialogSettings().
>>
>> org.eclipse.imp.wizards.NewProjectWizardFirstPage uses
>> org.eclipse.jdt.internal.ui.wizards.NewWizardMessages for text messages
>> and org.eclipse.jdt.internal.ui.preferences.NewJavaProjectPrefer encePage.
>>
>> org.eclipse.imp.wizards.NewProjectWizardSecondPage uses NewWizardMessages
>> as well and org.eclipse.jdt.internal.corext.util.JavaModelUtil,
>> org.eclipse.jdt.internal.ui.util.CoreUtility,
>> org.eclipse.jdt.internal.ui.wizards.ClassPathDetector for java project
>> configuration.
>>
>> *minor*
>> org.eclipse.imp.java.outliner.JavaOutliner uses
>> org.eclipse.jdt.internal.ui.JavaPluginImages for jdt images.
>> org.eclipse.imp.lpg.wizards.NewLanguageSupportWizardPage has an used
>> import to a pdt internal package.
>>
>> I hope it will help a bit. I think many of these dependencies can be
>> implemented very easy. The only thing that seems to be a problem is the
>> EditorRegistry.
>>
>> Best regards
>> Martin Schnabel
>
>
Previous Topic:BNF input
Next Topic:Update site - not updated?
Goto Forum:
  


Current Time: Mon Nov 24 01:17:42 GMT 2014

Powered by FUDForum. Page generated in 0.02154 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software