Re: [SailfishDevel] App splashscreens on Sailfish

[Martin Windolph]

Hi,

I don't know if there's something official by Silica, but I got a harbour 
rejection for long loading times a while ago.
I did the following:
On
 my "initialPage", I just show some splash image (anchors.fill: parent) 
and I include a "Loader" item that overlaps that (also anchors.fill: 
parent). The Loaders asynchronous property is set to true.
The item, 
the Loader loads, does the rest of the apps initialization, so you get a
 state change when it's done Loading. Then it's done, I make "the Loader
 visible" (and the splash screen invisible). That reduced my initial 
loading times a lot.
example: https://github.com/yoktobit/morzyn/blob/master/qml/MorzynPage.qml

bg
Martin

> Date: Wed, 22 Jan 2014 08:22:41 +0100
> From: christopher.l...@thurweb.ch
> To: devel@lists.sailfishos.org
> Subject: [SailfishDevel] App splashscreens on Sailfish
> 
> Hi all
> 
> Does sailfish support application splash screens? Is so how?
> 
> This indicates https://github.com/nemomobile/mapplauncherd that  
> Sailfish does not - at least when starting with mapplauncherd.
> 
> My semi-ported app is taking a little too long to start, and while I  
> have a clear medium term goal to find out what is taking time and  
> optimise / eliminate that, at the moment I am focussed on getting  
> things working on Sailfish, and therefore a splash screen would be  
> handy. Once everything is working, I can then turn to get it working  
> ever more slickly!
> 
> Chrsi
> 
> 
> ___
> SailfishOS.org Devel mailing list
  ___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

[Joona Hoikkala]

On 21 Jan 2014, at 21:39, Mohammed Hassan  
wrote:

> Each store has an audience. Harbour has its own audience as well as openrepos.

This is exactly what I'm thinking, Openrepos is very appealing to me for 
example, 
but wouldn't I recommend it for my mother who doesn't have the required 
skill / intrest checking backgrounds of all the shiny looking things. She needs
her device to work on daily basis and rm -rf / would be a disaster.

No QA can be foolproof, but at least as Harbour packages come, there is at 
least SOME control.

And I refuse to think Jolla phone as a hacker niche device in the long run.


--
Joona
___
SailfishOS.org Devel mailing list

[SailfishDevel] App splashscreens on Sailfish

[christopher . lamb]

Hi all

Does sailfish support application splash screens? Is so how?

This indicates https://github.com/nemomobile/mapplauncherd that  
Sailfish does not - at least when starting with mapplauncherd.


My semi-ported app is taking a little too long to start, and while I  
have a clear medium term goal to find out what is taking time and  
optimise / eliminate that, at the moment I am focussed on getting  
things working on Sailfish, and therefore a splash screen would be  
handy. Once everything is working, I can then turn to get it working  
ever more slickly!


Chrsi


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

[Ruediger Gad]

Please note: I actually didn't follow this discussion very closely but I
think I can add at least one small comment.

On 01/21/2014 10:03 PM, Martin Kolman wrote:
> 21.1.2014 21:34, Martin Grimme:
>> ...
> Just a slight correction. As far as I know, you can only upload source code
> to Extras-Devel which is built by the Maemo Autobuilder and the
> resulting binary package
> published. I'm quite sure you can't upload binary packages at all, at
> least I have not seen
> any in all those years in Extras-Devel.

"Binary packages" can be uploaded. See, e.g.:
http://maemo.org/downloads/product/Maemo5/icedtea6/

Essentially, you can upload a tarball as "source" that contains a
pre-compiled binary and then in the packaging simply extract that binary
and skip the according build, strip, etc. steps by adjusting the
build/packaging files.



hth,

Ruediger




> 
> On the other hand both OpenRepos and Harbour currently only accept
> binary packages,
> at least until the OpenRepos <-> OBS bridge is online.
> 
> So when we are doing comparisons, I would say Harbour is closer to the
> Ovi store, as available on Fremantle and Harmattan:
> * binary only upload
> * cross package dependencies not supported (bundle-all approach)
> * IIRC, there were no limits on packaging scripts
> * centralized mandatory QA with a multi-day QA period
> (at least the Harbour QA seems to repply in a more comprehensible
> manner, unlike the sometimes very confusing responses of the late Ovi
> store QA drones)
> * rules where the apps should store its file (data goes to /opt,
> deploying binaries to path not allowed, ...)
> * mandatory major.minor.build numbering
> * as Profilematic is in Ovi store, it looks like it was possible to
> install daemons and bind to events
> * location was supported over QtMobility
> * some semi-sane requirements for apps not to stop working due to upgrades
> * also only one-way user->store feedback and comments
> * unlike current Harbour, Ovi had a Web interface
> * no Android apps, but flooded by automatically made RSS-reader apps :)
> ___
> SailfishOS.org Devel mailing list


-- 
http://ruedigergad.com
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

[Martin Kolman]

21.1.2014 21:34, Martin Grimme:



You can compare
those in their function to Maemo Extras and Maemo Extras Devel in the old N900
days.
Everybody could upload to Extras Devel, but to get stuff into Extras, it had
to pass a quarantine and a (IMHO slow and frustrating) QA phase.
Only Extras was pre-enabled on sales devices, and even for this, Nokia
had to be
convinced first, that apps reaching Extras are ready for regular users.

Just a slight correction. As far as I know, you can only upload source code
to Extras-Devel which is built by the Maemo Autobuilder and the 
resulting binary package
published. I'm quite sure you can't upload binary packages at all, at 
least I have not seen

any in all those years in Extras-Devel.

On the other hand both OpenRepos and Harbour currently only accept 
binary packages,

at least until the OpenRepos <-> OBS bridge is online.

So when we are doing comparisons, I would say Harbour is closer to the 
Ovi store, as available on Fremantle and Harmattan:

* binary only upload
* cross package dependencies not supported (bundle-all approach)
* IIRC, there were no limits on packaging scripts
* centralized mandatory QA with a multi-day QA period
(at least the Harbour QA seems to repply in a more comprehensible 
manner, unlike the sometimes very confusing responses of the late Ovi 
store QA drones)
* rules where the apps should store its file (data goes to /opt, 
deploying binaries to path not allowed, ...)

