Skip to main content



      Home
Home » Archived » DSDP - Tools for Mobile Linux (TML) » Why have two extension-points to define services
Why have two extension-points to define services [message #561809] Wed, 23 July 2008 15:05 Go to next message
Eclipse UserFriend
Hello everyone,

I am not sure I got the idea of having the two different extension-points
to define services (org.eclipse.tml.framework.device and
org.eclipse.tml.serviceDefinition)

My understanding is that the goal of having two extension points is
basically defining basic service information through
"org.eclipse.tml.framework.device" and allowing them to be customized by
the "org.eclipse.tml.serviceDefinition" (which also defines handlers for
the state transitions).
This way one plug-in can define the services available and other plug-ins
could provide the different "implementation" for that same service.

Did I get the idea?

If my understanding is correct I would like to suggest merging these two
extension points in one (in order to avoid confusion) and add the
capability of defining services as abstract and allowing services to
extend parent services (something similar to what CDT does with elements
of the org.eclipse.cdt.managedbuilder.core.buildDefinitions)

Thanks,

Daniel
Re: Why have two extension-points to define services [message #1069266 is a reply to message #561809] Mon, 15 July 2013 10:59 Go to previous message
Eclipse UserFriend
It is actually a good idea to merge the two extension points. Makes the job easier.

_____________
agile development methodology
Previous Topic:invitation to next open meeting
Next Topic:developers mailing list
Goto Forum:
  


Current Time: Mon Mar 17 11:52:40 EDT 2025

Powered by FUDForum. Page generated in 0.02904 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top