[Qt-creator] Kit and device concept in QtCreator

[David Kaspar]

Hi Tobias,

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)

If any plugin answers the canProvideDeviceListFor() then there might be 
a new 'Devices' column added to the device-selector popupated via 
getDeviceList(). If not, then no 'Devices' is shown. This will be 
backward compatible change and possible enough flexible for other plugin 
to reuse this functionality.

We would not mind to implement this feature if it would be accepted from 
architecture point of view.

The second question is whether we should still have the 
'device-switching in run-configuration' if it would be available even in 
Mini Target Selector'. I think that it might be good to have it - just 
to make this switching more accessible - anyway this is specific to each 
plugin anyway...

See you,
   David


On 05/09/13 15:32, Tobias Hunger wrote:
> Hey Mehdi, Hallo Christian,
>
> feedback we had when we were still with Nokia was that the kits
> concept worked well for device development. The icon changing in the
> Mini Target Selector to reflect the actual device targeted was the one
> big thing there. That will go away with your device-switching
> approach: You will have to check the actual popup for the device used
> to see where your code will be run then.
>
> 2013/9/5 Christian Kandeler <christian.kandeler at digia.com>:
>> This would also help in making more visible which device we actually use
>> when deploying/running, at the place in the GUI where it matters most. I
>> actually planned to put a label there, but of course a combo box would
>> work as well,
> How is this setting any different from e.g. the compiler used to build
> the code or the Qt version used? Should those get labels in the
> buildconfiguration as well? Should we make those editable in the build
> configuration as well? UI-wise we would then be back at the targets,
> but with the disadvantage that projects will change settings for other
> projects. That may or may not break their configurations.
>
> My understanding was that we all agreed to go for having certain
> entries of the kits configurable in the mini target selector (that
> thing with the kit icon above the run/debug/build butttons). Which
> settings to have configurable there was supposed to be defined by the
> kits themselves, so that e.g. your blackberry plugin can put the
> device selector there while the desktop kit (there is always exactly
> one desktop device) will most likely not want to display that UI. That
> is a compromise everybody should be able to live with and it actually
> increases flexibility... which hardcoding "this platform can change
> this setting" does not.
>
> Did something pop up that changed that?
>
> Best Regards,
> Tobias
> _______________________________________________
> Qt-creator mailing list
> Qt-creator at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.