|
| Re: Where to post/mail additions to the 3.0 porting guide? [message #243715 is a reply to message #243668] |
Sat, 22 May 2004 21:58   |
Eclipse User |
|
|
|
Originally posted by: pascal.ibm.canada
Michael,
This is very good idea. You can send a message with your discoveries on
the eclipse-dev mailing list, and / or enter corresponding bug reports
in the appropriate components.
PaScaL
Michael Keppler wrote:
> Hi all,
>
> I have finally taken the steps to convert my plugin collection to 3.0
> API by removing all deprecated methods and the compatibility layer.
> During that I found that the porting guide does not cover all actions I
> needed for conversion. How can I reach someone to add information to
> that porting guide?
>
> E.g setting default preferences is now done using an
> AbstractPreferenceInitializer but that is not documented in the guide
> and also not in the deprecated AbstractUiPlugin preference methods.
>
> Ciao, Michael.
|
|
|
|
| Re: Where to post/mail additions to the 3.0 porting guide? [message #243875 is a reply to message #243817] |
Sun, 23 May 2004 08:04 |
 Michael Keppler
Messages: 164
Registered: July 2009 |
Senior Member |
|
|
snpe schrieb:
> Hello Michael,
> Please, post to this news
Well, these are the things I remember and which may be useful for others
too:
* using an AbstractPreferenceInitializer from the
org.eclipse.core.runtime.preferences extension point instead of
AbstractUIPlugin.initDefaultPreferences(IPreferenceStore) or
AbstractUIPlugin.initDefaultPluginPreferences()
* The guide tells not to use getInstallUrl() anymore but instead to rely
on bundle.getEntry(). For me the most use cases of getInstallUrl() were
in methods to retreive plugin image descriptors (where the method code
was taken in that form from articles on the Eclipse corner page, so I
suspect that this code is in use in many plugins now). In those cases it
is easier to use the new method
AbstractUIPlugin.imageDescriptorFromPlugin(String,String) instead of
working with the bundle itself.
* for the optional part: PluginRegistry and Platform.getPluginRegistry
shall now be ported to ExtensionRegistry and getExtensionRegistry (but
this is documented in the JavaDoc at least)
* One thing where I have not yet found the converted version is the
constant IWorkbenchActionConstants.M_VIEW for creating the sub menu
"Open Perspective...". In the ActionFactory I see no corresponding field
and it is also not on the list of deprecated constants in the porting
guide.
I still had one specific problem during conversion, where I don't know
if it is relevant for others: In the constructor of my plugin class I
called the constructor of another class, which used the preference store
of my (just being created) plugin. In the compatibility layer this
worked fine, without compatibility layer my Eclipse threw exceptions
like "MyPluginName is not a valid bundle activator for bundle x.y" at a
high rate and shutdown my application immediately again. Maybe it is a
general recommendation not to call other constructors in the constructor
of the plugin class?
Ciao, Michael.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03439 seconds
] 
Search
Help
Register
Login
Home
