[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cross-project-issues-dev] [Bug 185052] [europa]installable feature should contribute to capabilities prefs
|
Martin,
we're on the same line here: there are
2 points here
1 - optimize the number of plugin loaded
at startup
2 - give the end-user the possibility
to override default behavior by disabling any desired feature/project (which
would effectively prevent corresponding plugins to be loaded at startup)
Eric.
Eric JODET
Developer, Eclipse JDT Core
69, rue de la Vecquerie, 44600 Saint Nazaire
Phone : +33-(0)2 51 16 40 49 / 87 40 49 - Mobile +33-(0)6 70 75 76
83
e-Mail : eric_jodet@xxxxxxxxxx
"Oberhuber, Martin"
<Martin.Oberhuber@xxxxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
05/03/2007 01:53 PM
Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx> |
|
To
| "Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [cross-project-issues-dev] [Bug
185052] [europa]installable
feature should contribute to capabilities prefs |
|
Right... but I agree with Ed that
the responsibility for
defining the granularity seems
to be with the products
based on Eclipse (and not the
core framework, Eclipse itself).
Having a second level of enablers
("Capabilities of Capabilities",
or "Capability Enablers",
or "defined but currently hidden
Capabilities") seems like
an interesting idea.
Cheers,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
From: cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Eric
Jodet
Sent: Thursday, May 03, 2007 1:48 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] [Bug 185052] [europa]installable
feature should contribute to capabilities prefs
Ed,
the idea here is to find a way to optimize the number of plugins loaded
at startup.
As you may find out with other Eclipse based IBM Toolkits, europa may be
installed across the enterprise as the standard dev toolkit.
But some people may perform only (or mainly) Database work, whereas others
C/C++ or Java and so on...
Disabling unused features may help minimize the resources allocated when
using europa.
In fact, after installing a feature, the default would be to enable the
feature.
The idea here is to give the end-user the possibility to disable any additional
feature.
Eric.
Eric JODET
Developer, Eclipse JDT Core
69, rue de la Vecquerie, 44600 Saint Nazaire
Phone : +33-(0)2 51 16 40 49 / 87 40 49 - Mobile +33-(0)6 70 75 76
83
e-Mail : eric_jodet@xxxxxxxxxx
Ed Merks <merks@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
05/03/2007 12:29 PM
Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx> |
|
To
| Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
|
cc
| cross-project-issues-dev@xxxxxxxxxxx,
cross-project-issues-dev-bounces@xxxxxxxxxxx
|
Subject
| Re: [cross-project-issues-dev] [Bug
185052] [europa] installable feature should
contribute to capabilities prefs |
|
Eric,
For EMF we have capabilities defined in an example plugin. We ran
into
problems with providing these as an actual part of our standard feature
since IBM products wanted to define their own notion of what functions
fits
in what capability categories. So if the idea is that Europa will
now
deliver on the order of 20 or more categories out of the box, I'm not sure
that's a great idea. Is it possible to use capabilities to filter
out
capabilities themselves so they can be redefined differently by a client
who has their own notion of how best to group the function contributed
by
various Eclipse projects into categories of capability? I fear that
an
uncoordinated effort will just result in a hodgepodge of categories and
I
don't think EMF will be in a position to contribute to that (and reading
the bugzilla I don't think EMF loads plugins before their time is right).
So a word of caution, be careful what you ask for, you may get it.
I also wonder if people think it's realistic to ask others to ship their
features with their capabilities disabled. I know that when people
install
EMF directly they are really expecting it to be enabled and I'm sure every
project is in the same position in that regard. Is there a declarative
mechanism whereby products could change the default enablablement state
of
various capabilities?
Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265 (t/l 969)
Eric Jodet
<jodet.e@xxxxxx.c
om>
To
Sent by:
cross-project-issues-dev@xxxxxxxxxx
cross-project-iss
g
ues-dev-bounces@e
cc
clipse.org
Subject
[cross-project-issues-dev]
[Bug
05/03/2007 03:34
185052] [europa] installable
AM
feature should contribute
to
capabilities
prefs
Please respond to
Cross project
issues
<cross-project-is
sues-dev@eclipse.
org>
Hello,
please have a look at bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=185052.
As proposed by Daniel, I'm gonna open one individual bug per Europa project
/ feature.
The main idea here is to contribute the General / Capabilities in order
for
the user
to be able to enable/disable any project / feature individually, to prevent
multiple plugin loading at startup
as it's currently the case.
This would benefit the overall startup performance, as well as it might
improve/optimize resource usage after startup.
Thanks.
Eric.
Eric JODET
Developer, Eclipse JDT Core
69, rue de la Vecquerie, 44600 Saint Nazaire
Phone : +33-(0)2 51 16 40 49 / 87 40 49 - Mobile +33-(0)6 70 75 76
83
e-Mail : eric_jodet@xxxxxxxxxx
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev