We have moved to a new Sailfish OS Forum. Please start new discussions there.

Editing QML files during development

asked 2014-12-19 14:27:12 +0300

smoku gravatar image

updated 2014-12-19 14:35:55 +0300

eric gravatar image

Does anyone have a better workflow for creating QML files for SailfishOS application than the current edit-build-deploy-restart-test-edit-build-deploy-... cycle?

It feels like taking ages to have to do full build&deploy cycle after changing one line in QML file. I really miss the ability to run the same files I open in the editor and just doing "refresh" of QML files in my app (instead of copying them to VM or device).

edit retag flag offensive close delete

2 Answers

Sort by » oldest newest most voted

answered 2014-12-19 14:30:11 +0300

updated 2014-12-19 15:40:34 +0300

Qt Creator offers some options to make the deployment process a bit faster:

  1. Use "Deploy By Copying Binaries" instead of "Deploy As RPM Package"
  2. Configure Qt Creator to NOT build your app before deployment. You then have to build it manually if you change your C++ code before deployment but it is much faster when you just want deploy QML changes. See here for more information.

Original post:

In Qt Creator, you can deploy your app by choosing "Deploy By Copying Binaries" instead of "Deploy As RPM Package". This is much faster while developing your app :)

edit flag offensive delete publish link more


Not that much faster... I have a pretty big C++ part that is being scanned whether anything changed and needs rebuilding. RPM packaging is quick in comparison. Also, it copies files to different place than RPM packaging.

smoku ( 2014-12-19 14:42:29 +0300 )edit

I turned the "build every time before deployment" option off in Qt Creator, so I build it whenever I want with Ctrl+B. Otherwise I just run the app by hitting Ctrl+R.

ejjoman ( 2014-12-19 14:45:29 +0300 )edit

Oh. I wasn't aware of the option. I will check it out. Should help. :)

smoku ( 2014-12-19 14:47:28 +0300 )edit

The option can be found in Tools > Options > Build & Run. See http://doc.qt.io/qtcreator/creator-build-process-customizing.html for more information :)

ejjoman ( 2014-12-19 14:50:56 +0300 )edit

Updated my answer accordingly :)

ejjoman ( 2014-12-19 15:47:22 +0300 )edit

answered 2014-12-19 22:18:14 +0300

MartinK gravatar image

Check my answer to the How to deploy Qt/QML application without SDK? question. :) Even if you are not using Python, you can still rsync just the QML files.

edit flag offensive delete publish link more


How exactrly do you rsync? I'm thinking about a custom build step, but I need device address and credentials.

smoku ( 2014-12-20 22:12:07 +0300 )edit

I'm kinda doing it the other way around (I ssh to the device and rsync stuff to the device from my PC). But for your case, this should work:

  • configure SSH password in Settings -> Developer Tools (or how it is called in English)
  • make sure you can you can now SSH to your Jolla
  • optionally setup public key authentication so you don't have to type the SSH password every time
  • next try to rsync something from your PC to the Jolla over SSH
  • and finally setup the rsync with correct paths as a step in QtCreator
MartinK ( 2014-12-20 23:38:54 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2014-12-19 14:27:12 +0300

Seen: 513 times

Last updated: Dec 19 '14