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 (whic
Hi Thomas,
It is definitely possible to have common C++ base. Also, if your JS
files don't depend on platform-specific API, they can be shared across
platforms. That's what I do in TAO Translator[1]. However, instead of
using QFileSelector (as it's not available on Qt 4), I'm using #ifdef's
t
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
On Thu, 22 Oct 2015 15:43:46 +0200
TE 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 Sili
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 Direc
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 /
tes
