| [ANN] Equinox: a new Eclipse Technology Project [message #427] |
Wed, 19 February 2003 03:49  |
Eclipse User |
|
|
|
Originally posted by: jeff_mcaffer_REMOVE.ca.ibm.com
This is to announce the start of Equinox (http://eclipse.org/equinox), a new
Eclipse Technology project.
The goal of the Equinox project is to experiment with techniques for
broadening the range of Eclipse platform runtime configurations. For
example, the Eclipse plugin model is static; there is no discussion of
practices and tools for managing/reducing interplugin dependencies; service
discovery is not covered and the component distribution mechanism is
non-standard.
These issues do not severely impact the usefulness of Eclipse as a
development tool platform but they do affect the use of Eclipse in more
constrained environments (e.g., handheld devices, IT managed environments,
mass-appeal applications etc.). The Equinox project will investigate such
issues and develop approaches which are practical and applicable to the main
Eclipse code base.
Check out http://eclipse.org/equinox for more information.
|
|
|
| Re: [ANN] Equinox: a new Eclipse Technology Project [message #429 is a reply to message #427] |
Wed, 19 February 2003 15:27  |
| Eclipse User |
|
|
|
Originally posted by: burner.zclipse.org
Jeff McAffer wrote:
> This is to announce the start of Equinox (http://eclipse.org/equinox), a new
> Eclipse Technology project.
>
> The goal of the Equinox project is to experiment with techniques for
> broadening the range of Eclipse platform runtime configurations. For
> example, the Eclipse plugin model is static; there is no discussion of
> practices and tools for managing/reducing interplugin dependencies; service
> discovery is not covered and the component distribution mechanism is
> non-standard.
What sorts of deliverables does this project plan on producing?
Are you talking about rewriting core packages and providing patches?
Is Equinox a branch of Eclipse, or is it something entirely different?
mike
>
> These issues do not severely impact the usefulness of Eclipse as a
> development tool platform but they do affect the use of Eclipse in more
> constrained environments (e.g., handheld devices, IT managed environments,
> mass-appeal applications etc.). The Equinox project will investigate such
> issues and develop approaches which are practical and applicable to the main
> Eclipse code base.
>
> Check out http://eclipse.org/equinox for more information.
>
>
>
|
|
|
| Re: [ANN] Equinox: a new Eclipse Technology Project [message #441 is a reply to message #427] |
Wed, 19 February 2003 16:31 |
| Eclipse User |
|
|
|
Originally posted by: dominic.nospam.com
I cannot express my joy ! This is unbeleivibly important. The platform
contains so many things that are unecessary for vertical market type
application. Thumbs up for this effort.
"Jeff McAffer" <jeff_mcaffer_REMOVE@ca.ibm.com> wrote in message
news:b2ut85$tgd$1@rogue.oti.com...
> This is to announce the start of Equinox (http://eclipse.org/equinox), a
new
> Eclipse Technology project.
>
> The goal of the Equinox project is to experiment with techniques for
> broadening the range of Eclipse platform runtime configurations. For
> example, the Eclipse plugin model is static; there is no discussion of
> practices and tools for managing/reducing interplugin dependencies;
service
> discovery is not covered and the component distribution mechanism is
> non-standard.
>
> These issues do not severely impact the usefulness of Eclipse as a
> development tool platform but they do affect the use of Eclipse in more
> constrained environments (e.g., handheld devices, IT managed environments,
> mass-appeal applications etc.). The Equinox project will investigate such
> issues and develop approaches which are practical and applicable to the
main
> Eclipse code base.
>
> Check out http://eclipse.org/equinox for more information.
>
>
>
|
|
|
| Re: [ANN] Equinox: a new Eclipse Technology Project [message #454 is a reply to message #429] |
Thu, 20 February 2003 01:48 |
| Eclipse User |
|
|
|
Originally posted by: jeff_mcaffer_REMOVE.ca.ibm.com
Mike,
You have it basically right. Equinox delivers worked solutions to a
particular set of problems (e.g., dynamic plugins) to the Eclipse platform
team. The platform team takes this input pretty much like they take all
input. Of course, Platform team members are involved in Equinox so the
things produced should be in line with what the Platform needs/wants.
As for branching etc, yes, effectively Equinox is a branch. The project is
structured such that the branch will be frequently synchronized and will not
take on a life of its own.
Check out the web site for more information.
Jeff
"Michael R Head" <burner@zclipse.org> wrote in message
news:b3065o$rn7$1@rogue.oti.com...
> Jeff McAffer wrote:
> > This is to announce the start of Equinox (http://eclipse.org/equinox), a
new
> > Eclipse Technology project.
> >
> > The goal of the Equinox project is to experiment with techniques for
> > broadening the range of Eclipse platform runtime configurations. For
> > example, the Eclipse plugin model is static; there is no discussion of
> > practices and tools for managing/reducing interplugin dependencies;
service
> > discovery is not covered and the component distribution mechanism is
> > non-standard.
>
> What sorts of deliverables does this project plan on producing?
> Are you talking about rewriting core packages and providing patches?
> Is Equinox a branch of Eclipse, or is it something entirely different?
>
> mike
>
> >
> > These issues do not severely impact the usefulness of Eclipse as a
> > development tool platform but they do affect the use of Eclipse in more
> > constrained environments (e.g., handheld devices, IT managed
environments,
> > mass-appeal applications etc.). The Equinox project will investigate
such
> > issues and develop approaches which are practical and applicable to the
main
> > Eclipse code base.
> >
> > Check out http://eclipse.org/equinox for more information.
> >
> >
> >
>
|
|
|
| Re: [ANN] Equinox: a new Eclipse Technology Project [message #504 is a reply to message #427] |
Thu, 20 February 2003 17:01 |
| Eclipse User |
|
|
|
Originally posted by: ogruber.us.ibm.com
Very exciting time Jeff... I want to start different threads of discussion
about
what we think needs improvements or change in the Eclipse platform.
I know that we have people with different backgroungs and knowledge
in this newsgroup, probably different interests and agendas too :-)
So I would like to start three threads of discussions.
1) Component model
2) Self-hosting
3) Dynamic plug-ins
The first two are below the plug-in registry level and may impact how
plug-ins are defined, managed locally, and delivered. They will certainly
include some tooling discussions as well. The third is about how
dynamic loading/unloading of plug-ins will be exposed to plug-in developer,
focusing on extensions and extension points.
I expect the postings to be educational at first... We have quite different
communities involved with different knowledge of Eclipse and different
ideas about relevant technologies, frameworks, or even open standards.
I know for a fact that we have people from the Eclipse community (obvious
:-)
and also from the OSGi community (www.osgi.org). So I hope everyone
will be understanding at first and bare with educational postings.
I will start with an Eclipse platform quick review... corresponding to each
thread...
and I will outline some aspects that I believe need scrutinity, change, or
evolution.
This is intended to bootstrap the discussions... and also hopefully organize
them
a bit... I want to take this opportunity to welcome active participation.
Best regards,
Olivier.
"Jeff McAffer" <jeff_mcaffer_REMOVE@ca.ibm.com> wrote in message
news:b2ut85$tgd$1@rogue.oti.com...
> This is to announce the start of Equinox (http://eclipse.org/equinox), a
new
> Eclipse Technology project.
>
> The goal of the Equinox project is to experiment with techniques for
> broadening the range of Eclipse platform runtime configurations. For
> example, the Eclipse plugin model is static; there is no discussion of
> practices and tools for managing/reducing interplugin dependencies;
service
> discovery is not covered and the component distribution mechanism is
> non-standard.
>
> These issues do not severely impact the usefulness of Eclipse as a
> development tool platform but they do affect the use of Eclipse in more
> constrained environments (e.g., handheld devices, IT managed environments,
> mass-appeal applications etc.). The Equinox project will investigate such
> issues and develop approaches which are practical and applicable to the
main
> Eclipse code base.
>
> Check out http://eclipse.org/equinox for more information.
>
>
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05995 seconds
] 
Search
Help
Register
Login
Home
