platform-ui-home/rcp-proposal/rich_client_platform_facilities.html
Parent Directory
|
Revision Log
Revision 1.11 -
(download)
(as text)
(annotate)
Mon Jan 12 03:38:47 2004 UTC (5 years, 10 months ago) by nick
Branch: MAIN
Changes since 1.10: +8 -1 lines
Mon Jan 12 03:38:47 2004 UTC (5 years, 10 months ago) by nick
Branch: MAIN
Changes since 1.10: +8 -1 lines
Updated browser example
<html> <head> <meta http-equiv="Content-Language" content="en-us"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> <meta name="ProgId" content="FrontPage.Editor.Document"> <title>Rich Client Platform Facilities</title> </head> <body> <h1>Eclipse Rich Client Platform UI</h1> <p>The rich client platform (RCP) is a major theme for Eclipse 3.0. This is the main plan item:</p> <blockquote> <p><b>Enable Eclipse to be used as a rich client platform.</b> Eclipse was designed as a universal tool integration platform. However, many facets and components of Eclipse are not particularly specific to IDEs and would make equal sense in non-IDE applications (e.g., window-based GUI, plug-ins, help system, update manager). The Eclipse Platform should factor out and segregate IDE-specific facilities (e.g., everything having to do with workspace resources) so that a subset of it can be used as a rich client platform for building applications. [Platform Core, Platform UI, Platform Update] [Theme: Rich client platform] (<a href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=36967">36967</a>)</p> </blockquote> <p>Additional plan items cover other important issues such as adding and removing plug-ins dynamically.</p> <p>Note: The following documents are under active development and are being updated by the Eclipse team on an ongoing basis to reflect the latest thinking. The goal is to carve a UI for the rich client platform out of the Eclipse Platform UI. By the nature of this kind of work, it's difficult to plan everything in advance of actually doing the work; so we're not even going to try. Instead, we are revising these documents as we incrementally make our way towards a satisfactory solution:</p> <ul> <li><a href="generic_workbench_summary.html">Executive Summary of the Eclipse Rich Client Platform UI</a> (includes excerpts from the documents below)</li> </ul> These changes are covered in the <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.eclipse.platform.doc.isv/porting/eclipse_3_0_porting_guide.html">Eclipse 3.0 Porting Guide</a>. The original porting for the generic workbench is <a href="generic_workbench_porting_guide.html">here</a>. <p>Articles: <ul> <li><a href="rcp_tutorial/tutorial1.html">Rich Client Platform Tutorial - Part 1</a></li> <li><a href="rcp_tutorial/tutorial2.html">Rich Client Platform Tutorial - Part 2</a></li> </ul> <p>Design documents:</p> <ul> <li><a href="generic_workbench_direction.html">Statement of Direction for the Eclipse Rich Client Platform UI</a></li> <li><a href="generic_workbench_approach.html">Eclipse Rich Client Platform UI - Proposed Approach</a></li> <li><a href="generic_workbench_overview.html">Overview of the Generic Workbench</a></li> <li><a href="generic_workbench_structure.html">Generic Workbench Plug-in Structure</a></li> </ul> <p>Examples:</p> <ul> <li>RCP Browser Example in project <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.ui.examples.rcp.browser"> org.eclipse.ui.examples.rcp.browser</a> in the Eclipse repository. <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.ui.examples.rcp.browser/readme.html"> Click here for the readme file.</a></li> </ul> </body> </html>
| help@eclipse.org | ViewVC Help |
| Powered by ViewVC 1.0.3 |
