| [News.eclipse.foundation] Re: What is the future of RCP? |
Secondly isn't it a little bit confusing if the welcome page of eclipse.org says Eclipse is used for:
- Enterprise Development -> "Ok, I understand"
- Embedded + Device Development -> "Ok, I understand"
- Equinox Portal (former RCP): "what the hell is Equinox?" (By the way: wasn't it just an implementation of OSGi? Now Equinox seems to be more a non-technical term)
I agree. I've opened http://bugs.eclipse.org/228421 to discuss.
Thanks for your input.
Denis
- ...
Finally it is to say that in the current status of the website I don't get it that Eclipse can be used for desktop application development too. In my humble opinion this has to be changed.
Kind regards, Robert
Mike Milinkovich wrote:"Robert Möstl" <robert.moestl@xxxxxxxxxxx> wrote in message news:ftvaln$r13$1@xxxxxxxxxxxxxxxxxxxx
I am in agreement with what Ian and Boris have already said, but just wanted to reinforce one item.
But will eclipse be an application platform in the future too?
This is the key question. And the answer is most emphatically *yes*. All that is happening is that the scope of Eclipse as an application integration platform is widening. We focused 100% on RCP when the projects were working on desktop application integration technologies. Now that we have projects working on server-side (Swordfish, EclipseLink, RAP) and device-side (eRCP) runtimes, the messaging is widening to accomodate that.
Put another way, RCP is now part of the Eclipse runtime story, rather than being *the* Eclipse runtime story.
We at the EMO always struggle with trying to deliver marketing messages that try to explain what is going on in the projects. Let's face it: we don't tell the projects what to do, so our marketing is largely post-facto. It is trying to explain where the projects have already headed. It's an interesting challenge. Especially since our marketing resources are so limited.
Is this helpful? Do you feel we are on the right track, or do we need to reconsider our approach?
--