Bug 186773 - [api] Split ISystemRegistryUI from ISystemRegistry
Summary: [api] Split ISystemRegistryUI from ISystemRegistry
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P2 enhancement (vote)
Target Milestone: 2.0   Edit
Assignee: Martin Oberhuber CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks: 170923 175680
  Show dependency tree
 
Reported: 2007-05-14 08:30 EDT by Martin Oberhuber CLA
Modified: 2008-08-13 13:18 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-05-14 08:30:20 EDT 
ISystemRegistryUI should be an interface on its own right, rather than extend ISystemRegistry. 

Only like that, it will be possible to move SystemRegistry implementation into non-UI in the future.

Clients which need an ISystemRegistry should always do
   RSECorePlugin.getTheSystemRegistry() 
in order to get the ISystemRegistyr. Clients which need the UI services, should
   RSEUIPlugin.getTheSystemRegistryUI()
Comment 1 Martin Oberhuber CLA 2007-05-14 09:04:48 EDT 
Work complete, checkin comment:
[186773][api] split ISystemRegistryUI from ISystemRegistry

Migration Docs:
---------------
Client code that wants to use the ISystemRegistry, MUST now call
   RSECorePlugin.getTheSystemRegistry()
Client code that needs UI facilities such as postEvent() and the clipboard,
MUST now call
   RSEUIPlugin.getTheSystemRegistryUI()
Comment 2 Martin Oberhuber CLA 2008-08-13 13:18:29 EDT 
[target cleanup] 2.0 M7 was the original target milestone for this bug