Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Heads up - considering o.e.remote for LaunchBar Targets

Actually, the only thing needed by the LaunchBar is the target id and target type/id and the concept of having an active target. All the build and launching is handled by the launch delegates.

One thing that o.e.remote gives us is the ability to get the os and arch from the connection. My plan is to use that to help select CDT build configs applicable for a given target and maybe even os specific launch configurations. But the end goal is to provide generic remote launching for CDT (and potentially JDT) over SSH using the o.e.remote.jsch extension.

Doug

From: Mikhail Khodjaiants <mikhailkhod@xxxxxxxxxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Friday, November 28, 2014 at 11:52 AM
To: "cdt-dev@xxxxxxxxxxx" <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Heads up - considering o.e.remote for LaunchBar Targets

Correct me if I am wrong but from the LaunchBar's UI point of view all information required from the target is the following:
    - unique id
    - target type id
    - user friendly name
    - support for "Build": canBuild() and build()
    - list of supported launch modes (Run, Debug, etc)
    - support for "Launch": canLaunch() and launch()
    - support for "Terminate"
Methods called on lightweight target objects will be delegated to the "real" target implementations.

I would even go further and replace build, launch and terminate related methods by services. What do you think?

On 28/11/2014 11:25 AM, Doug Schaefer wrote:
I struggled with that question, but in the end it came to what’s the difference between creating an implementation of ILaunchTarget versus IRemoteConnection?

The implementation for Arduino will tell me how much work is involved. Other than storing the serial port name, it should be a pretty minimal implementation for IRemoteConnection. So we’ll see.

The key is to start driving towards a single API for target management so all our tools can work together. Introducing yet another one is a maintenance nightmare and really unnecessary.

Doug.

From: Mikhail Khodjaiants <mikhailkhod@xxxxxxxxxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Friday, November 28, 2014 at 11:18 AM
To: "cdt-dev@xxxxxxxxxxx" <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Heads up - considering o.e.remote for LaunchBar Targets

On 28/11/2014 9:46 AM, Doug Schaefer wrote:
So, I’m currently prototyping replacing ILaunchTarget with IRemoteConnection. So far, I’m getting excited about the direction. Everything I wanted is already in the Remote plug-ins. And it looks easy to extend to add new connection types. The big test will be getting the Arduino serial connection implemented with this. I’ll also be adding a re-usable file system browser that’ll use the file APIs. The big benefit will be to get SSH remote target support with minimal effort.

Doug,

I may be wrong but wouldn't it be better to keep ILaunchTarget very simple and provide an implementation based on IRemoteConnection. This with a proper registration mechanism would allow other implementations of ILaunchTarget that are not based on o.e.remote.

Mikhail


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top