[SailfishDevel] Workflow for co-development for desktop / sailfish silica

[Amilcar Santos]

My workflow to speedup development on Windows (when compiling the
binary is not necessary / QML changes only):
  - Start QtCreator + emulators
  - Open a project
  - Deploy once (copy binaries)
  - start WinSCP (winscp.net) and login in emulator
    - Select in WinSCP > Commands > Keep Remote Directory up to Date..
   -  'Local directory': my project qml folder
   -  'Remote directory': /opt/sdk/<project>/usr/share/../qml
   -  Mark checkboxes: "Update subdirectories" + "Synch on start"
    -  Press "Start" -> now WinSCP will keep updating all qml files
that are saved
 - From QtCreator: I can stop and (re)start from Application console
toolbar (don't forget to save first)

Also found this project (didn't tested):
 https://www.npmjs.com/package/sailfish-reload


2015-10-22 14:43 GMT+01:00 TE <yurumi at gmx.de>:
> Hi all,
>
> until now, my development workflow consists of coding and subsequently
> testing on the device or emulator respectively. Every cycle takes quite some
> time. Is there a neat way / architecture for co-developing for the desktop
> and Silica UI. The aim would be to do most of the coding / testing with the
> desktop target and switch to the emulator / device for the Silica UI.
>
> I would be grateful if anybody could share his/her experiences or workflow!
>
> Cheers,
> Thomas
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscribe at lists.sailfishos.org



-- 
Amilcar
(djditz in the mix... ;)