[platform-ui-dev] Re: [platform-text-dev] RCP proposal - extension point

["Nick Edgar" <Nick_Edgar@xxxxxxxxxx>]

We will not be going ahead with any concrete refactoring for the Rich 
Client Platform for M2.  The plan for M2 is to have a detailed design 
document which other teams can review.  Since the Text and UI components 
are currently so tightly bound, we will be working with the Text team 
before M2 to sort out the relevant details.  The aim is to have Platform 
Text as a completely separable and optional component from the RCP, 
although it would be included by the IDE Workbench.  Any extension points 
owned by Text would be moved out of org.eclipse.ui (or the equivalent in 
the RCP world) and into the Text plugins.

Nick





Kai-Uwe Maetzel/Zurich/IBM@IBMCH
Sent by: platform-text-dev-admin@xxxxxxxxxxx
07/02/2003 12:08 PM
Please respond to platform-text-dev
 
        To:     platform-ui-dev@xxxxxxxxxxx, platform-text-dev@xxxxxxxxxxx
        cc: 
        Subject:        [platform-text-dev] RCP proposal - extension point 
changes



The paper proposes to replace the org.eclipse.ui.markerUpdater extension 
point with org.eclipse.ui.resources.markerUpdaters. This extension point 
is used by the org.eclipse.ui.workbench.texteditor plug-in but is not 
owned by it for compatibility reasons. As establishing the RCP will imply 
API breaking changes anyway, the text plug-ins that are under the roof of 
org.eclipse.ui should assume ownership for that portions of the 
org.eclipse.ui plugin.xml file they use or conceptually own. For the other 
plug-ins that probably makes sense as well. Could you please notify when 
you start changing the extension point definitions, so that changes can be 
done at the same time. 

Kai