[SailfishDevel] Lipstick and xdg-open

Hi Developers, How does Lipstick handle xdg-open in cases when the app is already running? When the app isn't running, I can currently open a file through xdg-open, which opens the app and passes in the file url as a command line parameter. I expected that upon subsequent xdg-open calls, it

Re: [SailfishDevel] Lipstick and xdg-open

lipstick itself doesnt handle xdg, because it's a different things. to make it works like clicking in application grid you should use libcontentaction instead. -- Исходное сообщение -- От: "r0kk3rz" Кому: "Sailfish OS Developers"

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

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

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

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 /

Re: [SailfishDevel] Lipstick and xdg-open

It depends if your app is configured (via .desktop file) to be running as single instance or not; and that is related to the launcher (which is enforced on SFOS btw); see "How can I disable single-instance launching?" under https://harbour.jolla.com/faq). If

Re: [SailfishDevel] SDK version 1510 (1.1.9) is released

Hello Thomas, > Somehow the "unfoldability" of the Silica reference has gone AWOL in the > process. Thanks for reporting this - fixed, to be released soon. BR, Martin ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to

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

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