Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [dsdp-tm-dev] Status of core/ui separation?

Hi Greg,

Most preparations are done for UI/Core splitting, i.e.
all important interfaces are in Core but implementations
have not all moved yet.

We came across a roadblock in the SubSystem abstract
base class, which should be core but is still UI.

Long story short: We have prepared the interfaces, such
that when we're moving to TM 3.0 we can complete the
splitting mostly without breaking API. But we ran out
of time cmpleting it for 2.0. The SystemRegistry impl,
for instance, has been prepared and should be ready for 
moving to Core, but it has not been done yet.

Do you have a concrete use case why you'd like using
a SystemRegistry in Core only?

Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member 

> -----Original Message-----
> From: dsdp-tm-dev-bounces@xxxxxxxxxxx 
> [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx] On Behalf Of Greg Watson
> Sent: Wednesday, June 06, 2007 1:21 AM
> To: Target Management developer discussions
> Subject: [dsdp-tm-dev] Status of core/ui separation?
> Hi,
> What is the status of the separation of RSE core from the UI? 
> Are you  
> still planning to do this? I notice that the SystemRegistry is still  
> in org.eclipse.rse.ui, and when I try to load just  
> org.eclipse.rse.core, RSECorePlugin.getSystemRegistry() returns null.
> Thanks,
> Greg
> _______________________________________________
> dsdp-tm-dev mailing list
> dsdp-tm-dev@xxxxxxxxxxx

Back to the top