* mandatory major.minor.build numbering
* as Profilematic is in Ovi store, it looks like it was possible to 
install daemons and bind to events

* location was supported over QtMobility
* some semi-sane requirements for apps not to stop working due to upgrades
* also only one-way user->store feedback and comments
* unlike current Harbour, Ovi had a Web interface
* no Android apps, but flooded by automatically made RSS-reader apps :)
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

[Martin Grimme]

Hi

2014/1/21, kaa :
> [...] Crap [...] Bla, bla , bla .. FUD .. bla bla bla [...] LOL [...] 
> bullshit [...] Howgh [...]

Thank you for valuable feedback. :)

IMHO, it makes sense to have both, Harbour and OpenRepos. You can compare
those in their function to Maemo Extras and Maemo Extras Devel in the old N900
days.
Everybody could upload to Extras Devel, but to get stuff into Extras, it had
to pass a quarantine and a (IMHO slow and frustrating) QA phase.
Only Extras was pre-enabled on sales devices, and even for this, Nokia
had to be
convinced first, that apps reaching Extras are ready for regular users.

Harbour has rules (sane rules IMHO) and QA (much less frustrating and
a lot faster than
the community-volunteer-driven Maemo Extras QA) to attempt to make
sure that apps

 - will install smoothly
 - will be compatible with future versions of the OS, where possible
 - will not break OS updates
 - don't compromise the system (well, it failed there, take the rpm installer
   in the Store, for instance)

I didn't include security in this enumeration, because we all know
that you cannot be
100% safe from malware, and OpenRepos may actually be safer in this
regard, if the
source is open.

The Flashlight app that phoned home with usage statistics still was legally
fine, though, even though phoning home is generally not well received.
It stole no
data, at least.

OpenRepos OTOH imposes no rules and no QA on the apps. Therefore, users should
be aware that apps

 - may not be installable or need more dependencies
 - may stop working with future OS updates
 - may even break OS updates (what happens in case of package conflicts?)
 - may compromise the system, as there are no limits

Basically, the users are free to do what they want with their devices. But for
legal reasons, the users must be informed about the consequences and accept
that if they break something, they get to keep the pieces.
The "Developer Mode" switch is this barrier.

It is a barrier that regular users (who may not even tell what a package is and
think of Linux as a laundry detergent) should not pass.
OpenRepos clearly lies beyond this barrier. That's why Harbour and the Jolla
Store are needed.

If you want to ignore Harbour, then that's your choice, and maybe it's fine as
your apps may be too advanced for the Average Joe, anyway.
But if you want to target the Average Joe, too, then you won't get around to
play by the rules of Harbour. It depends on who you want to reach.
Fortunately, Harbour rules are not set in stone and you can help shape them
for a better developer experience.


Just my 2 cents,
Martin
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

[Mohammed Hassan]

On Tue, Jan 21, 2014 at 02:15:14PM +0200, Joona Hoikkala wrote:
> Openrepos doesn't have any QA process, and you can publish your own closed 
> source blobs through it. 
> Meaning that someone could potentially push an application that steals or 
> destroys users data.

Maybe openrepos does not have the QA harbour has but I still have a few reasons 
to use openrepos:
1) I trust developers like coderus for example among others.
   I know they will not upload malware and I happily install
   their apps. Most apps are open so the code is there if
   I want to check.
2) Plenty of apps are available. Not all of them are mature
   but the FOSS sperit is to contribute (Or live with them).
3) OpenRepos is about native apps which is what I personally prefer.
   I am not a fan of Android apps at all.
4) I can browse openrepos using my browser and find the goodies I need.
5) I am sure I have missed some more reasons.

Each store has an audience. Harbour has its own audience as well as openrepos.

As for QA, No QA will prevent malware completely and it's a lie if it claims so.

Just my 0.02.

Cheers,
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Harbour compliant way to read contacts

[Bernd Wachter]

Harald Schmitt  writes:

Hi,

> I tried to use QContactManager, QContact and so on for an app I'd like
> to publish on harbour, but the line in my .pro file
> PKGCONFIG += Qt5Contacts
> is rejected by the new validation tool.
> How can I access contacts in a harbour app? Is there an example?

Short answer: Right now it's not allowed for legal reasons: We are not
allowed to pass contacts synced to the device from some third party
services through to other applications. 

Longer answer: There are two contacts databases on the device, one used
by Jolla applications, one for use by third party applications. The one
used by third party applications is currently empty, and won't be taken
into account by Jolla applications -> right now it does not make sense
to allow access to contacts, as you'd just live in your own small
world. We're working on making it possible for third party apps to
access 'local' contacts (i.e., contacts not tied to some service
agreement). The Android contacts access was easier to implement, as we
don't allow applications there to modify contacts, and we can filter to
pass through only local contacts.

Bernd

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] [Sailfish IDE] Can't run app in Debug mode anymore

[Sylvain B .]

Ok thanks Benoît, my last attempt was indeed certainly with the previous SDK.I 
just found out that it is referenced in the known issues: 
https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues#EmulatorIf I have time I 
will have a look at how to use GDB in command line. I just need to use the rpm 
containing the debug symbols I guess?
Thanks!-- Sylvain.

