[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ui-dev] Clarifying activities in 3.0
|
Basically I mean that it is up to the product managers where it would go.
Whether that is a primary feature or not depends on the situation - it is
by no means a restriction.
I just want to discourage people adding activity definitions in the
plug-ins they are contributing to a larger product unless there is a
strong reason to.
Tod
Jeff McAffer/Ottawa/IBM@IBMCA
Sent by: platform-ui-dev-admin@xxxxxxxxxxx
01/13/2004 04:19 PM
Please respond to platform-ui-dev
To: platform-ui-dev@xxxxxxxxxxx
cc:
Subject: Re: [platform-ui-dev] Clarifying activities in 3.0
Can you clarify what you mean by "defined in the primary feature"?
Features have no presence in the runtime and under different configuration
managers may not even exist. As such, the only thing that can define
something is a plugin.
Jeff
Tod Creasey/Ottawa/IBM@IBMCA
Sent by: platform-ui-dev-admin@xxxxxxxxxxx
01/13/2004 03:06 PM
Please respond to
platform-ui-dev
To
platform-ui-dev@xxxxxxxxxxx
cc
Subject
[platform-ui-dev] Clarifying activities in 3.0
Looks like I generated some confusion with my last mail (sorry guys).
Activities will generally be defined in the primary feature of a product
(i.e. org.eclipse.platform). Plug-in developers would not normally do
this.
We are discouraging the definition of activities in plug-ins as it will
make the product managers job more challenging if they are forced to use
activities that were defined for them.
There of course may be cases where it does make sense to define them in
plug-ins but we expect this to be the exception not the rule. Eclipse will
likely have activities defined in the org.eclipse.platform primary
feature. We will do this once the product team has defined what they want.
Tod
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ui-dev
