2016-02-08 23:45:57 +01:00
|
|
|
.. _doc_one-click_deploy:
|
2016-02-08 22:07:55 +01:00
|
|
|
|
2016-02-06 01:54:33 +01:00
|
|
|
One-click deploy
|
|
|
|
|
================
|
|
|
|
|
|
2016-02-19 22:00:07 +01:00
|
|
|
Sounds good, what is it?
|
2016-02-06 01:54:33 +01:00
|
|
|
------------------------
|
|
|
|
|
|
|
|
|
|
This feature will pop up automatically once a platform is properly
|
|
|
|
|
configured and a supported device is connected to the computer. Since
|
|
|
|
|
things can go wrong at many levels (platform may not be configured
|
2017-11-01 09:45:33 +01:00
|
|
|
correctly, SDK may be incorrectly installed, device may be improperly
|
2016-02-06 01:54:33 +01:00
|
|
|
configured, kitty ate the USB cable, etc.), it's good to let the user
|
|
|
|
|
know that it exists.
|
|
|
|
|
|
|
|
|
|
Some platforms (at the time of this writing, only Android and Blackberry
|
|
|
|
|
10) can detect when a USB device is connected to the computer, and offer
|
|
|
|
|
the user to automatically export, install and run the project (in debug
|
|
|
|
|
mode) on the device. This feature is called, in industry buzz-words,
|
|
|
|
|
"One Click Deploy" (though, it's technically two clicks...).
|
|
|
|
|
|
2016-02-19 22:00:07 +01:00
|
|
|
Steps for one-click deploy
|
2016-02-06 01:54:33 +01:00
|
|
|
--------------------------
|
|
|
|
|
|
|
|
|
|
#. Configure target platform.
|
|
|
|
|
#. Configure device (make sure it's in developer mode, likes the
|
2016-05-23 21:15:26 +02:00
|
|
|
computer, usb is recognized, usb cable is plugged, etc.).
|
2016-02-06 01:54:33 +01:00
|
|
|
#. Connect the device..
|
2016-02-19 22:00:07 +01:00
|
|
|
#. And voila!
|
2016-02-06 01:54:33 +01:00
|
|
|
|
2017-10-14 14:19:23 +02:00
|
|
|
.. image:: img/oneclick.png
|
2016-02-06 01:54:33 +01:00
|
|
|
|
|
|
|
|
Click once.. and deploy!
|
