Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[platform-ui-dev] Rich Client Platform UI changes to be released to HEAD after integration build

Further to the changes announced below, the Platform UI, Text, and Help 
teams, as well as affected downstream teams, will be releasing changes to 
HEAD after this week's integration build.
The goal is to have the Platform UI, Text and Help changes released to 
HEAD by Wednesday afternoon, with downstream teams adapting to the changes 
over the rest of the week.
We aim to have everything working again in the Eclipse SDK in time for 
next week's integration build.

Nick


----- Forwarded by Nick Edgar/Ottawa/IBM on 11/03/2003 02:57 PM -----

Kevin Haaland/Ottawa/IBM@IBMCA 
Sent by: eclipse-dev-admin@xxxxxxxxxxx
10/21/2003 11:14 AM
Please respond to
eclipse-dev


To
platform-ui-dev@xxxxxxxxxxx, eclipse-dev@xxxxxxxxxxx, 
platform-dev@xxxxxxxxxxx
cc

Subject
[eclipse-dev] API implications of Eclipse Rich Client Platform UI work







As outlined in the 3.0 plan,  the eclipse team firmly believes in 
preserving API compatability. With this mindset the team has produced a 
propsal that results in a good overall Eclipse solution while keeping most 
API intact. There is a bugzilla report for this plan item and 
documentation available on the UI team's home page. 

The bugzilla report for this plan item is: 

        http://bugs.eclipse.org/bugs/show_bug.cgi?id=36967 


The summary of the proposed changes and porting guide are here: 

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

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



If you are interested in this work or are concerned about the proposed API 
changes I encourage you to review the available information and send your 
comments to the platform-ui-dev@xxxxxxxxxxx mailing list. 



/The Eclipse Platform Team


Back to the top