Home » Eclipse Projects » Eclipse Platform » Rich Client Platform (RCP) timeframe?
| Rich Client Platform (RCP) timeframe? [message #125348] |
Tue, 09 September 2003 09:56  |
Eclipse User |
|
|
|
Originally posted by: joerg.von.frantzius.artnology.nospam.com
Hi all,
does anybody know about planning on a timeframe for RCP? Will it be
included with Eclipse 3.0 final?
Thanks for any hints,
Jörg.
|
|
| | | | |
| Re: Rich Client Platform (RCP) timeframe? [message #126504 is a reply to message #126257] |
Wed, 10 September 2003 10:36  |
| Eclipse User |
|
|
|
Originally posted by: simon.ibm.oti.lab
Look at the 3.0 plan and bug report 40682 for more information about the
RCP. You can also look at the proposal documents on the ui team web page
( http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/plat form-ui-home/do
cs.html).
In short, the RCP plan item it to split the org.eclipse.ui plugin into
several plugins (some of this was done for 2.1). There will be a "generic"
workbench plugin that can be used by clients wanting to build applications
that are not IDEs. There will be another plugin using this generic workbench
to build the IDE of eclipse.
This RCP work definitely complements the Equinox work, it does not replace
it. The equinox project is dealing more with dynamic plug-ins, alternate
runtimes, services, security, etc The RCP work is to remove the IDE
specific pieces from the workbench, so the workbench is more useful to other
applications.
Simon :-)
"Kevin" <supreme_java_guru_1@yahoo.com> wrote in message
news:bjmcvc$nao$1@eclipse.org...
> What is this RCP about? I thought Equinox project was a sub-project to
make
> Eclipse a headless UI/plugin application shell. I have seen almost nothing
> in Equinox in the past few months, so is it still going on? Is it now RCP?
> Or what?
>
> "Simon Arsenault" <simon@ibm.oti.lab> wrote in message
> news:bjkpi6$4gv$1@eclipse.org...
> > The work is progressing. We would really like to have something ready
for
> > M4. We still need to get approval from the PMC to release these changes
> into
> > the HEAD stream and eventually to be part of 3.0 (we are breaking APIs
so
> > approval is required)
> >
> > Simon :-)
> >
> > "Joerg von Frantzius" <joerg.von.frantzius@artnology.nospam.com> wrote
in
> > message news:bjkm3t$ge$1@eclipse.org...
> > > Hi all,
> > >
> > > does anybody know about planning on a timeframe for RCP? Will it be
> > > included with Eclipse 3.0 final?
> > >
> > > Thanks for any hints,
> > > J
|
|
|
| Re: Rich Client Platform (RCP) timeframe? [message #128704 is a reply to message #125741] |
Sat, 13 September 2003 00:51 |
| Eclipse User |
|
|
|
Originally posted by: kk.dev.null
Chris Laffra wrote:
> Just out of curiosity...
> What are you planning to do with the RCP?
>
Just to add to the discussion, we have been waiting eagerly for 3.0
and the RCP. We are currently developing rich GUI application plugin
in anticipation (of course, it still works without the RCP, but we have
to hack the eclipse code to get rid off things we don't need).
We are currently heavily testing 3.0 and reporting bugs. And change
our apps according to API change.
We are developing an enterprise information security platform, with
rich GUI front-end application. One area of application is HIPAA-compliant
system in hospitals. We provide role-based access control to the
information,
and security (including encryption and digital signature) is critical.
Data are in XML format, and rendered on the fly in the eclipse desktop.
So we use heavily SWT, GEF, EMF.
Things we found are missing, which could have helped a lot:
- easy way to remove IDE-related components
- browser component : eclipse should have provided a browser
api and package the moz gecko engine (as a plugin) long time ago
- not enough of useful SWT widget, and the programming model is weird.
Widgets in Swing are nicer (sure, some of Swing components are pure
horror), such JTable. The SWT counterpart does not play nice with model
(as in MVC)
- Some of the UI components are considered internal use only, wonder
why, such the form components in update.ui.forms, and the scrollable
section used in PDE manifest editor. Ok, the scrollable section form
is horribly slow, but it's kinda nice for some app, and you can't trust to
call them as they are "internal" and might change without any reason.
- GEF widgets are sometimes weird too, and not enough. We end up
having to write a lot of these stuffs ourselves (as for SWT too).
- And did I mention documentation? Please, more documentation,
especially on the API. A lot of those APIs are not documented, just
the methods and parameters name, and we are expected to guess what
they do and how they work. We end up reading the code of all the
components we use to understand how to use them. And there are
components that probably could have helped us a lot, and we probably
didn't even know, coz they are documented, and sometimes, we just skipped.
- ability to unload plugins that are not used anymore, which is the
work of equinox, but the development of equinox seems to be "really"
slow compared to other eclipse projects. We currently don't have the
resources to look at this area yet, but we would like to get some hack
going to reduce resource consumption by eclipse.
Sorry for the long rant. Eclipse is good stuff :)
|
|
|
| Re: Rich Client Platform (RCP) timeframe? [message #129282 is a reply to message #128704] |
Mon, 15 September 2003 10:02 |
| Eclipse User |
|
|
|
Originally posted by: simon.ibm.oti.lab
Could you add your comments to bug report #36967
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=36967) so we do not lose
track of them
Simon :-)
"kk" <kk@dev.null> wrote in message news:bju7lr$7lo$1@eclipse.org...
> Chris Laffra wrote:
> > Just out of curiosity...
> > What are you planning to do with the RCP?
> >
>
> Just to add to the discussion, we have been waiting eagerly for 3.0
> and the RCP. We are currently developing rich GUI application plugin
> in anticipation (of course, it still works without the RCP, but we have
> to hack the eclipse code to get rid off things we don't need).
>
> We are currently heavily testing 3.0 and reporting bugs. And change
> our apps according to API change.
>
> We are developing an enterprise information security platform, with
> rich GUI front-end application. One area of application is HIPAA-compliant
> system in hospitals. We provide role-based access control to the
> information,
> and security (including encryption and digital signature) is critical.
> Data are in XML format, and rendered on the fly in the eclipse desktop.
> So we use heavily SWT, GEF, EMF.
>
> Things we found are missing, which could have helped a lot:
> - easy way to remove IDE-related components
> - browser component : eclipse should have provided a browser
> api and package the moz gecko engine (as a plugin) long time ago
> - not enough of useful SWT widget, and the programming model is weird.
> Widgets in Swing are nicer (sure, some of Swing components are pure
> horror), such JTable. The SWT counterpart does not play nice with model
> (as in MVC)
> - Some of the UI components are considered internal use only, wonder
> why, such the form components in update.ui.forms, and the scrollable
> section used in PDE manifest editor. Ok, the scrollable section form
> is horribly slow, but it's kinda nice for some app, and you can't trust to
> call them as they are "internal" and might change without any reason.
> - GEF widgets are sometimes weird too, and not enough. We end up
> having to write a lot of these stuffs ourselves (as for SWT too).
> - And did I mention documentation? Please, more documentation,
> especially on the API. A lot of those APIs are not documented, just
> the methods and parameters name, and we are expected to guess what
> they do and how they work. We end up reading the code of all the
> components we use to understand how to use them. And there are
> components that probably could have helped us a lot, and we probably
> didn't even know, coz they are documented, and sometimes, we just skipped.
> - ability to unload plugins that are not used anymore, which is the
> work of equinox, but the development of equinox seems to be "really"
> slow compared to other eclipse projects. We currently don't have the
> resources to look at this area yet, but we would like to get some hack
> going to reduce resource consumption by eclipse.
>
> Sorry for the long rant. Eclipse is good stuff :)
>
>
|
|
|
Goto Forum:
Current Time: Sun Jul 27 08:57:04 EDT 2025
Powered by FUDForum. Page generated in 0.04094 seconds |
Home