> Date: Tue, 21 Jan 2014 16:18:59 +0100
> From: kher...@khertan.net
> To: devel@lists.sailfishos.org
> Subject: Re: [SailfishDevel] [Sailfish IDE] Can't run app in Debug mode 
> anymore
> 
> It was working in Alpha2 SDK, and is broken in Alpha3 SDK ... :)
> 
> ---
> Benoît HERVIER - http://khertan.net/
> 
> Le 2014-01-21 16:14, winfried.do...@xmsnet.nl a écrit :
> > Are you sure it worked some weeks ago? Because as far as I know, 
> > debugging
> > has so far never worked, not on the emulator nor on the target.
> > 
> > I recently encountered the same issue and on IRC some sailors replied 
> > that
> > it's currently a known issue that will be fixed in a future SDK update.
> > 
> > regards,
> > 
> > Winfried
> > 
> > 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> Hello,
> >> This week-end, I wanted to investigate some segfault (easily 
> >> reproducible,
> >> see here:
> >> https://lists.sailfishos.org/pipermail/devel/2013-December/001707.html 
> >> )
> >> And for some reason, I found out that I am not able to run an app in 
> >> Debug
> >> anymore :/
> >> Few weeks ago it worked, but now, the Run Debug command just get stuck
> >> forever at the "Lauching" stage (after deployment)You can find below 
> >> the
> >> last lines of the debug logs (I don't know why copy/past add a "d" at 
> >> the
> >> beginning of each line)As anybody encountered the same issue? Any idea 
> >> of
> >> what I can do?
> >> 
> >> ps: I tried to uninstall/reinstall the SDK and recreate an application
> >> from scratch, but it doesn't help.pps: If you want the very simple
> >> segfaulting application described in the link above, I've put it here:
> >> http://sthocs.free.fr/sailfish/Hello-0.1-1.armv7hl.rpm. Click on any 
> >> Item
> >> to go to the second page and pull back to the first page: segfault.
> >> 
> >> Thank you,Sylvain.
> >> 
> >> 
> >> dState changed from DebuggerNotReady(0) to EngineSetupRequested(1)
> >> dQUEUE: SETUP ENGINE
> >> dNOTE: REQUEST REMOTE SETUP
> >> dCALL: SETUP ENGINE
> >> dEXAMINING
> >> C:/Users/Sylvain/Sailfish/build-Hello-MerSDK_SailfishOS_i486_x86-Debug/Hello
> >> dELF SECTIONS:  .interp .note.ABI-tag .note.gnu.build-id .gnu.hash 
> >> .dynsym
> >> .dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text
> >> .fini .rodata .eh_frame_hdr .eh_frame .init_array .ctors .dtors .jcr
> >> .dynamic .got .got.plt .data .bss .comment .debug_aranges .debug_info
> >> .debug_abbrev .debug_line .debug_str .debug_ranges .debug_types 
> >> .gdb_index
> >> .shstrtab .symtab .strtab
> >> dNOTE: REQUEST REMOTE SETUP
> >> dCALL: SETUP ENGINE
> >> dEXAMINING
> >> C:/Users/Sylvain/Sailfish/build-Hello-MerSDK_SailfishOS_i486_x86-Debug/Hello
> >> dELF SECTIONS:  .interp .note.ABI-tag .note.gnu.build-id .gnu.hash 
> >> .dynsym
> >> .dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text
> >> .fini .rodata .eh_frame_hdr .eh_frame .init_array .ctors .dtors .jcr
> >> .dynamic .got .got.plt .data .bss .comment .debug_aranges .debug_info
> >> .debug_abbrev .debug_line .debug_str .debug_ranges .debug_types 
> >> .gdb_index
> >> .shstrtab .symtab .strtab
> >> dTRYING TO START ADAPTER
> >> dNOTE: REQUEST REMOTE SETUP
> >> 
> >> 
> >>  
> >> ___
> >> SailfishOS.org Devel mailing list
> > 
> > 
> > ___
> > SailfishOS.org Devel mailing list
> ___
> SailfishOS.org Devel mailing list
  ___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] [Sailfish IDE] Can't run app in Debug mode anymore

[Benoît HERVIER]

It was working in Alpha2 SDK, and is broken in Alpha3 SDK ... :)

---
Benoît HERVIER - http://khertan.net/

Le 2014-01-21 16:14, winfried.do...@xmsnet.nl a écrit :
Are you sure it worked some weeks ago? Because as far as I know, 
debugging

has so far never worked, not on the emulator nor on the target.

I recently encountered the same issue and on IRC some sailors replied 
that

it's currently a known issue that will be fixed in a future SDK update.

regards,

Winfried









Hello,
This week-end, I wanted to investigate some segfault (easily 
reproducible,

see here:
https://lists.sailfishos.org/pipermail/devel/2013-December/001707.html 
)
And for some reason, I found out that I am not able to run an app in 
Debug

anymore :/
Few weeks ago it worked, but now, the Run Debug command just get stuck
forever at the "Lauching" stage (after deployment)You can find below 
the
last lines of the debug logs (I don't know why copy/past add a "d" at 
the
beginning of each line)As anybody encountered the same issue? Any idea 
of

what I can do?

ps: I tried to uninstall/reinstall the SDK and recreate an application
from scratch, but it doesn't help.pps: If you want the very simple
segfaulting application described in the link above, I've put it here:
http://sthocs.free.fr/sailfish/Hello-0.1-1.armv7hl.rpm. Click on any 
Item

to go to the second page and pull back to the first page: segfault.

Thank you,Sylvain.


dState changed from DebuggerNotReady(0) to EngineSetupRequested(1)
dQUEUE: SETUP ENGINE
dNOTE: REQUEST REMOTE SETUP
dCALL: SETUP ENGINE
dEXAMINING
C:/Users/Sylvain/Sailfish/build-Hello-MerSDK_SailfishOS_i486_x86-Debug/Hello
dELF SECTIONS:  .interp .note.ABI-tag .note.gnu.build-id .gnu.hash 
.dynsym

.dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text
.fini .rodata .eh_frame_hdr .eh_frame .init_array .ctors .dtors .jcr
.dynamic .got .got.plt .data .bss .comment .debug_aranges .debug_info
.debug_abbrev .debug_line .debug_str .debug_ranges .debug_types 
.gdb_index

.shstrtab .symtab .strtab
dNOTE: REQUEST REMOTE SETUP
dCALL: SETUP ENGINE
dEXAMINING
C:/Users/Sylvain/Sailfish/build-Hello-MerSDK_SailfishOS_i486_x86-Debug/Hello
dELF SECTIONS:  .interp .note.ABI-tag .note.gnu.build-id .gnu.hash 
.dynsym

.dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text
.fini .rodata .eh_frame_hdr .eh_frame .init_array .ctors .dtors .jcr
.dynamic .got .got.plt .data .bss .comment .debug_aranges .debug_info
.debug_abbrev .debug_line .debug_str .debug_ranges .debug_types 
.gdb_index

.shstrtab .symtab .strtab
dTRYING TO START ADAPTER
dNOTE: REQUEST REMOTE SETUP


  
___
SailfishOS.org Devel mailing list



___
SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] [Sailfish IDE] Can't run app in Debug mode anymore

[winfried . dobbe]

Are you sure it worked some weeks ago? Because as far as I know, debugging
has so far never worked, not on the emulator nor on the target.

I recently encountered the same issue and on IRC some sailors replied that
it's currently a known issue that will be fixed in a future SDK update.

regards,

Winfried


>
>
>
>
>
>
> Hello,
> This week-end, I wanted to investigate some segfault (easily reproducible,
> see here:
> https://lists.sailfishos.org/pipermail/devel/2013-December/001707.html )
> And for some reason, I found out that I am not able to run an app in Debug
> anymore :/
> Few weeks ago it worked, but now, the Run Debug command just get stuck
> forever at the "Lauching" stage (after deployment)You can find below the
> last lines of the debug logs (I don't know why copy/past add a "d" at the
> beginning of each line)As anybody encountered the same issue? Any idea of
> what I can do?
>
> ps: I tried to uninstall/reinstall the SDK and recreate an application
> from scratch, but it doesn't help.pps: If you want the very simple
> segfaulting application described in the link above, I've put it here:
> http://sthocs.free.fr/sailfish/Hello-0.1-1.armv7hl.rpm. Click on any Item
> to go to the second page and pull back to the first page: segfault.
>
> Thank you,Sylvain.
>
>
> dState changed from DebuggerNotReady(0) to EngineSetupRequested(1)
> dQUEUE: SETUP ENGINE
> dNOTE: REQUEST REMOTE SETUP
> dCALL: SETUP ENGINE
> dEXAMINING
> C:/Users/Sylvain/Sailfish/build-Hello-MerSDK_SailfishOS_i486_x86-Debug/Hello
> dELF SECTIONS:  .interp .note.ABI-tag .note.gnu.build-id .gnu.hash .dynsym
> .dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text
> .fini .rodata .eh_frame_hdr .eh_frame .init_array .ctors .dtors .jcr
> .dynamic .got .got.plt .data .bss .comment .debug_aranges .debug_info
> .debug_abbrev .debug_line .debug_str .debug_ranges .debug_types .gdb_index
> .shstrtab .symtab .strtab
> dNOTE: REQUEST REMOTE SETUP
> dCALL: SETUP ENGINE
> dEXAMINING
> C:/Users/Sylvain/Sailfish/build-Hello-MerSDK_SailfishOS_i486_x86-Debug/Hello
> dELF SECTIONS:  .interp .note.ABI-tag .note.gnu.build-id .gnu.hash .dynsym
> .dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text
> .fini .rodata .eh_frame_hdr .eh_frame .init_array .ctors .dtors .jcr
> .dynamic .got .got.plt .data .bss .comment .debug_aranges .debug_info
> .debug_abbrev .debug_line .debug_str .debug_ranges .debug_types .gdb_index
> .shstrtab .symtab .strtab
> dTRYING TO START ADAPTER
> dNOTE: REQUEST REMOTE SETUP
>
>
> 
> ___
> SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Limitations for icons in the event screen?

[Boris Pohler]

Yepp, even after reboot the background is black.

Am Dienstag, den 21.01.2014, 14:37 +0100 schrieb Andrea Bernabei:
> hello Boris, 
> 
> 
> do they *always* show with black background? (msybe only after reboot,
> or maybe only when they appear, stuff like that)
> 
> I noticed that also happens with android apps notifications, but not
> always! so in that case it's probably a bug somewhere in the image
> handling
> 
> 
> 2014/1/21 Andrey Kozhevnikov 
> i had same question on 3rd Januarry. Still unanswered...
> https://lists.sailfishos.org/pipermail/devel/2014-January/002482.html
> 
> 
> On 21.01.2014 19:28, Boris Pohler wrote:
> Hi,
> are there any limitations/requirements for icons used
> by notifications
> on the event screen? I ask because I have a problem
> with transparent
> backgrounds of the icons, see screenshot in the link
> below:
> 
> https://dl.dropboxusercontent.com/u/107743837/20140121141345.jpg
> The icons (64x64px, size about 1kB) have transparent
> background and for
> the first few starts everything is fine, but then the
> transparent
> background turns to black.
> I looked at the icons used by jolla
> at /usr/share/themes/jolla-ambient/meegotouch/icons/
> but didn't found
> any difference.
> Any suggestions?
> Thanks!
> Boris
> 
> 
> ___
> SailfishOS.org Devel mailing list
> 
> ___
> SailfishOS.org Devel mailing list
> 
> 
> 
> ___
> SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Limitations for icons in the event screen?

[Andrey Kozhevnikov]

i have white background instead of transparent.

On 21.01.2014 19:37, Andrea Bernabei wrote:

hello Boris,

do they *always* show with black background? (msybe only after reboot, 
or maybe only when they appear, stuff like that)


I noticed that also happens with android apps notifications, but not 
always! so in that case it's probably a bug somewhere in the image 
handling



2014/1/21 Andrey Kozhevnikov >


i had same question on 3rd Januarry. Still unanswered...
https://lists.sailfishos.org/pipermail/devel/2014-January/002482.html


On 21.01.2014 19:28, Boris Pohler wrote:

Hi,
are there any limitations/requirements for icons used by
notifications
on the event screen? I ask because I have a problem with
transparent
backgrounds of the icons, see screenshot in the link below:
https://dl.dropboxusercontent.com/u/107743837/20140121141345.jpg
The icons (64x64px, size about 1kB) have transparent
background and for
the first few starts everything is fine, but then the transparent
background turns to black.
I looked at the icons used by jolla
at /usr/share/themes/jolla-ambient/meegotouch/icons/ but
didn't found
any difference.
Any suggestions?
Thanks!
Boris


___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list




___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Limitations for icons in the event screen?

[Andrea Bernabei]

hello Boris,

do they *always* show with black background? (msybe only after reboot, or
maybe only when they appear, stuff like that)

I noticed that also happens with android apps notifications, but not
always! so in that case it's probably a bug somewhere in the image handling


2014/1/21 Andrey Kozhevnikov 

> i had same question on 3rd Januarry. Still unanswered...
> https://lists.sailfishos.org/pipermail/devel/2014-January/002482.html
>
>
> On 21.01.2014 19:28, Boris Pohler wrote:
>
>> Hi,
>> are there any limitations/requirements for icons used by notifications
>> on the event screen? I ask because I have a problem with transparent
>> backgrounds of the icons, see screenshot in the link below:
>> https://dl.dropboxusercontent.com/u/107743837/20140121141345.jpg
>> The icons (64x64px, size about 1kB) have transparent background and for
>> the first few starts everything is fine, but then the transparent
>> background turns to black.
>> I looked at the icons used by jolla
>> at /usr/share/themes/jolla-ambient/meegotouch/icons/ but didn't found
>> any difference.
>> Any suggestions?
>> Thanks!
>> Boris
>>
>>
>> ___
>> SailfishOS.org Devel mailing list
>>
>
> ___
> SailfishOS.org Devel mailing list
>
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Limitations for icons in the event screen?

[Andrey Kozhevnikov]

i had same question on 3rd Januarry. Still unanswered... 
https://lists.sailfishos.org/pipermail/devel/2014-January/002482.html


On 21.01.2014 19:28, Boris Pohler wrote:

Hi,
are there any limitations/requirements for icons used by notifications
on the event screen? I ask because I have a problem with transparent
backgrounds of the icons, see screenshot in the link below:
https://dl.dropboxusercontent.com/u/107743837/20140121141345.jpg
The icons (64x64px, size about 1kB) have transparent background and for
the first few starts everything is fine, but then the transparent
background turns to black.
I looked at the icons used by jolla
at /usr/share/themes/jolla-ambient/meegotouch/icons/ but didn't found
any difference.
Any suggestions?
Thanks!
Boris


___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

[SailfishDevel] Limitations for icons in the event screen?

[Boris Pohler]

Hi,
are there any limitations/requirements for icons used by notifications
on the event screen? I ask because I have a problem with transparent
backgrounds of the icons, see screenshot in the link below:
https://dl.dropboxusercontent.com/u/107743837/20140121141345.jpg
The icons (64x64px, size about 1kB) have transparent background and for
the first few starts everything is fine, but then the transparent
background turns to black.
I looked at the icons used by jolla
at /usr/share/themes/jolla-ambient/meegotouch/icons/ but didn't found
any difference.
Any suggestions?
Thanks!
Boris


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

[kaa]

Bla, bla , bla .. FUD .. bla bla bla

Harbour QA input is allways binary blob! And as security specialist i 
say: Harbour QA not able to force true security. Too many security holes 
is in OS - for now Jolla's/SailfishOS security is tragic. And after 
afera with internet connectivity from simple app for LED light .. passed 
thru QA without any problem .. sorry no one believe to Harbour QA .. LOL


When developer make app from git on OBS .. and binary blob have right 
checkum in Openrepos .. this is better then Harbour. And Openrepos 
working on connect/bridge with OBS. OBS bulding is only one true 
bin-blobs control. With OBS we know: THIS blob is builded from THIS 
source. Harbour way is bullshit. ..  sorry ..


In short: Openrepos with OBS provide better security then harbour .. 
Howgh ..

For people with brain Openrepos is not problem.

Jolla make too many wrong decisions and in combine with lack of 
informations .. i am two steps to go to furture with fully open Nemo. 
Maybe take my work to this diretion will be better decision ..


Kaacz

Dne 21.1.2014 13:15, Joona Hoikkala napsal(a):

Openrepos doesn't have any QA process, and you can publish your own closed 
source blobs through it.
Meaning that someone could potentially push an application that steals or 
destroys users data.

Harbour is very much needed.

--
Joona


On 21 Jan 2014, at 12:59, kaa  wrote:


Thank you for quick answer.

But now i have other question: after this way .. why we need Harbour ? Nope ..

Openrepos with own client is better on both sides.

Openrepos backend/repo use standard linux rules, Harbour is too much 
restricted. Mainly for lack of many Jolla decisions. Or for example terrible 
decision about naming convention. :(

Openrepos client is better also, easy and user friendly with more info and very 
clear. Harbour client is confused and buggy - still show me nonclearable 
notifications about app updates .. but i have better version from openrepos. 
Harbour client see :different: not :higher: version. And client not able to 
solve this situation. Crap.

Who cares about problematic Harbour when we have OpenRepos? Jolla missed chance 
..
When developer use OpenRepos, have not one reason for move to bloody Harbour 
after ...

Kaacz



Dne 13.1.2014 13:34, Jonni Rainisto napsal(a):

Again not official answer: but with current rules right way is to setup 
application 1st in Openrepos or OBS which uses root capas, and after 1000+ 
people have installed it and found it working and stable, then push it to 
Harbour, and apply for exception for intake rules. As applications with proven 
track record and demand can have exceptions to approval rules.

In a long run we hopefully have some better API or rules to solve this. I'm 
only saying current situation.

re, Jonni

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of kaa [k...@iol.cz]
Sent: Monday, January 13, 2014 2:22 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

.. runned as root .. because doing work on root level.

Simple apps like "life years/months/days" are nice, but we need many
better, stronger, "under-skin" apps..
Like Profilematic, call blocker/recorder/assist, PhotoSync & many others
with daemon running.
Without this kind of apps Jolla phone is crap worse than Android...
As N9 user .. now I may use Jolla phone only with pain and frustration.

Then I have question:

What is right way to set-up "run daemon now and after boot" right after
install .. without post-inst script in RPM ?

And I want answer, please ...

Thanks
Kaacz

Dne 11.1.2014 11:41, Jonni Rainisto napsal(a):

because they are runned as root.

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Andrey Kozhevnikov [coderusin...@gmail.com]
Sent: Saturday, January 11, 2014 11:22 AM
To: Sailfish OS Developers
Subject: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

Why RPM scriptlets not allowed to harbour?
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list



___
SailfishOS.org Devel mailing list

[SailfishDevel] [Sailfish IDE] Can't run app in Debug mode anymore

[Sylvain B .]

Hello,
This week-end, I wanted to investigate some segfault (easily reproducible, see 
here: https://lists.sailfishos.org/pipermail/devel/2013-December/001707.html )
And for some reason, I found out that I am not able to run an app in Debug 
anymore :/
Few weeks ago it worked, but now, the Run Debug command just get stuck forever 
at the "Lauching" stage (after deployment)You can find below the last lines of 
the debug logs (I don't know why copy/past add a "d" at the beginning of each 
line)As anybody encountered the same issue? Any idea of what I can do?

ps: I tried to uninstall/reinstall the SDK and recreate an application from 
scratch, but it doesn't help.pps: If you want the very simple segfaulting 
application described in the link above, I've put it here: 
http://sthocs.free.fr/sailfish/Hello-0.1-1.armv7hl.rpm. Click on any Item to go 
to the second page and pull back to the first page: segfault.

Thank you,Sylvain.


dState changed from DebuggerNotReady(0) to EngineSetupRequested(1)
dQUEUE: SETUP ENGINE
dNOTE: REQUEST REMOTE SETUP
dCALL: SETUP ENGINE
dEXAMINING 
C:/Users/Sylvain/Sailfish/build-Hello-MerSDK_SailfishOS_i486_x86-Debug/Hello
dELF SECTIONS:  .interp .note.ABI-tag .note.gnu.build-id .gnu.hash .dynsym 
.dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text .fini 
.rodata .eh_frame_hdr .eh_frame .init_array .ctors .dtors .jcr .dynamic .got 
.got.plt .data .bss .comment .debug_aranges .debug_info .debug_abbrev 
.debug_line .debug_str .debug_ranges .debug_types .gdb_index .shstrtab .symtab 
.strtab 
dNOTE: REQUEST REMOTE SETUP
dCALL: SETUP ENGINE
dEXAMINING 
C:/Users/Sylvain/Sailfish/build-Hello-MerSDK_SailfishOS_i486_x86-Debug/Hello
dELF SECTIONS:  .interp .note.ABI-tag .note.gnu.build-id .gnu.hash .dynsym 
.dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text .fini 
.rodata .eh_frame_hdr .eh_frame .init_array .ctors .dtors .jcr .dynamic .got 
.got.plt .data .bss .comment .debug_aranges .debug_info .debug_abbrev 
.debug_line .debug_str .debug_ranges .debug_types .gdb_index .shstrtab .symtab 
.strtab 
dTRYING TO START ADAPTER
dNOTE: REQUEST REMOTE SETUP


  ___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

[Andrey Kozhevnikov]

harbour is just something built-in phone. openrepos is categorized 
catalogue. if no openrepos users will download rpm files from internet 
and nothing will be changed. its silly to think about openrepos in this 
way :)


On 21.01.2014 18:15, Joona Hoikkala wrote:

Openrepos doesn't have any QA process, and you can publish your own closed 
source blobs through it.
Meaning that someone could potentially push an application that steals or 
destroys users data.

Harbour is very much needed.

--
Joona


On 21 Jan 2014, at 12:59, kaa  wrote:


Thank you for quick answer.

But now i have other question: after this way .. why we need Harbour ? Nope ..

Openrepos with own client is better on both sides.

Openrepos backend/repo use standard linux rules, Harbour is too much 
restricted. Mainly for lack of many Jolla decisions. Or for example terrible 
decision about naming convention. :(

Openrepos client is better also, easy and user friendly with more info and very 
clear. Harbour client is confused and buggy - still show me nonclearable 
notifications about app updates .. but i have better version from openrepos. 
Harbour client see :different: not :higher: version. And client not able to 
solve this situation. Crap.

Who cares about problematic Harbour when we have OpenRepos? Jolla missed chance 
..
When developer use OpenRepos, have not one reason for move to bloody Harbour 
after ...

Kaacz



Dne 13.1.2014 13:34, Jonni Rainisto napsal(a):

Again not official answer: but with current rules right way is to setup 
application 1st in Openrepos or OBS which uses root capas, and after 1000+ 
people have installed it and found it working and stable, then push it to 
Harbour, and apply for exception for intake rules. As applications with proven 
track record and demand can have exceptions to approval rules.

In a long run we hopefully have some better API or rules to solve this. I'm 
only saying current situation.

re, Jonni

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of kaa [k...@iol.cz]
Sent: Monday, January 13, 2014 2:22 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

.. runned as root .. because doing work on root level.

Simple apps like "life years/months/days" are nice, but we need many
better, stronger, "under-skin" apps..
Like Profilematic, call blocker/recorder/assist, PhotoSync & many others
with daemon running.
Without this kind of apps Jolla phone is crap worse than Android...
As N9 user .. now I may use Jolla phone only with pain and frustration.

Then I have question:

What is right way to set-up "run daemon now and after boot" right after
install .. without post-inst script in RPM ?

And I want answer, please ...

Thanks
Kaacz

Dne 11.1.2014 11:41, Jonni Rainisto napsal(a):

because they are runned as root.

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Andrey Kozhevnikov [coderusin...@gmail.com]
Sent: Saturday, January 11, 2014 11:22 AM
To: Sailfish OS Developers
Subject: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

Why RPM scriptlets not allowed to harbour?
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Project Kits lost on Target Refresh

[christopher . lamb]

Hi Juha

Thanks.

The kits are easily added again, and this is no problem if only one or  
two projects are open.


But I often have 5 or more open ...

Another irritating strange behaviour in QtCreator, again with several  
projects open, Is that If I have one project selected to build and  
run, but the highlight in the Project Explorer (top left pane of  
QtCreator) is on a file in a second project, then the build fails  
because it gets muddled up.


e.g below I am building GSTTorch, but the highlight is on a file in  
QMLTorch. It tries to build GSTTorch using files from QMLTorch!


As I am frequently switching between projects I encounter this error  
many times!


Chris


RPM build errors:
error: File not found: /home/deploy/installroot/usr/share/QMLTorch/qml


error: File not found:  
/home/deploy/installroot/usr/share/applications/QMLTorch.desktop

error:


File not found:  
/home/deploy/installroot/usr/share/icons/hicolor/86x86/apps/QMLTorch.png

error: File not found: /home/deploy/installroot/usr/share/QMLTorch



File not found: /home/deploy/installroot/usr/share/QMLTorch/qml
File not found:  
/home/deploy/installroot/usr/share/applications/QMLTorch.desktop
File not found:  
/home/deploy/installroot/usr/share/icons/hicolor/86x86/apps/QMLTorch.png

File not found: /home/deploy/installroot/usr/share/QMLTorch




13:10:48: The process  
"/Users/christopherlamb/.config/SailfishAlpha3/mer-sdk-tools/MerSDK/SailfishOS-i486-x86/deploy" exited with code  
1.
Error while building/deploying project GSTTorch (kit:  
MerSDK-SailfishOS-i486-x86)



Zitat von "Juha Kallioinen" :


On 21.01.2014 09:17, christopher.l...@thurweb.ch wrote:

Hi All

If I do a QtCreator / SailfishOS/ Targets / Manage Targets /  
 / Manage / Sync, with project(s) open in QtCreator, then I  
lose the kits of the open project(s), and have to re-add these.




Hi Chris,

yes it's an unfortunate side effect of the way the build engine/qt  
creator interface has been implemented. This should be fixed in some  
future release, but is not a high priority.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list





___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

[Joona Hoikkala]

Openrepos doesn't have any QA process, and you can publish your own closed 
source blobs through it. 
Meaning that someone could potentially push an application that steals or 
destroys users data.

Harbour is very much needed.

--
Joona


On 21 Jan 2014, at 12:59, kaa  wrote:

> Thank you for quick answer.
> 
> But now i have other question: after this way .. why we need Harbour ? Nope ..
> 
> Openrepos with own client is better on both sides.
> 
> Openrepos backend/repo use standard linux rules, Harbour is too much 
> restricted. Mainly for lack of many Jolla decisions. Or for example terrible 
> decision about naming convention. :(
> 
> Openrepos client is better also, easy and user friendly with more info and 
> very clear. Harbour client is confused and buggy - still show me nonclearable 
> notifications about app updates .. but i have better version from openrepos. 
> Harbour client see :different: not :higher: version. And client not able to 
> solve this situation. Crap.
> 
> Who cares about problematic Harbour when we have OpenRepos? Jolla missed 
> chance ..
> When developer use OpenRepos, have not one reason for move to bloody Harbour 
> after ...
> 
> Kaacz
> 
> 
> 
> Dne 13.1.2014 13:34, Jonni Rainisto napsal(a):
>> Again not official answer: but with current rules right way is to setup 
>> application 1st in Openrepos or OBS which uses root capas, and after 1000+ 
>> people have installed it and found it working and stable, then push it to 
>> Harbour, and apply for exception for intake rules. As applications with 
>> proven track record and demand can have exceptions to approval rules.
>> 
>> In a long run we hopefully have some better API or rules to solve this. I'm 
>> only saying current situation.
>> 
>> re, Jonni
>> 
>> From: devel-boun...@lists.sailfishos.org 
>> [devel-boun...@lists.sailfishos.org] on behalf of kaa [k...@iol.cz]
>> Sent: Monday, January 13, 2014 2:22 PM
>> To: Sailfish OS Developers
>> Subject: Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour
>> 
>> .. runned as root .. because doing work on root level.
>> 
>> Simple apps like "life years/months/days" are nice, but we need many
>> better, stronger, "under-skin" apps..
>> Like Profilematic, call blocker/recorder/assist, PhotoSync & many others
>> with daemon running.
>> Without this kind of apps Jolla phone is crap worse than Android...
>> As N9 user .. now I may use Jolla phone only with pain and frustration.
>> 
>> Then I have question:
>> 
>> What is right way to set-up "run daemon now and after boot" right after
>> install .. without post-inst script in RPM ?
>> 
>> And I want answer, please ...
>> 
>> Thanks
>> Kaacz
>> 
>> Dne 11.1.2014 11:41, Jonni Rainisto napsal(a):
>>> because they are runned as root.
>>> 
>>> From: devel-boun...@lists.sailfishos.org 
>>> [devel-boun...@lists.sailfishos.org] on behalf of Andrey Kozhevnikov 
>>> [coderusin...@gmail.com]
>>> Sent: Saturday, January 11, 2014 11:22 AM
>>> To: Sailfish OS Developers
>>> Subject: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour
>>> 
>>> Why RPM scriptlets not allowed to harbour?
>>> ___
>>> SailfishOS.org Devel mailing list
>>> ___
>>> SailfishOS.org Devel mailing list
>>> 
>> ___
>> SailfishOS.org Devel mailing list
>> ___
>> SailfishOS.org Devel mailing list
>> 
> 
> ___
> SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

[kaa]

Thank you for quick answer.

But now i have other question: after this way .. why we need Harbour ? 
Nope ..


Openrepos with own client is better on both sides.

Openrepos backend/repo use standard linux rules, Harbour is too much 
restricted. Mainly for lack of many Jolla decisions. Or for example 
terrible decision about naming convention. :(


Openrepos client is better also, easy and user friendly with more info 
and very clear. Harbour client is confused and buggy - still show me 
nonclearable notifications about app updates .. but i have better 
version from openrepos. Harbour client see :different: not :higher: 
version. And client not able to solve this situation. Crap.


Who cares about problematic Harbour when we have OpenRepos? Jolla missed 
chance ..
When developer use OpenRepos, have not one reason for move to bloody 
Harbour after ...


Kaacz



Dne 13.1.2014 13:34, Jonni Rainisto napsal(a):

Again not official answer: but with current rules right way is to setup 
application 1st in Openrepos or OBS which uses root capas, and after 1000+ 
people have installed it and found it working and stable, then push it to 
Harbour, and apply for exception for intake rules. As applications with proven 
track record and demand can have exceptions to approval rules.

In a long run we hopefully have some better API or rules to solve this. I'm 
only saying current situation.

re, Jonni

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of kaa [k...@iol.cz]
Sent: Monday, January 13, 2014 2:22 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

.. runned as root .. because doing work on root level.

Simple apps like "life years/months/days" are nice, but we need many
better, stronger, "under-skin" apps..
Like Profilematic, call blocker/recorder/assist, PhotoSync & many others
with daemon running.
Without this kind of apps Jolla phone is crap worse than Android...
As N9 user .. now I may use Jolla phone only with pain and frustration.

Then I have question:

What is right way to set-up "run daemon now and after boot" right after
install .. without post-inst script in RPM ?

And I want answer, please ...

Thanks
Kaacz

Dne 11.1.2014 11:41, Jonni Rainisto napsal(a):

because they are runned as root.

From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Andrey Kozhevnikov [coderusin...@gmail.com]
Sent: Saturday, January 11, 2014 11:22 AM
To: Sailfish OS Developers
Subject: [SailfishDevel] Scriptlets in RPM hot allowed to Harbour

Why RPM scriptlets not allowed to harbour?
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list



___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Project Kits lost on Target Refresh

[Juha Kallioinen]

On 21.01.2014 09:17, christopher.l...@thurweb.ch wrote:

Hi All

If I do a QtCreator / SailfishOS/ Targets / Manage Targets /  
/ Manage / Sync, with project(s) open in QtCreator, then I lose the 
kits of the open project(s), and have to re-add these.




Hi Chris,

yes it's an unfortunate side effect of the way the build engine/qt 
creator interface has been implemented. This should be fixed in some 
future release, but is not a high priority.


Best regards,
 Juha

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Harbour compliant way to read contacts

[Harald Schmitt]

Am 21.01.2014 11:28, schrieb Andrey Kozhevnikov:
> On 21.01.2014 16:15, Harald Schmitt wrote:
>> Hi,
>>
>> I tried to use QContactManager, QContact and so on for an app I'd like
>> to publish on harbour, but the line in my .pro file
>> PKGCONFIG += Qt5Contacts
>> is rejected by the new validation tool.
>> How can I access contacts in a harbour app? Is there an example?
>>
>> Best regards,
>> Harald
>
> is fetching Contacts allowed to Harbour at all?
> 
If there is no way for an harbour app at all, that would be an answer to
my question. Maybe it is only allowed for an android app?
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Harbour compliant way to read contacts

[Andrey Kozhevnikov]

is fetching Contacts allowed to Harbour at all?

On 21.01.2014 16:15, Harald Schmitt wrote:

Hi,

I tried to use QContactManager, QContact and so on for an app I'd like
to publish on harbour, but the line in my .pro file
PKGCONFIG += Qt5Contacts
is rejected by the new validation tool.
How can I access contacts in a harbour app? Is there an example?

Best regards,
Harald
___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

[SailfishDevel] SMS wishlist & a possible issue

[Seppo Tiainen]

Hi,

I would like to add two more items to the SMS wish list:

1) If you use Qt.openUrlExternally("sms:" + smsNumber + "?body=" +
smsText); in your app you will not be returned back to the app after
sending but instead you will have to close the sms sending UI and and
'maximize' the app.  In some cases this may result in some kind of error
(stack? - black screen, reboot). I think a fix is needed. - The same method
for 'tel:' works great! Please don't change that. Something similar for the
'sms:' would be really cool.

2) Regarding item 1), there is no display of the recipient (number/contact)
of the SMS when you are supposed to finally send the text, unless you
realize you can swipe to see that and then come back. Risky?

regards,
Seppo
___
SailfishOS.org Devel mailing list

[SailfishDevel] Harbour compliant way to read contacts

[Harald Schmitt]

Hi,

I tried to use QContactManager, QContact and so on for an app I'd like
to publish on harbour, but the line in my .pro file
PKGCONFIG += Qt5Contacts
is rejected by the new validation tool.
How can I access contacts in a harbour app? Is there an example?

Best regards,
Harald
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] PKGCONFIG entry in project .pro file

[Andrey Kozhevnikov]

check this: http://paste.ubuntu.com/6790746/

On 21.01.2014 15:59, christopher.l...@thurweb.ch wrote:

Hi All

When / why is a PKGCONFIG entry required in a Sailfish .pro file?

Is there a better way of specifying the same (e.g. via a .yaml entry)?

As an example, I am playing around with GStreamer. If I have the 
following entry n my .pro file then the project builds and deploys ok.


PKGCONFIG += gstreamer-0.10

However if the entry is missing, then I get the error:

gst/gstelement.h: No such file or directory

Chris


___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

[SailfishDevel] PKGCONFIG entry in project .pro file

[christopher . lamb]

Hi All

When / why is a PKGCONFIG entry required in a Sailfish .pro file?

Is there a better way of specifying the same (e.g. via a .yaml entry)?

As an example, I am playing around with GStreamer. If I have the  
following entry n my .pro file then the project builds and deploys ok.


PKGCONFIG += gstreamer-0.10

However if the entry is missing, then I get the error:

gst/gstelement.h: No such file or directory

Chris


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Fwd: Re: QGeoSatelliteInfoSource in Sailfish

[dcaliste]

Hello Aaron and list members,

Selon Aaron McCarthy :
> > but the direction is missing from QGeoPositionInfo, the method
> > hasAttribute() on a valid GPS fix returns false, always. How to get the
> > direction? Should one calculate it by hand ?
> This is a bug in the Geoclue positioning plugin in Qt. I have filed a bug in
> the Qt bug tracker: https://bugreports.qt-project.org/browse/QTBUG-36298
Ah, ok I see thanks for deposing a bug. I will follow it and as a work around,
I'll use the previous position to approximate direction.

Have a nice day,

Damien.
___
SailfishOS.org Devel mailing list