Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: AW: [jdt-dev] JDT Goes PDE





Hi Thorsten,

if you dig deeper into RCP you will find that Eclipse is now running on an
OSGI based run-time.
OSGI defines an industry standard component model. In OSGI a bundle
corresponds to a module and
has a manifest. You can imagine that PDE evolves from a plug-in development
environment to also support OSGI bundles
(some basic bundle support is already provided by the latest version of
PDE).
However, the JDT should stick to its current vision and provide "pure" Java
tooling.

If you are interested in helping PDE evolve in this direction then I'm sure
that the PDE team is open
for your help.

--erich



                                                                       
             "SP/Fink                                                  
             Thorsten"                                                 
             <sptf@xxxxxxx>                                             To
             Sent by:                  <jdt-dev@xxxxxxxxxxx>           
             jdt-dev-admin@ecl                                          cc
             ipse.org                                                  
                                                                   Subject
                                       Re: AW: [jdt-dev] JDT Goes PDE  
             04/30/2004 10:43                                          
             AM                                                        
                                                                       
                                                                       
             Please respond to                                         
             jdt-dev@eclipse.o                                         
                    rg                                                 
                                                                       
                                                                       




Hi Erich,

thank you very much for responding to my mail. My knowledge of the RCP
approach has been very
limited, so I spent some hours going through the links that you sent me.

From what I see there I understand (please correct me if and where I am
wrong), in Eclipse
3.0 PDE it will be possible to develop J2SE Client applications. These
applications will be
built atop the Eclipse Generic Workbench, a UI platform which is at the
heart of Eclipse 3.0.

My vision is about J2SE client applications (with or without RCP), J2SE
server applications,
J2EE web application and full-blown J2EE applications.

Similarities as they might be, my vision runs orthogonal to yours --
everything is borrowed
from PDE but abstracted, because in my opinion, PDE answers many general
questions about
component orientation. Let me make up an acronym, for the sake of this
discussion: JCOA --
Java Component Oriented Architecture. JCOA is about how Java components
communicate
their essentials to the outside world (the keyword is manifest files),
giving other components
the possibility to use, configure and extend them.

The attached document shows how and why, in my opinion, JCOA and RCP run
orthogonal. Three categories
should be considered: JCOA Levels, the type of Java application and
infrastructure classes.

My vision is:

1. Eclipse JDT supports JCOA at all levels.
2. Eclipse provides a hook, so that Service Providers can provide
infrastructure classes at all JCOA
levels, just as Eclipse 3.0 will be playing the role of service provider
with the Generic Workbench.
This is "invitation rule" and "fair play rule" in my eyes.

There are so many applications using Eclipse which would profit
tremendously from Eclipse JDT provding
support just for the first three JCOA levels (or even the first two). IDE's
are "your bread and butter",
and you guys are so close to filling a gap which has been around for far
too long.

Cheers
Thorsten




-----Ursprüngliche Nachricht-----
Von: Erich Gamma [mailto:erich_gamma@xxxxxxxxxx]
Gesendet: Mittwoch, 28. April 2004 18:41
An: jdt-dev@xxxxxxxxxxx
Betreff: Re: AW: [jdt-dev] JDT Goes PDE






Hi Thorsten,

the vision you describe in the slideware looks very similar to the goals of
the 3.0 RCP effort:

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-ui-home/rcp-proposal/rich_client_platform_facilities.html

The idea is that you can use the Eclipse component model not only for IDE
development but for
general purpose Java development. The nice thing about the Eclipse RCP
approach is that
1) the existing Eclipse component model can be reused
2) the existing PDE tools can be used for general purpose
component-oriented
Java development.

--erich




             "SP/Fink
             Thorsten"
             <sptf@xxxxxxx>                                             To
             Sent by:                  <jdt-dev@xxxxxxxxxxx>
             jdt-dev-admin@ecl                                          cc
             ipse.org
                                                                   Subject
                                       AW: [jdt-dev] JDT Goes PDE
             04/28/2004 05:57
             PM


             Please respond to
             jdt-dev@eclipse.o
                    rg






Dear All,

as promised there is now an English version of the ppt available.

Cheers
Thorsten

Software Produktion
Verlag für Standesamtswesen GmbH
Hanauer Landstraße 197
60314 Frankfurt am Main
Telefon: 069.40 58 94-737
Telefax: 069.40 58 94-700
Email: sptf@xxxxxxx
www.vfst.de





_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-dev
(See attached file: JCOA_ideas.pdf)

Attachment: JCOA_ideas.pdf
Description: Binary data


Back to the top