Re: [SailfishDevel] SQLite linking

[Caliste Damien]

Hello,

Le samedi 04 mars 2017, rinigus a écrit :
> one month + 10 days later - no response for PR nor SQLite linking from
> Harbour / Jolla devs.
Well, the  topic of adding allowed libraries seems to be a sensitive
one, without easy answering. You may propose this discussion for a
coming community IRC meeting. Next one is next Monday, you may add a
topic, or prefer to wait for the next one, announcing your topic early
so Jaymz may arrange to get answers (at least a negative one).

You may try to ask on IRC directly who you may ping to get a review or
a discussion of your PR, sometimes they don't see them.

Good luck,

Damien.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] SQLite linking

[rinigus]

Hi Damien,

agreed, the topic of adding allowed libraries seems to be a sensitive one.
Which, in many cases, leads to inhibited development and wasting of time.
While I understand the limitations imposed on rather infrequently used
libraries due to inability to ensure Q&A, sqlite is probably used at many
parts of SFOS and, as a result, passes Q&A anyway. So, by not letting us to
link to it directly and forcing to bundle it with the app, Jolla is just
introducing an additional source for non-patched software (I can just miss
some bugfix on that lib).

As for goodness of IRC, the meetings are, by definition, arranged at some
time. So far, its for me at the time when I am busy with my job and just
cannot commit myself to hobby-related issues.

I would have thought that this mailing list and github issues/PRs should be
sufficient channels to get a feedback. In the end, Jolla employees are
posting over here and are reading messages over here as well (I think its
reasonable to expect it from anyone posting over here).

cheers,

Rinigus

On Sat, Mar 4, 2017 at 12:27 PM, Caliste Damien  wrote:

> Hello,
>
> Le samedi 04 mars 2017, rinigus a écrit :
> > one month + 10 days later - no response for PR nor SQLite linking from
> > Harbour / Jolla devs.
> Well, the  topic of adding allowed libraries seems to be a sensitive
> one, without easy answering. You may propose this discussion for a
> coming community IRC meeting. Next one is next Monday, you may add a
> topic, or prefer to wait for the next one, announcing your topic early
> so Jaymz may arrange to get answers (at least a negative one).
>
> You may try to ask on IRC directly who you may ping to get a review or
> a discussion of your PR, sometimes they don't see them.
>
> Good luck,
>
> Damien.
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscribe@lists.
> sailfishos.org
>
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] SQLite linking

[Marcin Mielniczuk]

You can always use OpenRepos...

On March 4, 2017 8:50:37 AM GMT+01:00, rinigus  wrote:
>Hi,
>
>one month + 10 days later - no response for PR nor SQLite linking from
>Harbour / Jolla devs. Already had to ship few versions with SQLite
>bundled
>with application as well. I'd say its rather poor response times
>already
>now (with the response time not reached yet).
>
>Rinigus
>
>
>On Wed, Jan 18, 2017 at 4:30 PM, rinigus  wrote:
>
>> Slava,
>>
>> thank you for this constructive suggestion. I submitted PR
>> https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/pull/86 to
>add
>> sqlite into the list of allowed libraries. Hopefully, it will be
>accepted.
>>
>> Best wishes,
>>
>> Rinigus
>>
>> On Wed, Jan 18, 2017 at 3:29 PM, Slava Monich
>
>> wrote:
>>
>>> I believe rpm automatically detects the dependencies, even if they
>are
>>> not in the spec. Removing the dependency from the spec might not
>help.
>>> There may be some hackish ways of removing a dependency from the rpm
>>> headers but I don't think that it would be a good idea. Better to
>spend
>>> time on hacking something more useful than that.
>>>
>>> Another approach is to load the library with dlopen, e.g.
>>>
>>>
>https://github.com/monich/harbour-books/blob/master/app/stubs/libmagic.c
>>>
>>> This allows you to get around the harbour limitations and yet in
>every
>>> other respect it's as good as linking with the system library. Of
>course by
>>> doing so you assume the risk of using the unsupported api.
>Obviously, this
>>> kind of trick should only be done to very stable libraries that are
>>> extremely unlikely to disappear from the system and have a proven
>track
>>> record of evolving in a backward compatible manner.
>>>
>>> I think the best solution is to add sqlite3 to
>allowed_libraries.conf and
>>> submit a pull request:
>>>
>>> https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blo
>>> b/master/allowed_libraries.conf
>>>
>>> Cheers,
>>>
>>> -Slava
>>>
>>>
 Is the automatic checker not allowing it through with sqlite3 as a
 requirement? Are you sure that you used the packagename used on
