[Qt-creator] Tab UI in Projects mode to TreeView

[Ariel Molina]

> Why don't you use a single build directory for all the kits?
1. Because I the workflow almost never uses parallel deployment, it's
single device, but all along the day i need to re-deploy to some random
devices.
2. It has to run on local Linux without any modifications.

I also do this for Android from time to time. What i've found is the
Android-style deployment is very powerful, I can build and the Android
device is selected on launch. If there would be a possibility to have a Kit
with "Ask for Remote device" it will work very easily.

I was thinking about this, and, maybe Im getting off-topic, but this will
help a lot. It will appear only when not using local machines.
http://imgur.com/kMtEzJD

It will also help iOS deployments as they have the very same problem.

Ariel


On Tue, Aug 4, 2015 at 1:03 AM, Orgad Shaneh <orgads at gmail.com> wrote:

> בתאריך 4 באוג׳ 2015 1:13 לפנה״צ,‏ "Ariel Molina" <ariel at edis.mx> כתב:
> >
> > Hello,
> >
> > I would like to add an opinion, I am one person who has several kits on
> his setup, look at: http://imgur.com/mwlqEWY
> >
> > But I find the reason for it to be a suboptimal Kit Definition mechanism
> in QtC. For example, I need to develop on several Raspberry Pi for testing,
> and some of them are DHCP clients, I need to create new kits for all of
> them, following the Wizard or cloning. Then I need to deploy to several
> targets, it is a pain to wait for recompilation based on a fact that only
> the IP address was changed. Please see: http://imgur.com/mwlqEWY
> >
> > Ariel
>
> Reminds me of this thread
> <http://lists.qt-project.org/pipermail/qt-creator/2012-November/001536.html>
> ...
>
> Why don't you use a single build directory for all the kits?
>
> - Orgad
>



-- 
Ariel Molina R.

Oficina: +52 (222) 3723196
Movil: +521 2226 758874
http://edis.mx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20150804/a01fae60/attachment.html>