[news.eclipse.platform.rcp] Re: Product based on features

[Peter Manahan <manahan@xxxxxxxxxxxxxxxxx>]

Steve Blass wrote:
> Hugo A. Garica wrote:
>
> > Ok
> >
> > Let me rephrase the question:
> >
> > What are pros and cons of using only plugin based configuration vs 
> > feature base configuration?
> >
> > -H
>
> The update manager requires features: game, set, match; right?

Only if you want to use the update manager and only if you want to 
update plugins. Once you move outside of updating just plugins you will 
probably need another update mechanism anyway. It all depends on what 
you need to update. For some eclipse based applications update manager 
is all that is needed. For others features and update manager become a 
hindrance.

It really depends on the application needs. For example if your 
application contains multiple RCP applications then Update Manager may 
not work for your update needs.

Some pro's of a feature based configuration.
-- pro: can use update manager to update most parts of your application
-- pro: features help package logical units of function nicely.
-- pro: the update configurator will read the features and based on the 
them provide the runtime the list of plugins to use. It simplifies the 
usage. The plugins to use may or may not be the latest version available 
in the plugins directory.

Pro's of a plugin based configuration
-- pro: full control over what is loaded by the runtime.
-- pro: full control over what is installed and updated (have to use a 
differnt method than Update Manager though)
-- pro: for small applications its simpler.
-- con: more complicated to manage.

There are pro's and con's to using Update Manager to update as well but 
thats a different topic.

Peter