>jolla
 systems for the requirement?

>>>
>>> During deployment as RPM, the specific error is
>>>
>>>  Requires
>>>
>>> 
>>>
>>> ERROR [libsqlite3.so.0] Cannot require shared library:
>'libsqlite3.so.0'
>>>
>>> INFO [harbour-osmscout-server] Please see our FAQ here:
>>>
>https://harbour.jolla.com/faq#2.6.0
>>> how to use '__provides_exclude_from' and '__requires_exclude' .spec
>file to
>>> avoid that
>>>
>>> FAILED
>>>
>>>
>>> earlier versions of this app were published in the store without any
>>> issues. Its a part of the app evolution to require sqlite3 for its
>>> function, at least for a time being.
>>>
>>> I agree that static linking of sqlite3 is not necessary and can be
>>> considered as a bloat. Hence my question :)
>>>
>>> rinigus
>>>
>>>
>>> ___
>>> SailfishOS.org Devel mailing list
>>> To unsubscribe, please send a mail to
>devel-unsubscr...@lists.sailfishos.org
>>>
>>>
>>>
>>> ___
>>> SailfishOS.org Devel mailing list
>>> To unsubscribe, please send a mail to devel-unsubscribe@lists.sailfi
>>> shos.org
>>>
>>
>>

-- 
Sent from my mobile. Please excuse my brevity.___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] SQLite linking

[rinigus]

Re OpenRepos: Sure, and I do. And through bundling I am publishing
@Harbour. But the main issue is the lack of response for a rather simple
request. Even a negative response is a response.

Sorry for complains. Enjoy the weekend and let's see if Jolla devs would
respond during the work hours :)

rinigus

On Sat, Mar 4, 2017 at 2:22 PM, Marcin Mielniczuk 
wrote:

> You can always use OpenRepos...
>
>
> On March 4, 2017 8:50:37 AM GMT+01:00, rinigus 
> wrote:
>>
>> Hi,
>>
>> one month + 10 days later - no response for PR nor SQLite linking from
>> Harbour / Jolla devs. Already had to ship few versions with SQLite bundled
>> with application as well. I'd say its rather poor response times already
>> now (with the response time not reached yet).
>>
>> Rinigus
>>
>>
>> On Wed, Jan 18, 2017 at 4:30 PM, rinigus  wrote:
>>
>>> Slava,
>>>
>>> thank you for this constructive suggestion. I submitted PR
>>> https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/pull/86 to add
>>> sqlite into the list of allowed libraries. Hopefully, it will be accepted.
>>>
>>> Best wishes,
>>>
>>> Rinigus
>>>
>>> On Wed, Jan 18, 2017 at 3:29 PM, Slava Monich 
>>> wrote:
>>>
 I believe rpm automatically detects the dependencies, even if they are
 not in the spec. Removing the dependency from the spec might not help.
 There may be some hackish ways of removing a dependency from the rpm
 headers but I don't think that it would be a good idea. Better to spend
 time on hacking something more useful than that.

 Another approach is to load the library with dlopen, e.g.

 https://github.com/monich/harbour-books/blob/master/app/stub
 s/libmagic.c

 This allows you to get around the harbour limitations and yet in every
 other respect it's as good as linking with the system library. Of course by
 doing so you assume the risk of using the unsupported api. Obviously, this
 kind of trick should only be done to very stable libraries that are
 extremely unlikely to disappear from the system and have a proven track
 record of evolving in a backward compatible manner.

 I think the best solution is to add sqlite3 to allowed_libraries.conf
 and submit a pull request:

 https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blo
 b/master/allowed_libraries.conf

 Cheers,

 -Slava


