Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[dsdp-tm-dev] RE: Advanced Remote Launching (was: Is TM/RSE right for us?) 
Hi Robert,

it's great to discuss this with you.

I understand your concerns about nested XML, and 
I also see your point with the prefixes. Still I
believe that ILaunchActions should be able to live
without the ILaunchConfiguration (perhaps there 
could be an implementation of ILaunchActionContext
that uses ILaunchConfiguration to retrieve some data).

Regarding serialization / deserialization, what do you
think about this:

* ILaunchAction specifies a set of properties that it
  needs to be configured. This could be the same types
  being used in plugin.xml (String, Integer, Boolean)
  plus the same meta information (worspace path, icon,
  class etc). For example, the PropertySetSpecification
  of an ILaunchAction for upload could be:
  {
    { "localPath", "String", "localPath" },
    { "remotePath", "String", "remotePath" },
    { "syncOnly", "Boolean", "" },
    { "ok", "Boolean", "result" }
  }
  where column 1 is the name of the property,
  column 2 is the plain type,
  and column 3 is the meta-info where "result"
  specifies an output parameter etc.

* With this set of meta-information about the properties,
  it is easy to write generic forms for data entry (e.g.
  using FieldEditors or forms), but also several different
  generic mechanisms for serialization/deserialization, e.g.
  xml, plain Java Properties or "script-like":
     upload -localPath "c:/x" -remotePath "/tmp", -syncOnly true -ok
$status

--> There can be several different serialization providers as needed
--> Effort fro writing a new ILaunchAction is minimal because
    just the property set meta-info needs to be specified
--> Minimal duplication of code
--> Generic UI
--> If an ILaunchAction wants an advanced UI it could contribute
    one, or just live with the generic one
--> Users can have multiple editors for editing the Launch Script:
    GUI based, XML, script-like, Graphical flowchart etc...
    imagine any type of editors, they are just new "views"
    on the generic "model" of the ILaunchAction

As for the names of the properties, an advanced version could
hold both a "native" property name which is stored internally
and a "localized" one or "description" or helpcontext etc.

What do you think?

Cheers,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm

Back to the top