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

[Martin Kolman]

Fri, 23 Oct 2015 15:21:47 +0200 Te:
> Thanks for the input, Almicar and Hassan,
>
> I successfully tried sailfish-reload on (Arch) Linux and will 
> definitely use it in the future as it *really* speeds up development.
>
> Hassan's tips seem to resemble the sailfish-reload internals in a 
> manual way (which is also nice to know, especially as an emacs power 
> user --> I tried to get rid off QtCreator long time ago).
>
> Anyhow, I'm still interested in co-developing for different targets, 
> as I have a laptop with deactivated virtualization (password protected 
> BIOS). Accidently, I stumbled upon QQmlFileSelector / QFileSelector 
> which sound promising. Maybe it is possible to have a common base of 
> C++ and js files and the respective QML component files are switched 
> depending on some characteristic selector.
I'm using Universal Components[0] for the modRana[1] UI - they make it 
possible to have just a single set of QML files for both Desktop/Android 
(using the Controls UC backend) or Sailfish OS (using the Silica UC 
backend). :)
So I can just run the app natively on my Linux (Fedora 22) desktop 
during development, which makes the code/run/debug cycles lightning fast. :)

BTW, as for what editor/IDE I'm using - Pycharm & vim; I don't actually 
even have the SDK installed and I'm using the Mer OBS[2] for package 
building. :)

Martin

[0] https://github.com/M4rtinK/universal-components
[1] https://github.com/M4rtinK/modrana
[2] https://build.merproject.org/

> Has anyone used QQmlFileSelector for Sailfish development?
>
> Cheers,
> Thomas
>
>
> On 22.10.2015 18:25, Mohammed Hassan wrote:
>> On Thu, 22 Oct 2015 15:43:46 +0200
>> TE <yurumi at gmx.de> wrote:
>>
>>> 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!
>> There are multiple tips if you are using Linux AND you don't care
>> about QtCreator:
>> - I use a multi-tabbed terminal. The first tab has emacs (console not
>>    X11) editing code. Once I am done with the code, I switch to the 2nd
>>    tab.
>>    The 2nd tab is a tab dedicated for typing 1 command: sb2 make && scp
>>    <whatever> phone:~/app_test_dir/
>>    The 3rd tab is a phone ssh session where I just ^c and rerun the app
>>    to check it.
>>
>> - Sometimes I edit QML code on the phone and restart the app to check
>>    but you have to be capable of tolerating vi (The editor on the 
>> phone).
>>
>> - C++ engine is easily testable on the desktop. Not a big issue IMHO.
>>
>> - You can try installing Silica on the desktop especially that there
>>    are now x86 binaries. This can speed up your development. I have not
>>    done that so I unfortunately cannot help here but it should be 
>> doable.
>>
>> HTH
>>
>> Cheers,
>
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to 
> devel-unsubscribe at lists.sailfishos.org