> Is the automatic checker not allowing it through with sqlite3 as a
> requirement? Are you sure that you used the packagename used on jolla
> systems for the requirement?
>

 During deployment as RPM, the specific error is

  Requires

 

 ERROR [libsqlite3.so.0] Cannot require shared library:
 'libsqlite3.so.0'

 INFO [harbour-osmscout-server] Please see our FAQ here:
 https://harbour.jolla.com/faq#
 2.6.0 how to use '__provides_exclude_from' and '__requires_exclude'
 .spec file to avoid that

 FAILED


 earlier versions of this app were published in the store without any
 issues. Its a part of the app evolution to require sqlite3 for its
 function, at least for a time being.

 I agree that static linking of sqlite3 is not necessary and can be
 considered as a bloat. Hence my question :)

 rinigus


 ___
 SailfishOS.org Devel mailing list
 To unsubscribe, please send a mail to 
 devel-unsubscr...@lists.sailfishos.org



 ___
 SailfishOS.org Devel mailing list
 To unsubscribe, please send a mail to devel-unsubscribe@lists.sailfi
 shos.org

>>>
>>>
>>
> --
> Sent from my mobile. Please excuse my brevity.
>
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] SQLite linking

[Andrew Branson]

Hi,

I've had a look internally about this, and it's caught up in a larger overhaul 
of the whitelist and harbour rules aiming to make development more attractive 
to developers while remaining maintainable. This is part of the reason you 
haven't had any feedback yet, but also everyone's got caught up in the huge 
amount of work lately that you've now seen some news about.

It's not great when external PRs and bugs on the merproject bugzilla appear to 
look dead because they're blocked internally but not visibly, especially when 
someone's taken the time and trouble to investigate and submit something. Sorry 
about that. Even if the internal progress on such things can't be made public, 
an acknowledgement would be nice. The apparent silence doesn't mean your 
efforts aren't appreciated nor influential.

Hope that helps a bit,

Andrew

On Saturday, 4 March 2017, rinigus wrote:
> Re OpenRepos: Sure, and I do. And through bundling I am publishing @Harbour. 
> But the main issue is the lack of response for a rather simple request. Even 
> a negative response is a response. 
> 
> 
> Sorry for complains. Enjoy the weekend and let's see if Jolla devs would 
> respond during the work hours :)
> 
> 
> rinigus
> 
> 
> On Sat, Mar 4, 2017 at 2:22 PM, Marcin Mielniczuk  
> wrote:
> 
> You can always use OpenRepos... 
> 
> 
> 
> On March 4, 2017 8:50:37 AM GMT+01:00, rinigus  wrote: 
> Hi, 
> 
> 
> one month + 10 days later - no response for PR nor SQLite linking from 
> Harbour / Jolla devs. Already had to ship few versions with SQLite bundled 
> with application as well. I'd say its rather poor response times already now 
> (with the response time not reached yet). 
> 
> 
> Rinigus
> 
> 
> 
> 
> On Wed, Jan 18, 2017 at 4:30 PM, rinigus  wrote:
> 
> Slava, 
> 
> 
> thank you for this constructive suggestion. I submitted PR 
> https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/pull/86 to add 
> sqlite into the list of allowed libraries. Hopefully, it will be accepted.
> 
> 
> Best wishes,
> 
> 
> Rinigus
> 
> 
> On Wed, Jan 18, 2017 at 3:29 PM, Slava Monich  wrote:
> 
> I believe rpm automatically detects the dependencies, even if they are not in 
> the spec. Removing the dependency from the spec might not help. There may be 
> some hackish ways of removing a dependency from the rpm headers but I don't 
> think that it would be a good idea. Better to spend time on hacking something 
> more useful than that.
> 
> Another approach is to load the library with dlopen, e.g.
> https://github.com/monich/harbour-books/blob/master/app/stubs/libmagic.c
> This allows you to get around the harbour limitations and yet in every other 
> respect it's as good as linking with the system library. Of course by doing 
> so you assume the risk of using the unsupported api. Obviously, this kind of 
> trick should only be done to very stable libraries that are extremely 
> unlikely to disappear from the system and have a proven track record of 
> evolving in a backward compatible manner.
> I think the best solution is to add sqlite3 to allowed_libraries.conf and 
> submit a pull request:
> https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/master/allowed_libraries.conf
> 
> Cheers,
> 
> -Slava
> 
> 
> 
> 
> 
> Is the automatic checker not allowing it through with sqlite3 as a 
> requirement? Are you sure that you used the packagename used on jolla systems 
> for the requirement?
> 
> 
> During deployment as RPM, the specific error is 
> 
> 
>  Requires
> 
> ERROR [libsqlite3.so.0] Cannot require shared library: 'libsqlite3.so.0'
> INFO [harbour-osmscout-server] Please see our FAQ here: 
> https://harbour.jolla.com/faq#2.6.0 how to use '__provides_exclude_from' and 
> '__requires_exclude' .spec file to avoid that
> FAILED
> 
> 
> earlier versions of this app were published in the store without any issues. 
> Its a part of the app evolution to require sqlite3 for its function, at least 
> for a time being.
> 
> 
> I agree that static linking of sqlite3 is not necessary and can be considered 
> as a bloat. Hence my question :)
> 
> 
> rinigus
> 
> 
> 
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
> 
> 
> 
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
> 
> 
> 
> 
> 
> 
> 
> -- 
> 
> Sent from my mobile. Please excuse my brevity.
> 
>

