[Qt-creator] Kit and device concept in QtCreator

[Christian Kandeler]

On 09/05/2013 05:39 PM, David Kaspar wrote:
> Then as you suggest, we might have another interface to represent the
> 'context' instead of RunConfiguration.

Thinking about this some more, it seems to me that we already have that 
context -- it's the Target object, isn't it?


Christian

> Theoretically we might use such
> Context even for the Device i.e.:
>
> bool canHandle(Context)
> Context getActive(Context)
> QList<Context> getChildren(Context)
> void setActive(Context, Context)
>
> This would be enough extensible to allow any number of columns if
> necessary. The current behavior of the columns might be handled by a
> fallback implementation (aka Project/Target/Build/Deploy/Run columns)
> which would be always searching for extension interface to allow plugin
> into any column.
>
> Thanks,
>     David
>
>
> On 05/09/13 17:23, Christian Kandeler wrote:
>> On 09/05/2013 05:15 PM, David Kaspar wrote:
>>> We wanted this 'device-switching in Mini Target Selector' feature
>>> implemented right after the 'device-switching in run-configuration' - at
>>> least for Qnx plugin. This would significantly improve the usability. I
>>> think that this feature would be very useful even for other devices.
>>>
>>>     From API point of view, this feature can be implemented by providing a
>>> new extension interface with the following methods:
>>>
>>> bool canProvideDeviceListFor(RunConfiguration)
>>> Core::Id getActiveDevice(RunConfiguration)
>>> QList<Core::Id> getDeviceList(RunConfiguration)
>>> void setActiveDevice(RunConfiguration, Core::Id)
>> Please keep in mind that there might not be a run configuration, but a
>> deploy configuration could still be present (or, less likely, vice
>> versa). And if both are present, they would typically share the device
>> setting. So you'd need a new abstraction for that.
>>
>>
>> Christian