-- 
Sent from my Jolla
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] SQLite linking

[rinigus]

Hi,

thank you very much for the response and explanation. Looking forward to
see the new whitelist / harbour rules. Its fine to take time to do it
properly, thanks for the feedback.

Best wishes,

Rinigus

On Sat, Mar 4, 2017 at 3:15 PM, Andrew Branson 
wrote:

> Hi,
>
> I've had a look internally about this, and it's caught up in a larger
> overhaul of the whitelist and harbour rules aiming to make development more
> attractive to developers while remaining maintainable. This is part of the
> reason you haven't had any feedback yet, but also everyone's got caught up
> in the huge amount of work lately that you've now seen some news about.
>
> It's not great when external PRs and bugs on the merproject bugzilla
> appear to look dead because they're blocked internally but not visibly,
> especially when someone's taken the time and trouble to investigate and
> submit something. Sorry about that. Even if the internal progress on such
> things can't be made public, an acknowledgement would be nice. The apparent
> silence doesn't mean your efforts aren't appreciated nor influential.
>
> Hope that helps a bit,
>
> Andrew
>
> On Saturday, 4 March 2017, rinigus wrote:
> > Re OpenRepos: Sure, and I do. And through bundling I am publishing
> @Harbour. But the main issue is the lack of response for a rather simple
> request. Even a negative response is a response.
> >
> >
> > Sorry for complains. Enjoy the weekend and let's see if Jolla devs would
> respond during the work hours :)
> >
> >
> > rinigus
> >
> >
> > On Sat, Mar 4, 2017 at 2:22 PM, Marcin Mielniczuk <
> marmistrz...@gmail.com> wrote:
> >
> > You can always use OpenRepos...
> >
> >
> >
> > On March 4, 2017 8:50:37 AM GMT+01:00, rinigus 
> wrote:
> > Hi,
> >
> >
> > one month + 10 days later - no response for PR nor SQLite linking from
> Harbour / Jolla devs. Already had to ship few versions with SQLite bundled
> with application as well. I'd say its rather poor response times already
> now (with the response time not reached yet).
> >
> >
> > Rinigus
> >
> >
> >
> >
> > On Wed, Jan 18, 2017 at 4:30 PM, rinigus  wrote:
> >
> > Slava,
> >
> >
> > thank you for this constructive suggestion. I submitted PR
> https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/pull/86 to add
> sqlite into the list of allowed libraries. Hopefully, it will be accepted.
> >
> >
> > Best wishes,
> >
> >
> > Rinigus
> >
> >
> > On Wed, Jan 18, 2017 at 3:29 PM, Slava Monich 
> wrote:
> >
> > I believe rpm automatically detects the dependencies, even if they are
> not in the spec. Removing the dependency from the spec might not help.
> There may be some hackish ways of removing a dependency from the rpm
> headers but I don't think that it would be a good idea. Better to spend
> time on hacking something more useful than that.
> >
> > Another approach is to load the library with dlopen, e.g.
> > https://github.com/monich/harbour-books/blob/master/app/stubs/libmagic.c
> > This allows you to get around the harbour limitations and yet in every
> other respect it's as good as linking with the system library. Of course by
> doing so you assume the risk of using the unsupported api. Obviously, this
> kind of trick should only be done to very stable libraries that are
> extremely unlikely to disappear from the system and have a proven track
> record of evolving in a backward compatible manner.
> > I think the best solution is to add sqlite3 to allowed_libraries.conf
> and submit a pull request:
> > https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/
> blob/master/allowed_libraries.conf
> >
> > Cheers,
> >
> > -Slava
> >
> >
> >
> >
> >
> > Is the automatic checker not allowing it through with sqlite3 as a
> requirement? Are you sure that you used the packagename used on jolla
> systems for the requirement?
> >
> >
> > During deployment as RPM, the specific error is
> >
> >
> >  Requires
> > 
> > ERROR [libsqlite3.so.0] Cannot require shared library: 'libsqlite3.so.0'
> > INFO [harbour-osmscout-server] Please see our FAQ here:
> https://harbour.jolla.com/faq#2.6.0 how to use '__provides_exclude_from'
> and '__requires_exclude' .spec file to avoid that
> > FAILED
> >
> >
> > earlier versions of this app were published in the store without any
> issues. Its a part of the app evolution to require sqlite3 for its
> function, at least for a time being.
> >
> >
> > I agree that static linking of sqlite3 is not necessary and can be
> considered as a bloat. Hence my question :)
> >
> >
> > rinigus
> >
> >
> >
> > ___
> > SailfishOS.org Devel mailing list
> > To unsubscribe, please send a mail to devel-unsubscribe@lists.
> sailfishos.org
> >
> >
> >
> > ___
> > SailfishOS.org Devel mailing list
> > To unsubscribe, please send a mail to devel-unsubscribe@lists.
> sailfishos.org
> >
> >
> >
> >
> >
> >
> >
> > --
> >
> > Sent from my mobile. Please excuse my brevity.
> >
> >
>
> --
> Sent from my 

[SailfishDevel] FadeAnimator in Sailfish OS 2.1

[Matthias Fehring]

Hi,

with Sailfish OS 2.1 I have a problem when using FadeAnimator in QML for 
example in

Grid {
add: FadeAnimator {}
}

The content is than not shown, but it works on versions prior to 2.1. Is that 
an intended behavior? I could not find any hint in the release notes of Iijoki.

Best greetings
Matthias Fehring
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] FadeAnimator in Sailfish OS 2.1

[Andrey Kozhevnikov]

Use FadeAnimation instead of Animator

-- Исходное сообщение --
От: "Matthias Fehring" 
Кому: "Sailfish OS Developers" 
Отправлено: 04.03.2017 16:55:48
Тема: [SailfishDevel] FadeAnimator in Sailfish OS 2.1


Hi,

with Sailfish OS 2.1 I have a problem when using FadeAnimator in QML 
for

example in

Grid {
add: FadeAnimator {}
}

The content is than not shown, but it works on versions prior to 2.1. 
Is that
an intended behavior? I could not find any hint in the release notes of 
Iijoki.


Best greetings
Matthias Fehring
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

[SailfishDevel] Custom in-app icons

[decon]

Hi,

Does anyone know how to use custom icons (monocrome) with Silica theme 
highlighting?

If I do as described at https://sailfishos.org/develop/docs/jolla-ambient/ it 
works with Silica icons, but I have not managed to do it with custom icons. The 
following code displays the icon, but highlighting does not work when clicking 
on the icon.

IconButton {
icon.source: "qrc:/icons/z1.00/icon-m-case-sensitive.png?" + (pressed ?

 Theme.highlightColor :

 Theme.primaryColor)
onClicked: { console.log("Clicked icon") }
}

There were no error messages in the log either.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Custom in-app icons

[Kimmo Lindholm]

Hi,

You need to make your own iconprovider. Explained here 
https://together.jolla.com/question/44325/iconbutton-how-to-use-own-icons-with-highlight/
 

-kimmo
-Original Message-
From: Devel [mailto:devel-boun...@lists.sailfishos.org] On Behalf Of decon
Sent: 4. maaliskuuta 2017 18:09
To: devel
Subject: [SailfishDevel] Custom in-app icons

Hi,

Does anyone know how to use custom icons (monocrome) with Silica theme 
highlighting?

If I do as described at https://sailfishos.org/develop/docs/jolla-ambient/ it 
works with Silica icons, but I have not managed to do it with custom icons. The 
following code displays the icon, but highlighting does not work when clicking 
on the icon.

IconButton {
icon.source: "qrc:/icons/z1.00/icon-m-case-sensitive.png?" + (pressed ?

 Theme.highlightColor :

 Theme.primaryColor)
onClicked: { console.log("Clicked icon") } }

There were no error messages in the log either.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Custom in-app icons

[Andrey Kozhevnikov]

Or just use such shader: 
https://github.com/CODeRUS/harbour-screentapshot/blob/master/qml/overlay.qml#L171


-- Исходное сообщение --
От: "Kimmo Lindholm" 
Кому: "cod...@userspace.se" ; "Sailfish OS 
Developers" 

Отправлено: 04.03.2017 19:12:02
Тема: Re: [SailfishDevel] Custom in-app icons


Hi,

You need to make your own iconprovider. Explained here 
https://together.jolla.com/question/44325/iconbutton-how-to-use-own-icons-with-highlight/


-kimmo
-Original Message-
From: Devel [mailto:devel-boun...@lists.sailfishos.org] On Behalf Of 
decon

Sent: 4. maaliskuuta 2017 18:09
To: devel
Subject: [SailfishDevel] Custom in-app icons

Hi,

Does anyone know how to use custom icons (monocrome) with Silica theme 
highlighting?


If I do as described at 
https://sailfishos.org/develop/docs/jolla-ambient/ it works with Silica 
icons, but I have not managed to do it with custom icons. The following 
code displays the icon, but highlighting does not work when clicking on 
the icon.


IconButton {
icon.source: "qrc:/icons/z1.00/icon-m-case-sensitive.png?" + 
(pressed ?

 Theme.highlightColor :

 Theme.primaryColor)

onClicked: { console.log("Clicked icon") } }

There were no error messages in the log either.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Custom in-app icons

[decon]

Thank you both for your answers! I tried Kimmo's IconProvider and it worked 
perfectly.

Regards,
Decon

On Sat, 04 Mar 2017 16:18:08 +, "Andrey Kozhevnikov" 
 wrote:

> Or just use such shader: 
> https://github.com/CODeRUS/harbour-screentapshot/blob/master/qml/overlay.qml#L171
> 
> -- Исходное сообщение --
> От: "Kimmo Lindholm" 
> Кому: "cod...@userspace.se" ; "Sailfish OS 
> Developers" 
> Отправлено: 04.03.2017 19:12:02
> Тема: Re: [SailfishDevel] Custom in-app icons
> 
> >Hi,
> >
> >You need to make your own iconprovider. Explained here 
> >https://together.jolla.com/question/44325/iconbutton-how-to-use-own-icons-with-highlight/
> >
> >-kimmo
> >-Original Message-
> >From: Devel [mailto:devel-boun...@lists.sailfishos.org] On Behalf Of 
> >decon
> >Sent: 4. maaliskuuta 2017 18:09
> >To: devel
> >Subject: [SailfishDevel] Custom in-app icons
> >
> >Hi,
> >
> >Does anyone know how to use custom icons (monocrome) with Silica theme 
> >highlighting?
> >
> >If I do as described at 
> >https://sailfishos.org/develop/docs/jolla-ambient/ it works with Silica 
> >icons, but I have not managed to do it with custom icons. The following 
> >code displays the icon, but highlighting does not work when clicking on 
> >the icon.
> >
> >IconButton {
> > icon.source: "qrc:/icons/z1.00/icon-m-case-sensitive.png?" + 
> >(pressed ?
> > 
> >  Theme.highlightColor :
> > 
> >  Theme.primaryColor)
> > onClicked: { console.log("Clicked icon") } }
> >
> >There were no error messages in the log either.
> >___
> >SailfishOS.org Devel mailing list
> >To unsubscribe, please send a mail to 
> >devel-unsubscr...@lists.sailfishos.org
> >___
> >SailfishOS.org Devel mailing list
> >To unsubscribe, please send a mail to 
> >devel-unsubscr...@lists.sailfishos.org


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org