Re: [SailfishDevel] [Official Announcement] Join the Sailfish Community Device Program now!
Thank you Kimmo, somehow I slipped that sentence :-P Maybe it's my allergy to everything non SFOS :D On Thu, May 26, 2016 at 1:01 PM, Kimmo Lindholm wrote: > https://jolla.com/jollac > > > > “Pure Sailfish OS 2.0 compatible with Android™ apps” > > > > > > > > *Lähettäjä:* devel-boun...@lists.sailfishos.org [mailto: > devel-boun...@lists.sailfishos.org] *Puolesta *Luca Donaggio > *Lähetetty:* 26. toukokuuta 2016 13:59 > *Vastaanottaja:* Sailfish OS Developers > *Aihe:* Re: [SailfishDevel] [Official Announcement] Join the Sailfish > Community Device Program now! > > > > Will this new Jolla C have Android support included? Even if I can rely > 90% on Sailfosh OS only, there are still a few things I need Android for > (mainly a bank app). I can't afford a new, developer-only device: to > justify the expense I need it to become my main, everyday phone too. > > Can you please clarify this point? > > > > On Thu, May 26, 2016 at 11:59 AM, Jolla Community > wrote: > > Dear Jolla community member, > > As a thank you for your loyalty, we've just announced a new program for > *you*, the Jolla community! By joining the Sailfish Community Device > Program, you will get access to special content and R&D sessions, event > invitations, and the new Sailfish OS smartphone, the limited community > edition *Jolla C*. > > Join the program now here > <http://shop.jolla.com/eu_en/sailfish-community/sfos-community-developer-programme-offering.html> > . > > Read more about the Program in the latest Jolla blog post! > <https://blog.jolla.com/sailfish-community-device-program/> > > On behalf of the whole Jolla team, > James Noori > Community Manager > > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > > > > > -- > > Luca Donaggio > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] [Official Announcement] Join the Sailfish Community Device Program now!
Will this new Jolla C have Android support included? Even if I can rely 90% on Sailfosh OS only, there are still a few things I need Android for (mainly a bank app). I can't afford a new, developer-only device: to justify the expense I need it to become my main, everyday phone too. Can you please clarify this point? On Thu, May 26, 2016 at 11:59 AM, Jolla Community wrote: > Dear Jolla community member, > > As a thank you for your loyalty, we've just announced a new program for > *you*, the Jolla community! By joining the Sailfish Community Device > Program, you will get access to special content and R&D sessions, event > invitations, and the new Sailfish OS smartphone, the limited community > edition *Jolla C*. > > Join the program now here > <http://shop.jolla.com/eu_en/sailfish-community/sfos-community-developer-programme-offering.html> > . > > Read more about the Program in the latest Jolla blog post! > <https://blog.jolla.com/sailfish-community-device-program/> > > On behalf of the whole Jolla team, > James Noori > Community Manager > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Maps and Goodbye (for now)
I'm aware of that one, but it's still unfinished and looks like its author is not developing it anymore (last commit is from 11 months ago). On Tue, Jan 5, 2016 at 2:14 PM, Coley wrote: > A port for Sailfish already exists > https://github.com/skorjevec/stel-sf/releases/ > > -Coley. > > On 5 January 2016 at 12:54, Luca Donaggio wrote: > >> Yes, please, porting Stellarium will be so sweet ;-) ! >> >> On Tue, Jan 5, 2016 at 1:19 PM, David van rijn >> wrote: >> >>> Wow, Thank you so much guys, It does make me feel good, but also >>> slightly endebted (which would be a good motivation for working more and >>> harder). >>> >>> As for other projects, i am also working on the Transmission-Remote app, >>> which i started because i needed it, (but before i released it, tremotefs >>> was released, so not incentive to continue). >>> And there is my plan of makeing a flipcover keyboard, and if there are >>> people willing to help make this more mass-producable, this could also be >>> for everyone. I have not yet put stuff online for this, but i will soon. >>> >>> And i was just starting to make a soundcloud client. But that came as >>> far as making "soundcloud.cpp" before my phone broke. >>> >>> I am also still thinking of porting/cloning stellarium to get the whole >>> opensource skymaps going. (And practice for my orbital mechanics at the >>> same time :) >>> >>> I mostly start pjojects because i need them and they are not out there >>> yet, but i try to look for other apps i like and make pull requests. I >>> added 9292ov support for fahrplan (someone improved it later). >>> >>> If you have good suggestions for new apps or old ones that need work, >>> i'd be happy to hear it. >>> >>> >>> Love, >>> >>> David >>> >>> >>> 2016-01-03 15:18 GMT+01:00 Chris Walker < >>> cdw_noki...@the-walker-household.co.uk>: >>> >>>> On Sun, 03 Jan 2016 12:52:57 + >>>> Mike Gabriel wrote: >>>> >>>> > Hi David, >>>> > >>>> > On Mi 23 Dez 2015 16:51:04 CET, David van rijn wrote: >>>> > >>>> > > Hello, >>>> > > >>>> > > Sadly, i broke my phone, and i don't have money for a new one. So i >>>> > > will not be developing for a while. This does make me sad, but I >>>> [snip] >>>> > > David >>>> > >>>> > Do I get you right that your only blocker for continuing with >>>> > development for SailfishOS is not having a phone at hand anymore? >>>> > >>>> > If that is so, please get in touch with Jolla and order a new phone. >>>> > I will sponsor that. >>>> >>>> There are more important things than money in my life so I'll chip in >>>> some euros too. >>>> >>>> > Please also send me a list of Jolla projects you have been working >>>> > on in the past and let me know what your plans for other >>>> > Jolla-related development projects are. >>>> > >>>> > light+love >>>> > Mike (Debian Developer and Jolla fan) >>>> >>>> ___ >>>> 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 >>> >> >> >> >> -- >> Luca Donaggio >> >> ___ >> 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 > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Maps and Goodbye (for now)
Yes, please, porting Stellarium will be so sweet ;-) ! On Tue, Jan 5, 2016 at 1:19 PM, David van rijn wrote: > Wow, Thank you so much guys, It does make me feel good, but also slightly > endebted (which would be a good motivation for working more and harder). > > As for other projects, i am also working on the Transmission-Remote app, > which i started because i needed it, (but before i released it, tremotefs > was released, so not incentive to continue). > And there is my plan of makeing a flipcover keyboard, and if there are > people willing to help make this more mass-producable, this could also be > for everyone. I have not yet put stuff online for this, but i will soon. > > And i was just starting to make a soundcloud client. But that came as far > as making "soundcloud.cpp" before my phone broke. > > I am also still thinking of porting/cloning stellarium to get the whole > opensource skymaps going. (And practice for my orbital mechanics at the > same time :) > > I mostly start pjojects because i need them and they are not out there > yet, but i try to look for other apps i like and make pull requests. I > added 9292ov support for fahrplan (someone improved it later). > > If you have good suggestions for new apps or old ones that need work, i'd > be happy to hear it. > > > Love, > > David > > > 2016-01-03 15:18 GMT+01:00 Chris Walker < > cdw_noki...@the-walker-household.co.uk>: > >> On Sun, 03 Jan 2016 12:52:57 + >> Mike Gabriel wrote: >> >> > Hi David, >> > >> > On Mi 23 Dez 2015 16:51:04 CET, David van rijn wrote: >> > >> > > Hello, >> > > >> > > Sadly, i broke my phone, and i don't have money for a new one. So i >> > > will not be developing for a while. This does make me sad, but I >> [snip] >> > > David >> > >> > Do I get you right that your only blocker for continuing with >> > development for SailfishOS is not having a phone at hand anymore? >> > >> > If that is so, please get in touch with Jolla and order a new phone. >> > I will sponsor that. >> >> There are more important things than money in my life so I'll chip in >> some euros too. >> >> > Please also send me a list of Jolla projects you have been working >> > on in the past and let me know what your plans for other >> > Jolla-related development projects are. >> > >> > light+love >> > Mike (Debian Developer and Jolla fan) >> >> ___ >> 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 > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Happy holidays from Jolla Harbour!
Thanks a lot guys and Merry Christmas to all the Sailors! On Wed, Dec 23, 2015 at 1:52 PM, wrote: > Merry Christmas/happy holidays to all of you! And thanks for your hard > work! > > -- > Lähetetty Jollastani > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] SailfishOS SDK 1510 and launcher icon for tablet version
Thanks Andrey! On Tue, Oct 20, 2015 at 12:31 PM, Andrey Kozhevnikov wrote: > icon128.files = icon128/appname.png > icon128.path = /usr/share/icons/hicolor/128x128/apps > INSTALLS += icon128 > > and add /usr/share/icons/hicolor/128x128/apps to files section in yaml/spec > > -- Исходное сообщение -- > От: "Luca Donaggio" > Кому: "Sailfish OS Developers" > Отправлено: 20.10.2015 14:53:55 > Тема: [SailfishDevel] SailfishOS SDK 1510 and launcher icon for tablet > version > > > Launcher icon for the tablet version of any app should by 128x128 px and > have to be deployed in /usr/share/icons/hicolor/128x128/apps/appname.png, > but sailfishapp.prf and the auto-generated appname.yaml seems to take care > only of launcher icon for the phone version (86x86 px). > > Which is the best way to include a 128x128 px launcher icon in my projects? > > Are there any plans to automate this process in a future SDK release? > > -- > Luca Donaggio > > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] SailfishOS SDK 1510 and launcher icon for tablet version
Launcher icon for the tablet version of any app should by 128x128 px and have to be deployed in /usr/share/icons/hicolor/128x128/apps/appname.png, but sailfishapp.prf and the auto-generated appname.yaml seems to take care only of launcher icon for the phone version (86x86 px). Which is the best way to include a 128x128 px launcher icon in my projects? Are there any plans to automate this process in a future SDK release? -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Introducing the Jolla Tablet Developer Device loan program (Pilot)
On Fri, May 29, 2015 at 10:44 AM, Luciano Montanaro wrote: > As for the timing, Well, yes, I suppose tablet specific programs will > start coming out in earnest next fall. > But if as I think most devepers are programming their apps as a hobby > or a side work, I doubt this will slow them down much. I expect to be > able to work on my application a bit more (or rather, a bit! I have > not been very active I am afraid). > > What I find a bit puzzling is the availability of the SDK -- What is > the reason to restrict it so much? I understand it is not to be used > for programs to release for the current Sailfish/phone, but letting > people try out their programs in an emulator could mean a few more > applications running correctly on day T-day one. Just labelling the > SDK as beta and warning that things are subject to change should be > enough to keep things under control. > > What am I mising? > > Cheers, > Luciano > I second Luciano's opinion about the SDK: everybody who has an app published in harbour should have access to the new SDK *before* the tablets are available! This way even those among us who don't want to purchase one (I don't have the budget nor any real use for it right now) can test their app and make adjustments to support a different form factor / more screen real estate / etc. -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Update on SailfishOS roadmap
Great guys! I really appreciate this! On Mon, May 11, 2015 at 2:25 PM, Soumya Bijjal < soumya.bij...@jollamobile.com> wrote: > Hello all, > > It's been a while since the last update from us. The development of the > new UI framework and adaptation work for the Tablet have been our priority > for some time and will continue to be until we are ready with the sales > release for the Tablet. > > Alongside this important activity, we are preparing for the next software > upgrade, version 1.1.6 for your Jolla phone. Here are the highlights on > what to expect: > - Private browsing mode in Browser > - View detailed disk usage information under Settings > System > About > Product, by tapping on the memory info > - Option to search in Mail app > - Notification for voicemail (subject to your operator providing push > notifications) > - View phone number of your contact in the call log by invoking the > context sensitive menu (via press and hold action) on the call log entry > - Display a notification if an email attachment cannot be opened > - Import .ical and .vcs entries from the transfer list to the > Calendar app > - Option to send read receipt to the recipient when you have opened > the MMS received > > As you may have noticed, we've recently put up the development roadmap at > sailfishos.org (accessed as a link from the highlevel roadmap page): > https://sailfishos.org/developmentroadmap/ > > It has now been updated after our iteration planning day on last Tuesday. > We will continue update the page after every planning day to reflect the > advancements. > > Each item in the roadmap view signifies when the task is expected _to be > started_. In addition, we will provide more meta-data to each task to > indicate when it is implemented (read merged into our master code base) > followed by which software version it was released in. We chose this method > over displaying when an item is expected to be delivered as more often than > not, tasks span through multiple weeks, sometimes put on hold due to one > matter or another. We trust that a combination of whats started, > implemented and released gives you a better picture of our development > efforts. > > - bijjal > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Unknown Component
and it's still there after the new SDK update! C'mon guys, it shouldn't be so hard ... ;-) -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Unknown Component
Yeah, Coderus did an amazing job with the missing qmltypes, but question from Chris is still valid: since it's an annoyance (I'm not daring to call it a bug :) ) which has always been there since the begininnig and a solution has already been provided (by Coderus) it shouldn't be so hard to fix it! Maybe it will come with the next SDK release (the one with update11 targets) ? On Sat, Feb 21, 2015 at 3:21 PM, Michael Neufing wrote: > Installation of missing QML types should resolve the problem. > Coderus provided them on GitHub: https://github.com/CODeRUS/ > better-sailfishos-qmltypes > > Additionally it also provides code completion for other missing types like > the Theme-type. > > Installation instructions are available in the readme. > > > > Zitat von Chris Walker : > > > If I run the 'Run checks' command from the Tools->QML/JS option in >> Creator, I get the error message 'error: Unknown component. (M300). >> >> This is for the error against CoverActionList in Cover Page and >> similarly for CoverAction. >> >> While I realise that this isn't a huge problem, it can be >> distracting when scanning code for errors. This has been there since the >> year dot. Any chance of fixing it? >> ___ >> 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 > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Different behaviour of ShaderEffectSource in emulator vs. device
Wow! Documentation for Qt 5.4 has massively improved! Never thought about
looking at the 5.4 branch for docs though, as I'm developing for SailfishOS
exclusively and it's still 5.2 based; but from now on I will for sure, it's
sooo much better, thank you for pointing this out!
On Wed, Feb 11, 2015 at 8:07 PM, Gunnar Sletta
wrote:
>
> On 11 Feb 2015, at 10:46, Luca Donaggio wrote:
>
> Thank you Gunnar!
>
> I completely misunderstood the "layer" property of the Item element! I
> thought its purpouse was to apply an effect (or a texture) to an Item
> before rendering it on the scene, not to render any Item as an out-of-scene
> texture which could then be used as the source for a ShaderEffect!
>
>
> A convenient way of adding an effect is one usecase certainly. You can
> use it for other things though. The Qt 5.4 docs should have a fairly good
> explanation of how it works.
> http://doc-snapshot.qt-project.org/qt5-5.4/qml-qtquick-item.html#item-layers
>
> I thought that's what ShaderEffectSource does!
>
>
> layer is a more convenient ShaderEffectSource which doesn’t require you
> to add items into the sibling hierarchy.
>
>
> In my defense I must say that Qt documentation is not very clear, nor
> there are many examples available :-)
>
>
> In pre Qt 5.4, yes. Very much so :) If you find the 5.4 docs lacking,
> please let me know.
>
>
> Just out of curiosity then: why do you think my first code example works
> in the Emulator?
>
>
> Using the FBO as a source texture while writing to it is supported on
> many graphics cards.
>
>
>
> On Tue, Feb 10, 2015 at 9:04 PM, Gunnar Sletta
> wrote:
>
>> Hi Luca,
>>
>> The application code is not doing the right thing :)
>>
>> If the ShaderEffectSource depends on itself, it needs to have the
>> “recursive” property set to true, and that is still probably not what you
>> want. What you probably want is to set “layer.enabled: true; layer.smooth:
>> true” on the gradientSource and then use it directly in the ShaderEffect.
>> That should do what you want and comes without consequence.
>>
>> cheers,
>> Gunnar
>>
>>
>> On 10 Feb 2015, at 11:54, Luca Donaggio wrote:
>>
>> Thanks Andrey.
>>
>> I'll report this on TJC as well, trying to get more visibility. I hope
>> that some Sailor will notice it: it's not that important, but it's
>> disturbing nonetheless.
>>
>>
>> On Tue, Feb 10, 2015 at 11:39 AM, Andrey Kozhevnikov <
>> coderusin...@gmail.com> wrote:
>>
>>> yes i can confirm this behaviour.
>>>
>>> 10.02.2015 15:24, Luca Donaggio пишет:
>>>
>>> Hi Andrey, thanks for your reply.
>>>
>>> Still, can you try both tests on your Jolla?
>>> The first shouldn't work, while the second does.
>>>
>>> On Tue, Feb 10, 2015 at 10:32 AM, Andrey Kozhevnikov <
>>> coderusin...@gmail.com> wrote:
>>>
>>>> sorry, not using emulator at all.
>>>>
>>>> 10.02.2015 14:28, Luca Donaggio пишет:
>>>>
>>>> Anybody is willing to try my test code and confirm or deny my finding?
>>>>
>>>> On Fri, Feb 6, 2015 at 2:12 PM, Luca Donaggio
>>>> wrote:
>>>>
>>>>> The following code works fine in Emulator, changing the gradient of
>>>>> the Rectangle correctly updates the nested ShaderEffectSource and it is
>>>>> reflected on the ShaderEffect which uses it as its texture:
>>>>>
>>>>> Page {
>>>>> id: page
>>>>>
>>>>> SilicaFlickable {
>>>>> anchors.fill: parent
>>>>>
>>>>> contentHeight: column.height
>>>>>
>>>>> Column {
>>>>> id: column
>>>>>
>>>>> anchors { top: parent.top; left: parent.left; right:
>>>>> parent.right; leftMargin: Theme.paddingLarge; rightMargin:
>>>>> Theme.paddingLarge; }
>>>>> spacing: Theme.paddingLarge
>>>>>
>>>>> PageHeader {
>>>>> title: qsTr("ShaderEffect Test")
>>>>> }
>>>>>
>>>>> Row {
>>>>> anchors.horizontalCenter: parent.horizontalCenter
>>>>> spacing: Theme.paddingLarge
>>>>>
>>>>> Column {
>>&
Re: [SailfishDevel] Different behaviour of ShaderEffectSource in emulator vs. device
Thank you Gunnar!
I completely misunderstood the "layer" property of the Item element! I
thought its purpouse was to apply an effect (or a texture) to an Item
before rendering it on the scene, not to render any Item as an out-of-scene
texture which could then be used as the source for a ShaderEffect! I
thought that's what ShaderEffectSource does!
In my defense I must say that Qt documentation is not very clear, nor there
are many examples available :-)
Just out of curiosity then: why do you think my first code example works in
the Emulator?
On Tue, Feb 10, 2015 at 9:04 PM, Gunnar Sletta
wrote:
> Hi Luca,
>
> The application code is not doing the right thing :)
>
> If the ShaderEffectSource depends on itself, it needs to have the
> “recursive” property set to true, and that is still probably not what you
> want. What you probably want is to set “layer.enabled: true; layer.smooth:
> true” on the gradientSource and then use it directly in the ShaderEffect.
> That should do what you want and comes without consequence.
>
> cheers,
> Gunnar
>
>
> On 10 Feb 2015, at 11:54, Luca Donaggio wrote:
>
> Thanks Andrey.
>
> I'll report this on TJC as well, trying to get more visibility. I hope
> that some Sailor will notice it: it's not that important, but it's
> disturbing nonetheless.
>
>
> On Tue, Feb 10, 2015 at 11:39 AM, Andrey Kozhevnikov <
> coderusin...@gmail.com> wrote:
>
>> yes i can confirm this behaviour.
>>
>> 10.02.2015 15:24, Luca Donaggio пишет:
>>
>> Hi Andrey, thanks for your reply.
>>
>> Still, can you try both tests on your Jolla?
>> The first shouldn't work, while the second does.
>>
>> On Tue, Feb 10, 2015 at 10:32 AM, Andrey Kozhevnikov <
>> coderusin...@gmail.com> wrote:
>>
>>> sorry, not using emulator at all.
>>>
>>> 10.02.2015 14:28, Luca Donaggio пишет:
>>>
>>> Anybody is willing to try my test code and confirm or deny my finding?
>>>
>>> On Fri, Feb 6, 2015 at 2:12 PM, Luca Donaggio
>>> wrote:
>>>
>>>> The following code works fine in Emulator, changing the gradient of the
>>>> Rectangle correctly updates the nested ShaderEffectSource and it is
>>>> reflected on the ShaderEffect which uses it as its texture:
>>>>
>>>> Page {
>>>> id: page
>>>>
>>>> SilicaFlickable {
>>>> anchors.fill: parent
>>>>
>>>> contentHeight: column.height
>>>>
>>>> Column {
>>>> id: column
>>>>
>>>> anchors { top: parent.top; left: parent.left; right:
>>>> parent.right; leftMargin: Theme.paddingLarge; rightMargin:
>>>> Theme.paddingLarge; }
>>>> spacing: Theme.paddingLarge
>>>>
>>>> PageHeader {
>>>> title: qsTr("ShaderEffect Test")
>>>> }
>>>>
>>>> Row {
>>>> anchors.horizontalCenter: parent.horizontalCenter
>>>> spacing: Theme.paddingLarge
>>>>
>>>> Column {
>>>> spacing: Theme.paddingSmall
>>>>
>>>> Rectangle {
>>>> id: gradientSource
>>>>
>>>> property list gradients: [
>>>> Gradient {
>>>> GradientStop { position: 0.0; color:
>>>> "black"; }
>>>> GradientStop { position: 1.0; color:
>>>> "blue"; }
>>>> },
>>>>
>>>> Gradient {
>>>> GradientStop { position: 0.0; color:
>>>> "black"; }
>>>> GradientStop { position: 1.0; color:
>>>> "red"; }
>>>> }
>>>> ]
>>>>
>>>> width: 100
>>>> height: 100
>>>>
>>>> gradient: gradients[0]
>>>>
>>>> ShaderEffectSource {
>>>> id: gradientTexture
>>>>
>>>>
Re: [SailfishDevel] Different behaviour of ShaderEffectSource in emulator vs. device
Thanks Andrey.
I'll report this on TJC as well, trying to get more visibility. I hope that
some Sailor will notice it: it's not that important, but it's disturbing
nonetheless.
On Tue, Feb 10, 2015 at 11:39 AM, Andrey Kozhevnikov wrote:
> yes i can confirm this behaviour.
>
> 10.02.2015 15:24, Luca Donaggio пишет:
>
> Hi Andrey, thanks for your reply.
>
> Still, can you try both tests on your Jolla?
> The first shouldn't work, while the second does.
>
> On Tue, Feb 10, 2015 at 10:32 AM, Andrey Kozhevnikov <
> coderusin...@gmail.com> wrote:
>
>> sorry, not using emulator at all.
>>
>> 10.02.2015 14:28, Luca Donaggio пишет:
>>
>> Anybody is willing to try my test code and confirm or deny my finding?
>>
>> On Fri, Feb 6, 2015 at 2:12 PM, Luca Donaggio wrote:
>>
>>> The following code works fine in Emulator, changing the gradient of the
>>> Rectangle correctly updates the nested ShaderEffectSource and it is
>>> reflected on the ShaderEffect which uses it as its texture:
>>>
>>> Page {
>>> id: page
>>>
>>> SilicaFlickable {
>>> anchors.fill: parent
>>>
>>> contentHeight: column.height
>>>
>>> Column {
>>> id: column
>>>
>>> anchors { top: parent.top; left: parent.left; right:
>>> parent.right; leftMargin: Theme.paddingLarge; rightMargin:
>>> Theme.paddingLarge; }
>>> spacing: Theme.paddingLarge
>>>
>>> PageHeader {
>>> title: qsTr("ShaderEffect Test")
>>> }
>>>
>>> Row {
>>> anchors.horizontalCenter: parent.horizontalCenter
>>> spacing: Theme.paddingLarge
>>>
>>> Column {
>>> spacing: Theme.paddingSmall
>>>
>>> Rectangle {
>>> id: gradientSource
>>>
>>> property list gradients: [
>>> Gradient {
>>> GradientStop { position: 0.0; color:
>>> "black"; }
>>> GradientStop { position: 1.0; color:
>>> "blue"; }
>>> },
>>>
>>> Gradient {
>>> GradientStop { position: 0.0; color:
>>> "black"; }
>>> GradientStop { position: 1.0; color:
>>> "red"; }
>>> }
>>> ]
>>>
>>> width: 100
>>> height: 100
>>>
>>> gradient: gradients[0]
>>>
>>> ShaderEffectSource {
>>> id: gradientTexture
>>>
>>> anchors.fill: parent
>>> sourceItem: gradientSource
>>> hideSource: false
>>> live: true
>>> }
>>> }
>>>
>>> Label {
>>> font.pixelSize: Theme.fontSizeExtraSmall
>>> wrapMode: Text.WordWrap
>>> text: "Rectangle\nShaderEffectSource"
>>> }
>>> }
>>>
>>> Column {
>>> spacing: Theme.paddingSmall
>>>
>>> ShaderEffect {
>>> property variant source: gradientTexture
>>>
>>> width: 100
>>> height: 100
>>>
>>> blending: false
>>> cullMode: ShaderEffect.BackFaceCulling
>>> fragmentShader: "
>>> varying highp vec2 qt_TexCoord0;
>>> uniform lowp float qt_Opacity;
>>> uniform sampler2D source;
>>>
>>> void main() {
>>> gl_FragColor = texture2D(source,
>>> qt_TexCoord0) * qt_Opacity;
>>>
Re: [SailfishDevel] Different behaviour of ShaderEffectSource in emulator vs. device
Hi Andrey, thanks for your reply.
Still, can you try both tests on your Jolla?
The first shouldn't work, while the second does.
On Tue, Feb 10, 2015 at 10:32 AM, Andrey Kozhevnikov wrote:
> sorry, not using emulator at all.
>
> 10.02.2015 14:28, Luca Donaggio пишет:
>
> Anybody is willing to try my test code and confirm or deny my finding?
>
> On Fri, Feb 6, 2015 at 2:12 PM, Luca Donaggio wrote:
>
>> The following code works fine in Emulator, changing the gradient of the
>> Rectangle correctly updates the nested ShaderEffectSource and it is
>> reflected on the ShaderEffect which uses it as its texture:
>>
>> Page {
>> id: page
>>
>> SilicaFlickable {
>> anchors.fill: parent
>>
>> contentHeight: column.height
>>
>> Column {
>> id: column
>>
>> anchors { top: parent.top; left: parent.left; right:
>> parent.right; leftMargin: Theme.paddingLarge; rightMargin:
>> Theme.paddingLarge; }
>> spacing: Theme.paddingLarge
>>
>> PageHeader {
>> title: qsTr("ShaderEffect Test")
>> }
>>
>> Row {
>> anchors.horizontalCenter: parent.horizontalCenter
>> spacing: Theme.paddingLarge
>>
>> Column {
>> spacing: Theme.paddingSmall
>>
>> Rectangle {
>> id: gradientSource
>>
>> property list gradients: [
>> Gradient {
>> GradientStop { position: 0.0; color:
>> "black"; }
>> GradientStop { position: 1.0; color:
>> "blue"; }
>> },
>>
>> Gradient {
>> GradientStop { position: 0.0; color:
>> "black"; }
>> GradientStop { position: 1.0; color:
>> "red"; }
>> }
>> ]
>>
>> width: 100
>> height: 100
>>
>> gradient: gradients[0]
>>
>> ShaderEffectSource {
>> id: gradientTexture
>>
>> anchors.fill: parent
>> sourceItem: gradientSource
>> hideSource: false
>> live: true
>> }
>> }
>>
>> Label {
>> font.pixelSize: Theme.fontSizeExtraSmall
>> wrapMode: Text.WordWrap
>> text: "Rectangle\nShaderEffectSource"
>> }
>> }
>>
>> Column {
>> spacing: Theme.paddingSmall
>>
>> ShaderEffect {
>> property variant source: gradientTexture
>>
>> width: 100
>> height: 100
>>
>> blending: false
>> cullMode: ShaderEffect.BackFaceCulling
>> fragmentShader: "
>> varying highp vec2 qt_TexCoord0;
>> uniform lowp float qt_Opacity;
>> uniform sampler2D source;
>>
>> void main() {
>> gl_FragColor = texture2D(source,
>> qt_TexCoord0) * qt_Opacity;
>> }"
>> }
>>
>> Label {
>> font.pixelSize: Theme.fontSizeExtraSmall
>> text: "ShaderEffect"
>> }
>> }
>> }
>>
>> Button {
>> anchors.horizontalCenter: parent.horizontalCenter
>> text: "Blue gradient"
>>
>> onClicked: gradientSource.gradient =
>> gradientSource.gradients[0]
>> }
>>
>> Button {
>> anchors.horizontalCenter: parent.horizontalCenter
>> text: "Red gradient"
>>
>>
Re: [SailfishDevel] Different behaviour of ShaderEffectSource in emulator vs. device
Anybody is willing to try my test code and confirm or deny my finding?
On Fri, Feb 6, 2015 at 2:12 PM, Luca Donaggio wrote:
> The following code works fine in Emulator, changing the gradient of the
> Rectangle correctly updates the nested ShaderEffectSource and it is
> reflected on the ShaderEffect which uses it as its texture:
>
> Page {
> id: page
>
> SilicaFlickable {
> anchors.fill: parent
>
> contentHeight: column.height
>
> Column {
> id: column
>
> anchors { top: parent.top; left: parent.left; right:
> parent.right; leftMargin: Theme.paddingLarge; rightMargin:
> Theme.paddingLarge; }
> spacing: Theme.paddingLarge
>
> PageHeader {
> title: qsTr("ShaderEffect Test")
> }
>
> Row {
> anchors.horizontalCenter: parent.horizontalCenter
> spacing: Theme.paddingLarge
>
> Column {
> spacing: Theme.paddingSmall
>
> Rectangle {
> id: gradientSource
>
> property list gradients: [
> Gradient {
> GradientStop { position: 0.0; color:
> "black"; }
> GradientStop { position: 1.0; color:
> "blue"; }
> },
>
> Gradient {
> GradientStop { position: 0.0; color:
> "black"; }
> GradientStop { position: 1.0; color:
> "red"; }
> }
> ]
>
> width: 100
> height: 100
>
> gradient: gradients[0]
>
> ShaderEffectSource {
> id: gradientTexture
>
> anchors.fill: parent
> sourceItem: gradientSource
> hideSource: false
> live: true
> }
> }
>
> Label {
> font.pixelSize: Theme.fontSizeExtraSmall
> wrapMode: Text.WordWrap
> text: "Rectangle\nShaderEffectSource"
> }
> }
>
> Column {
> spacing: Theme.paddingSmall
>
> ShaderEffect {
> property variant source: gradientTexture
>
> width: 100
> height: 100
>
> blending: false
> cullMode: ShaderEffect.BackFaceCulling
> fragmentShader: "
> varying highp vec2 qt_TexCoord0;
> uniform lowp float qt_Opacity;
> uniform sampler2D source;
>
> void main() {
> gl_FragColor = texture2D(source,
> qt_TexCoord0) * qt_Opacity;
> }"
> }
>
> Label {
> font.pixelSize: Theme.fontSizeExtraSmall
> text: "ShaderEffect"
> }
> }
> }
>
> Button {
> anchors.horizontalCenter: parent.horizontalCenter
> text: "Blue gradient"
>
> onClicked: gradientSource.gradient =
> gradientSource.gradients[0]
> }
>
> Button {
> anchors.horizontalCenter: parent.horizontalCenter
> text: "Red gradient"
>
> onClicked: gradientSource.gradient =
> gradientSource.gradients[1]
> }
> }
> }
> }
>
> It doesn't work on device though (changing Reactangle's gradient doesn't
> update the ShaderEffectSource).
>
> Un-nesting the ShaderEffectSource from its source item (the Rectangle)
> works fine both on emulator and on device:
>
> Page {
> id: page
>
> SilicaFlickable {
> anchors.fill: parent
>
> contentHeight: column.height
>
> Column {
> id: column
>
> anchors { top: parent.top; left: parent.left; right:
> parent.right; leftMargin: Theme.paddingLarge; rightMargin:
> Theme.paddingL
[SailfishDevel] Different behaviour of ShaderEffectSource in emulator vs. device
GradientStop { position: 0.0; color:
"black"; }
GradientStop { position: 1.0; color: "red";
}
}
]
width: 100
height: 100
gradient: gradients[0]
}
Label {
font.pixelSize: Theme.fontSizeExtraSmall
text: "Rectangle"
}
}
Column {
spacing: Theme.paddingSmall
ShaderEffectSource {
id: gradientTexture
width: 100
height: 100
sourceItem: gradientSource
hideSource: false
live: true
}
Label {
font.pixelSize: Theme.fontSizeExtraSmall
text: "ShaderEffectSource"
}
}
Column {
spacing: Theme.paddingSmall
ShaderEffect {
property variant source: gradientTexture
width: 100
height: 100
blending: false
cullMode: ShaderEffect.BackFaceCulling
fragmentShader: "
varying highp vec2 qt_TexCoord0;
uniform lowp float qt_Opacity;
uniform sampler2D source;
void main() {
gl_FragColor = texture2D(source,
qt_TexCoord0) * qt_Opacity;
}"
}
Label {
font.pixelSize: Theme.fontSizeExtraSmall
text: "ShaderEffect"
}
}
}
Button {
anchors.horizontalCenter: parent.horizontalCenter
text: "Blue gradient"
onClicked: gradientSource.gradient =
gradientSource.gradients[0]
}
Button {
anchors.horizontalCenter: parent.horizontalCenter
text: "Red gradient"
onClicked: gradientSource.gradient =
gradientSource.gradients[1]
}
}
}
}
Is it a bug?
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Sailfishos.org site renewal!
+1 On Sat, Jan 31, 2015 at 5:52 PM, Dan Arrhenius wrote: > +1 > > On 2015-01-31 16:08, Osmo Salomaa wrote: > > 31.01.2015, 15:26, Kimmo Lindholm kirjoitti: > >> As said below; > >> > >>> Currently the SDK includes Tutorial, Design and API Documentation, > >>> and these are not available on the website. > >> > >> Start SDK, click help on sidebar, last item from contents "Sailfish > >> silica reference" > > > > Thanks, but many of us dynamic-language folks don't use and don't want > > to use the SDK (much) at all. > > > > I hope documentation quickly returns to the website as well. > > > > I personally have a scrape of the old documentation (indexed for use > > with Emacs and helm-dash), so I'm fine, but others might not be fine. > > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Setting :: Applications and accounts
There's no documentation 'cause both are not officially supported YET - ie, you can use those features unofficilaly, but your app is not going to be accepted in Harbour. On Fri, Jan 9, 2015 at 4:16 AM, Nicolas Cisco wrote: > Hi, > i've seen that apps can be configure thought the settings app, but didn't > found any documentation about it, how that can be done?. > > The same question goes for the account section of Settings, custom apps > can be managed through that account configuration?. > > Best regards. > > -- > Nicolas Cisco > www.nckweb.com.ar > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] defining version number only once
This is the way I solved #1:
a) in your .yaml add the lines:
QMakeOptions:
- VERSION=%{version}
b) in your .pro add the lines:
# App version
DEFINES += APP_VERSION=\"\\\"$${VERSION}\\\"\"
c) in your .c's main() function add the lines:
QScopedPointer app(SailfishApp::application(argc,
argv));
app->setApplicationVersion(QString(APP_VERSION));
d) now your app's version is available in QML through
Qt.application.version
On Tue, Dec 23, 2014 at 5:44 PM, Alfonso Martone wrote:
> Sorry to ask here, but I wasn't able to get some official guidelines.
>
> 1) Version/Release numbers:
>
> - I have to place them both in the *.yaml *file (for RPM build) and in
> some *.h* or *.qml *source (to show it in some "about" dialog): is there
> a way to define the Version/Release numbers in a *single* file of the
> project, making them available to C++, QML and RPM-build ?
>
> 2) from time to time my software has to write some output file (collected
> data) that the user may use in another app:
>
> - is it correct to save in *$HOME/Documents* ?
>
> Thanks.
>
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to
> devel-unsubscr...@lists.sailfishos.org
>
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Tablet version SDK a.k.a 2.0
Yes, it will, but to populate the Store for the new tablet, every devel should upload the x86 version of their app's RPM Maybe a little incentive from Jolla in the form of a free-or-heavily-discounted-devel-only-edition's tablet could make it happen faster *hint* *hint* ;-D On Thu, Nov 20, 2014 at 11:27 AM, Luciano Montanaro wrote: > Yes, but the SDK already has an x86 target. The emulator is simply an > x86 virtual machine, so, if your app runs in the emulator, it will run > on the tablet. The resolution is wrong for the tablet, but other than > that, the app will run. > > On Thu, Nov 20, 2014 at 11:19 AM, Luca Donaggio > wrote: > > CPU architectures are different, too: tablet having a 64bit Intel SoC, > while > > phone uses a 32bit ARM. > > Currently every app in the Store is an ARM binary, so at least they all > need > > to be re-compiled for x86 and re-uploaded, as I doubt that the tablet > will > > sport an ARM compatibility layer. > > > > On Thu, Nov 20, 2014 at 10:09 AM, Luciano Montanaro > > wrote: > >> > >> Andrey is being ironic, I suppose, but it is a good guess. > >> > >> I don't think you need to care, though: > >> The SDK will probably be updated a couple of times before "Sailfish > >> 2.0", with interim updates... > >> I think that, as long as your app works on a phone, it will work on > >> the tablet. Maybe layout will not be optimal, but that can be fixed > >> later on. > >> > >> Luciano > >> > >> On Wed, Nov 19, 2014 at 9:53 PM, Fabio Isgrò < > fabio.is...@messinalug.org> > >> wrote: > >> > So 4th week of May 15 or 1week of Jun 15 ? > >> > > >> > On Wed, Nov 19, 2014 at 8:54 PM, Andrey Kozhevnikov > >> > > >> > wrote: > >> >> > >> >> a week after OS update released, as usual :D > >> >> > >> >> 20.11.2014 00:52, Alex Smirnoff пишет: > >> >> > >> >> Is that already known when new SDK will be available? > >> >> > >> >> Could not wait to port Gcompris to Jolla. > >> >> > >> >> > >> >> -- > >> >> Alex Smirnov > >> >> > >> >> > >> >> ___ > >> >> 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 > >> > >> > >> > >> -- > >> Luciano Montanaro > >> > >> Anyone who is capable of getting themselves made President should on > >> no account be allowed to do the job. -- Douglas Adams > >> ___ > >> SailfishOS.org Devel mailing list > >> To unsubscribe, please send a mail to > >> devel-unsubscr...@lists.sailfishos.org > > > > > > > > > > -- > > Luca Donaggio > > > > ___ > > SailfishOS.org Devel mailing list > > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > > > > -- > Luciano Montanaro > > Anyone who is capable of getting themselves made President should on > no account be allowed to do the job. -- Douglas Adams > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Tablet version SDK a.k.a 2.0
CPU architectures are different, too: tablet having a 64bit Intel SoC, while phone uses a 32bit ARM. Currently every app in the Store is an ARM binary, so at least they all need to be re-compiled for x86 and re-uploaded, as I doubt that the tablet will sport an ARM compatibility layer. On Thu, Nov 20, 2014 at 10:09 AM, Luciano Montanaro wrote: > Andrey is being ironic, I suppose, but it is a good guess. > > I don't think you need to care, though: > The SDK will probably be updated a couple of times before "Sailfish > 2.0", with interim updates... > I think that, as long as your app works on a phone, it will work on > the tablet. Maybe layout will not be optimal, but that can be fixed > later on. > > Luciano > > On Wed, Nov 19, 2014 at 9:53 PM, Fabio Isgrò > wrote: > > So 4th week of May 15 or 1week of Jun 15 ? > > > > On Wed, Nov 19, 2014 at 8:54 PM, Andrey Kozhevnikov < > coderusin...@gmail.com> > > wrote: > >> > >> a week after OS update released, as usual :D > >> > >> 20.11.2014 00:52, Alex Smirnoff пишет: > >> > >> Is that already known when new SDK will be available? > >> > >> Could not wait to port Gcompris to Jolla. > >> > >> > >> -- > >> Alex Smirnov > >> > >> > >> ___ > >> 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 > > > > -- > Luciano Montanaro > > Anyone who is capable of getting themselves made President should on > no account be allowed to do the job. -- Douglas Adams > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Update9 (1.1.0.38) and new Dialog Silica component
Thanks a lot Andrey, that did the trick! On Thu, Oct 23, 2014 at 11:55 AM, Andrey Kozhevnikov wrote: > You shouldn't put DialogHeader in column with margins, it should be in > Flickable top or ListView header and have parent.width > > 23.10.2014 15:47, Luca Donaggio пишет: > > As my two apps in Harbour both use a Dialog Silica component, I tried > both of them soon after upgrading to the new SFOS release. > > Both Dialogs presented a slightly different appearence and none of them > seems right to me (see attached screenshots): in one case the background of > the newly introduced dialog header is centered and in the other it is > anchored to the left, while I think that the right appearence would be to > horizontally fill the page. > Both Dialogs have the anchors.fill property set to "parent", what could > be the issue? > > -- > Luca Donaggio > > > ___ > 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 > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Okay to use Silica GlassItem?
GlassItem-using apps are not banned from Harbour AFAIK. At least mine has been accepted. On Sun, Oct 5, 2014 at 12:20 PM, Camil Bancioiu wrote: > I've read that the GlassItem QML component wasn't yet ready for usage, and > you > can't publish an application on Harbour if it uses GlassItem. Is that still > true? Or GlassItem is now allowed? > > If GlassItem is not yet supported in Harbour, is there another UI element > to > use for highlighting a ListItem? Apart from coloring its Labels with > Theme.highlightColor, of course. > > Best regards, > Camil > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Translating apps for SailfishOS
1. No, lupdate is included in the virtual machine used to bild your app and
invoked automatically
2. Just put your harbour-yourappname-xx.ts files into 'translations'
directory and you're set
3. Usually I install the RPM in the emulator and run it from command line
after changing LANG env variable
On Thu, Jul 17, 2014 at 10:37 AM, Marcin M. wrote:
> I couldn't find the answers to a couple of questions:
> 1. Does SailfishOS SDK require external lupdate? If yes, where can the
> command for lupdate be set (as of Mint 17 (Ubuntu 14.04), lupdate-qt5 is
> not provided by any package)
> 2. If using sailfishapp_i18n, are the QTranslator steps still needed?
> Should /usr/share/appname/i18n or .../appname/translations be used? If ` -
> '%{_datadir}/%{name}' ` is already in .yaml is anything else needed
> concerning packaging?
> 3. What's the recommended way of testing translations in the Emulator?
> setting LANG in the environmental variables?
>
> PS. There's no documentation concerning this on the sailfishos.org
> website.
> --
> Marcin
>
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to
> devel-unsubscr...@lists.sailfishos.org
>
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] XMLHttpRequest and timeouts
Hi all, I'm using an XMLHttpRequest object from a stateless javascript library to call some webservices. I understand that the implementation of this object provided by the Qt version currently used in SFOS lacks the "timeout" property (and, consequently, the "ontimeout" slot). As the web service I try to connect to is not always available, the result is that my app sometimes wait indefinitely for an answer from the remote server which is likely to never come. Is there any other way to detect (and react to) a network timeout in QML/javascript? -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] my letter on switching sides [non-technical]
Good luck! On Wed Jun 11 2014 20:25:50 GMT+0200 (CEST), Jarko Vihriala wrote: > > Hello there! > > This is my announcement to Sailfish developer community that I'm switching > sides. That's right, after next week I will be present in the community only > as private person with no direct connection to Jolla Oy. If you did not read > between the lines - I have resigned from my post as chief SDK Engineer in > Jolla and my last working day is tomorrow, 12.6.2014. > > I recently got a once-in-a-lifetime opportunity at somewhere else and just > could not resist to take it on, you'll find out about it soon enough. Making > the decision to leave Jolla was not easy. > > What now? Actually the SDK team has received new members and they are already > working on to get the next release out, so there should not be any stalling > of the engine. The harbour ranks stay intact also, so the biggest difference > is that you'll see someone else posting SDK announcement mails after this > week is over. Traditional support channels (#sailfishos irc, devel mailing > list and TJC) keep running just like before. > > I would like to thank you all in the community so far for such unforgettable > journey. We have shown the world together what it means to be part of this > tribe. Yes, there have been ups and downs but overall the atmosphere has been > and is great. > > So there, I hate long goodbyes (like I told my colleagues yesterday) so - > let's keep on rowing and keep those apps hitting the Jolla Store! > > with love, Jarko (jake9xx) > > -- Sent from my Jolla ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Detecting OS version
Thank you Joona! On Tue, Jun 10, 2014 at 4:42 PM, Joona Petrell wrote: > Hi Luca, > > We haven't yet started versioning Silica APIs (though we probably should > soon), sorry, but you can check if quickScroll property on your flickable > has been defined (myFlickable.quickScroll === undefined) to check if the > quick scroll functionality is available. > > Cheers, > > Joona > > -- > *From:* devel-boun...@lists.sailfishos.org [ > devel-boun...@lists.sailfishos.org] on behalf of Luca Donaggio [ > donag...@gmail.com] > *Sent:* 10 June 2014 17:30 > *To:* Sailfish OS Developers > *Subject:* [SailfishDevel] Detecting OS version > > Hi all, > > recent update (1.0.7.16) added fast scrolling to Silica flickable QML > components (like SilicaListView). > Before, for long lists I added a pull up menu with an option to > fast-scroll back to the top, others (Together app for example) used a > custom scroll decorator with the same functionality. > > Is there a way to detect at run-time (in QML would be perfect, but in C++ > would do the same) if the new functionality is available, or, > alternatively, which OS version we are in? > > This way I can avoid cluttering my app UI with elements which basically > duplicate the same functionality: > > if OS version >= 1.0.7.16 / system fast-scroll available: do nothing > else: enable custom fast-scroll > >-- > Luca Donaggio > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Detecting OS version
Thanks Jonni! On Tue, Jun 10, 2014 at 4:33 PM, Jonni Nakari wrote: > On 10.06.2014 17:30, Luca Donaggio wrote: > >> This way I can avoid cluttering my app UI with elements which basically >> duplicate the same functionality: >> > CODeRUS and veskuh recently added something like this to Tweetian, see: > > https://github.com/CODeRUS/Tweetian/commit/3d50e172455cf94f2dd8064f7078ff > 94fc430f9d > > -- > Jonni Nakari > jo...@egarden.fi > +358 50 4411 784 > > A: Because it disrupts the natural way of thinking. > Q: Why is top posting frowned upon? > > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscribe@lists. > sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Detecting OS version
Thanks Andrey, that's what I was looking for! On Tue, Jun 10, 2014 at 4:32 PM, Andrey Kozhevnikov wrote: > check > https://github.com/veskuh/Tweetian/commit/3d50e172455cf94f2dd8064f7078ff94fc430f9d > > > 10.06.2014 20:30, Luca Donaggio пишет: > >Hi all, > > recent update (1.0.7.16) added fast scrolling to Silica flickable QML > components (like SilicaListView). > Before, for long lists I added a pull up menu with an option to > fast-scroll back to the top, others (Together app for example) used a > custom scroll decorator with the same functionality. > > Is there a way to detect at run-time (in QML would be perfect, but in C++ > would do the same) if the new functionality is available, or, > alternatively, which OS version we are in? > > This way I can avoid cluttering my app UI with elements which basically > duplicate the same functionality: > > if OS version >= 1.0.7.16 / system fast-scroll available: do nothing > else: enable custom fast-scroll > >-- > Luca Donaggio > > > ___ > 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 > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] Detecting OS version
Hi all, recent update (1.0.7.16) added fast scrolling to Silica flickable QML components (like SilicaListView). Before, for long lists I added a pull up menu with an option to fast-scroll back to the top, others (Together app for example) used a custom scroll decorator with the same functionality. Is there a way to detect at run-time (in QML would be perfect, but in C++ would do the same) if the new functionality is available, or, alternatively, which OS version we are in? This way I can avoid cluttering my app UI with elements which basically duplicate the same functionality: if OS version >= 1.0.7.16 / system fast-scroll available: do nothing else: enable custom fast-scroll -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Acceptable Behaviour Guidelines - you decide
+1 On Wed, May 28, 2014 at 1:11 PM, Ville M. Vainio wrote: > It's not massive change to write up a guideline - the guideline does not > even need to address what *can* be discussed, but it can address what > *can't* be discussed, or what tone you need to maintain. > > It doesn't need a process or anything, just write it up and assume people > will adhere to it (and deal with uncompliance later on). Sometimes common > sense is a sufficient guideline, but, well, sometimes it isn't. > > > > > > On Tue, May 27, 2014 at 8:54 PM, wrote: > >> Hi Stefano >> >> Sorry If I distracted the line of argument with the forum vs. ML vs. TJC >> thing... >> >> To directly answer your / David's question: I have been in the ML since >> pretty early on, and I have never felt "oh I wish this list was moderated, >> get me out of here ...". Indeed I have welcomed the wide range of topics >> from intensely technical through to Jolla's take on Open Source. >> >> Equally I have never felt "he / she should be summarily booted off the M" >> (though I can't exclude the possibility that others may think that in my >> case ...). >> >> The past few days have been very different from the norm, and we should >> not make massive changes based on them alone. >> >> However it is possible that as this community increases, and becomes less >> of a small intimate family, then the need for moderation may grow. >> >> >> Chris >> >> >> >> Zitat von "Stefano Mosconi" : >> >> >> It seems that the original topic was a bit forgotten in favor of the >>> forum vs. ML vs. TJC (which is a good and intersting topic but no matter >>> what tool we use we will have to go back to the main question). >>> >>> Just to try to steer the boat back on the original journey this the >>> question that David was asking at the beginning: >>> >>> On 22/05/14 17:18, David Greaves wrote: >>> >>>> We need to be careful about over-policing discussions but there is such >>>> a thing >>>> as under-policing too. >>>> >>>> How would we (community, not Jolla) determine the line? and what >>>> measures do we >>>> think should be taken? >>>> >>>> Lorn pointed to this as a useful document: >>>>http://www.kde.org/code-of-conduct/ >>>> >>> >>> Stefano >>> ___ >>> 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 >> > > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] was "Acceptable Behaviour.." --> Forum
l about personal habits that one got used to. > > > > > > Right now, I am primarily using the Sailfish OS etc. sections at > > > talk.maemo.org as "semi-official" Sailfish OS/Jolla forum replacement. > > > So, in a sense, there is already something like a forum. > > > Maybe this is a viable approach that can be used in the meantime? > > > > > > > > > > > > BR > > > > > > Ruediger > > > > > > > Stefano > > > > ___ > > > > 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 > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] was "Acceptable Behaviour.." --> Forum
+1 for keeping this ML and (eventually) improving TJC. Personally, TJC currently suffers of one big drawback, which is not even technical: it is perceived more as a generic issue-reporting / feature-requesting tool than anything else. Developer related questions have always been reported on this ML first, and later on TJC mainly when it resulted in a bug of some sort. I'm not against forums, I just can't afford following another on-line source, two is more than enough for my (limited I must admit) spare time :-) On Mon, May 26, 2014 at 9:53 AM, Norbert Wenzel < norbert.wenzel.li...@gmail.com> wrote: > On 05/26/2014 09:21 AM, Ruediger Gad wrote: > > Why not let the users make the decision? > > I.e., we have a mailing list and a Q&A site already, just the forum is > > missing. > > So, if there were a forum as well, it would show over time how the usage > > and the user counts of the different infrastructures develops. > > I know that from other projects and what happened there was that some > people use forums and some people use mailinglists. The two communities > don't have much intersection. Which might or might not be a desired > outcome depending on the size of the community. > > Personally I have to say that I wouldn't use a forum or any other > web-based platform. I mean, if I really had to I'd post my question > there but I wouldn't follow discussions, since I'd need to actively > visit the forum. I prefer ML because I have one single spot where all > messages of all lists can be found and I'm reading along when I have the > time to do so. > > So besides my personal opinion I just wanted to say that too many > options for discussion might lead to fragmentation instead of making > everybody happy. > > Norbert > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Right to silence / General Mailing List
I absolutely agree to the general mailing list idea. Following this list when commuting mainly from my Jolla which has no email threading ability (*hint* *hint*) has become a real pain in the a$$ in the last few days ;) On Fri, May 23, 2014 at 10:27 AM, wrote: > +1 > > Zitat von "Panu Artimo" : > > I'm starting to think this whole thread is another instance of the >> problem that caused the initial problem in the first place. +1 plus >> for creating a "general" mailing list for subjects not directly >> related to software development and technical issues. >> ___ >> 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 > -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Screenshots in silica reference
+1 for the screenshots On Fri, May 23, 2014 at 7:21 AM, Kimmo Lindholm wrote: > > Hi, > > I so would like to see screenshots in silica reference. > > Like there is on "common pitfails" -page. > > -kimmo > -- > Lähetetty Jollastani > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org -- Luca Donaggio ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Some problems since 1.038+ update.
I think you should use QScopedPointers in your main:
QScopedPointer app(SailfishApp::application(argc,
argv));
QScopedPointer view(SailfishApp::createView());
Covers (and pages as well) can see all your ApplicationWindow (ie: their
parent) properties.
On Fri, Apr 25, 2014 at 10:14 AM, Gabriel Böhme <
m.gabrielboe...@googlemail.com> wrote:
> Hi sailors,
>
> I have released my app "Freiertag" in the days Jolla started. It worked
> pretty well, but now some updates later (since 1.038 and later) I'm facing
> a problem, I can't find a solution for.
>
> Starting the app first time works, but on the second try it crashes. After
> some inspection it seems the problem is, that the app is don't quit
> correctly. I can use the gesture in Emulator or press and click the X, in
> both cases it's still running, after a kill via SSH, it can be started
> again. The strange thing is, that it worked earlier.
>
> Thats the code from main:
>
> #include #include "FreiertagCom.hpp"
>
> int main(int argc, char *argv[])
>
> {
>
> QGuiApplication *app = SailfishApp::application(argc, argv);
>
> QQuickView *view = SailfishApp::createView();
>
> //create a new ListModel for the results
>
> FreiListModel *freiModel = new FreiListModel();
>
> //create a new instance of our object that is doing th
> e most work
>
> FreiertagCom *frei = new FreiertagCom(freiModel);
>
> view->rootContext()->setContextProperty("frei", frei);
>
> view->rootContext()->setContextProperty("freiModel", freiModel);
>
> view->setSource(SailfishApp::pathTo("qml/harbour-freiertag.qml"));
>
> view->showFullScreen();
>
> return app->exec();
>
> }
>
> Another thing is, that I've set my cover and QML pages in this way:
>
>
> import QtQuick 2.0import Sailfish.Silica 1.0
>
> import "pages"
>
> import "cover"
>
> ApplicationWindow
>
> {
>
> id: mainApplicationWindow
>
> MainPage {id: mainPage}
>
> StartCover {id: startCover}
>
> ResultPage {id: resultPage}
>
> initialPage: mainPage
>
> cover: startCover
>
> }
>
>
> I was doing it, to set text and other informations on the cover(s). But
> now that seems not to work anymore. So how can I "talk" to a cover, if I'm
> setting it via Qt.resolvedUrl for example?
>
> Thank you very much! :)
>
> Gabriel.
>
>
>
>
> ___
> SailfishOS.org Devel mailing list
>
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] SDK 1404 and translations
Thanks a lot Juha, I'll give the latest .prf a try! On Tue, Apr 22, 2014 at 4:10 PM, Juha Kallioinen wrote: > On 22.04.2014 16:47, Luca Donaggio wrote: > > Did I hit a bug with the newly added translations support? > > This two lines in .pro (I just changed the lang code in standard .pro > file created by sialfishapp/qtquick app wizard) file: > > CONFIG += sailfishapp_i18n > TRANSLATIONS += translations/harbour-yourproject-it.ts > > produce the following error at buld time: > > lrelease error: Cannot open > /home/mersdk/share/Projects/SailfishOS/harbour-yourproject/translations/harbour-yourproject-it.ts: > No such file or directory > > > Looking at sailfishapp_i18n.prf it seems it generates > harbour-yourproject.ts file only, not all the *.ts files specified in your > .pro file. > > > > Did I get something wrong or is it really a bug? > > > You did nothing wrong. It is a bug. > > The translation support was very lightly tested and could fail in a number > of ways. > > This support was changed and fixed over the Easter weekend. If you want to > try the changes and know what to do, you can replace the > sailfishapp_18n.prf file in the sb2 targets with the latest from here: > > > https://github.com/sailfish-sdk/libsailfishapp/blob/master/data/sailfishapp_i18n.prf > > Or as a workaround you can copy the existing .ts file to > harbour-yourproject-it.ts in the project's translations folder. > > The changes will be released after the next device software release. > > Best regards, > Juha > > > > ___ > SailfishOS.org Devel mailing list > -- Luca Donaggio ___ SailfishOS.org Devel mailing list
[SailfishDevel] SDK 1404 and translations
Did I hit a bug with the newly added translations support?
This two lines in .pro (I just changed the lang code in standard .pro file
created by sialfishapp/qtquick app wizard) file:
CONFIG += sailfishapp_i18n
TRANSLATIONS += translations/harbour-yourproject-it.ts
produce the following error at buld time:
lrelease error: Cannot open
/home/mersdk/share/Projects/SailfishOS/harbour-yourproject/translations/harbour-yourproject-it.ts:
No such file or directory
Looking at sailfishapp_i18n.prf it seems it generates
harbour-yourproject.ts file only, not all the *.ts files specified in your
.pro file.
lupdate command is invoked as per directive:
update_translations.commands += mkdir -p translations && lupdate
$${TRANSLATION_SOURCES} -ts $${TS_FILE}
where $${TS_FILE} is defined beforehand as follows:
TS_FILE = $${_PRO_FILE_PWD_}/translations/$${TARGET}.ts
Shouldn't it cycle through every file in $${TRANSLATIONS} instead and run
lupdate accordingly?
Something like this (beware: I'm in no way a cmake expert!!!):
for(ts_file, TRANSLATIONS) {
update_translations.commands += lupdate $${TRANSLATION_SOURCES} -ts
$$ts_file
}
Did I get something wrong or is it really a bug?
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] SailfishOS SDK April update available tomorrow. [update:all installers and repositories are online]
l/remove multiple packages from a specific target > - Updates page has a "Check for updates now" button > - Added Harbour tools page with RPM validator tool > > Installer: > - Better VirtualBox version checking. Lowest version supported is v4.0 > - Install virtual machines using correct VirtualBox version specific > parameters > - Handle empty alternate projects folder setting > - Install Sailfish template project as a package making it easier to > update > - Display Sailfish logo on Mac installer > - MerSDK no longer directly uses User's home directory, but mounts it as > /home/mersdk/share/ inside the virtual machine > - User's home directory is no longer polluted with a .scratchbox2 folder > - Shared mounts are mounted with correct access rights > - Default i486 target renamed to SailfishOS-i486 > - Rework documentation packaging > > Emulator: > - Applications can be removed from the Emulator's home screen by > long-clicking on the application icon, just like it is done on the phone. > > If you have any questions, you can either send email to this mailing list: > devel@lists.sailfishos.org or write it up in http://together.jolla.comand tag > your issue with 'sdk'. > > Happy hacking, > Jolla SDK Team. > > > ___ > SailfishOS.org Devel mailing list > -- Luca Donaggio ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] where to find any statistics about apps published in Jolla Harbour?
AFAIK, you can't (yet)! These features are planned but not yet implemented in Horbour web interface (harbour.jolla.com). On Wed, Apr 16, 2014 at 3:37 PM, Zoltán Lutor wrote: > Hi, > > Any source where developers can track their apps (downloads, reviews, > comments, whatnot) for Jolla Harbour? > > Thx, > > Zoltan > > ___ > SailfishOS.org Devel mailing list > -- Luca Donaggio ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem
This reminds me of SDK RPM-validator tool complaining about files with
executable permission (it issued a warning about possible deprecation of
executable files in RPM according to Harbour rules).
If any sort of permission-scheme has to be enforced, shouldn't the SDK's
RPM generator take care of it by itself?
On Wed, Apr 16, 2014 at 2:41 PM, Andrey Kozhevnikov
wrote:
> IMHO you should manage file permissions yourself before deploying?
>
> 16.04.2014 18:39, christopher.l...@thurweb.ch пишет:
>
> Hi All
>>
>> I have just installed the April SDK update, and have opened an existing
>> app, and am trying to deploy to my Jolla.
>>
>> The app worked with the previous SDK release, and is already installed on
>> the phone.
>>
>> If I deploy as "Deploy by copying Binaries" then thinks work as expected,
>> and the app successfully deploys and starts on the phone.
>>
>> If I deploy as "Deploy as RPM Package", then I get the error below in
>> QtCreator, and a "white screen of death" on the phone.
>>
>>
>> [W] unknown:72 - file:///usr/share/landed26_QT5/qml/landed26_QT5.qml:72:5:
>> Type MainPage unavailable
>> MainPage {
>> ^
>> [W] unknown:9 - file:///usr/share/landed26_QT5/qml/gui/MainPage.qml:9:1:
>> Script file:///usr/share/landed26_QT5/qml/javascript/landed.js
>> unavailable
>> import "../javascript/landed.js" as LJS
>> ^
>> [W] unknown:-1 - file:///usr/share/landed26_QT5/qml/javascript/landed.js:
>> File not found
>>
>> I also get the white screen when trying to open the app.
>>
>> Via SSH on the jolla device I can find the file is present:
>> [nemo@Jolla javascript]$ pwd
>> /usr/share/landed26_QT5/qml/javascript
>> [nemo@Jolla javascript]$ ls -ahl
>> total 48K
>> drwxr-xr-x 1 root root 152 2014-04-16 14:31 .
>> drwxr-xr-x 1 root root 110 2014-04-16 14:31 ..
>> -rw-r--r-- 1 root root 4.2K 2014-04-16 14:31 jsonpath.js
>> -rw--- 1 root root 349 2014-04-16 14:31 landed.js
>> -rw--- 1 root root 1.2K 2014-04-16 14:31 message.js
>> -rwxr-xr-x 1 root root 9.4K 2014-04-16 14:31 readDataModel.js
>> -rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
>> -rw-r--r-- 1 root root 5.2K 2014-04-16 14:31 writeDataModel.js
>>
>> However the access permissions look very strange. I suspect that all the
>> js files should have rights like -rwxr-xr-x
>>
>> Chris
>>
>>
>>
>> ___
>> SailfishOS.org Devel mailing list
>>
>
> ___
> SailfishOS.org Devel mailing list
>
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] SailfishOS SDK April update available tomorrow.
What about localization? I've seen some work in that area in libsailfishapp git repo, does it make the cut and is included in present update? Can you give some hints on how we should use it? On Tue, Apr 15, 2014 at 8:36 PM, Jarko Vihriala wrote: > Hello again, > > Tomorrow (16 April) at 10:00 UTC we will publish new installers, and > package repositories for our Sailfish OS SDK version Alpha-1404-Qt5. Please > note that links in this email are updated at that time as well. > > We apologise for the long delay between the SDK updates. We had to > completely recreate our SDK production environment before being able to > release an update. This took longer than expected and is the main reason > for the delay. > > If you already have an existing Alpha-Qt5 SDK installed you should see the > Updates Available icon in Qt Creator. If you don't have a previous SDK > installation you can get the latest installer from > http://www.sailfishos.org. It is recommended to uninstall the old SDK and > download a new installer. > > SDK content has been updated to match Jolla Release 1.0.5.16. Please see > below for detailed information of the changed items. > > A couple of things you should be aware of: > - Like before, in this update the build engine, emulator and targets are > re-installed so you will lose all changes you may have made in those - > however, if your application packaging is done correctly, rebuilding your > projects should reinstall the packages you have been using. > - All customization done to SDK (adding new package repositories, adding > custom targets, additional source paths) will be removed during the > installation process so make your own backup of those before starting the > update. > - If you import existing projects made with a previous version of the > Sailfish OS SDK, make sure you select the correct kit in the project > configuration step. Both ARM and i486 kits are available. > - Windows users need to install VC10 runtime from > http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328 or the > Installer will ask for admin rights during installation. > - Package repository contents have been updated and consequently using a > previous SDK version with these package repositories is not supported. > - For more information, please see the SDK Alpha-Qt5 known issues list at: > https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues. > - Oldest Mac OS X supported is now 10.8.5 (Mountain Lion). Other supported > platforms can be found from: > https://sailfishos.org/alpha_qt5_sdk_release_notes.html > > Here is a summary of changes: > > SDK IDE (Qt Creator) > - Crash fixes on OS X > - Yaml editor removed from Qt Creator and yaml files are presented as > plain text > - Alternate projects folder can be changed from Mer settings page > - Better path handling for shared directories in Windows > - Updated Sailfish template project > - Handle errors in project build/deploy phase more gracefully > - Debugging with GDB from Qt Creator works with the Emulator and the > Device > - Tooltips are displayed for Virtual Machine statuses > - Add changelog to your RPM with a .changes file > > SDK Control Center: > - Improved Targets management page > - Clean build targets are available for download via the Targets page > (pre-configured targets) > - Easily install/remove multiple packages from a specific target > - Updates page has a "Check for updates now" button > - Added Harbour tools page with RPM validator tool > > Installer: > - Better VirtualBox version checking. Lowest version supported is v4.0 > - Install virtual machines using correct VirtualBox version specific > parameters > - Handle empty alternate projects folder setting > - Install Sailfish template project as a package making it easier to > update > - Display Sailfish logo on Mac installer > - MerSDK no longer directly uses User's home directory, but mounts it as > /home/mersdk/share/ inside the virtual machine > - User's home directory is no longer polluted with a .scratchbox2 folder > - Shared mounts are mounted with correct access rights > - Default i486 target renamed to SailfishOS-i486 > - Rework documentation packaging > > Emulator: > - Applications can be removed from the Emulator's home screen by > long-clicking on the application icon, just like it is done on the phone. > > If you have any questions, you can either send email to this mailing list: > devel@lists.sailfishos.org or write it up in http://together.jolla.comand tag > your issue with 'sdk'. > > Happy hacking, > Jolla SDK Team. > > > ___ > SailfishOS.org Devel mailing list > -- Luca Donaggio ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] ShaderEffect QML element
Thanks a lot David! I'm pretty new to GLSL as well, I reached my conclusion with trial-and-error (basically commenting out each and every line of code in my fragment shader until I found the offending one) and I'm sure I tried your solution at least once, but to no avail. Oh well, now it works, so ;-) On Thu, Apr 10, 2014 at 2:14 PM, David Greaves wrote: > caveat: I'm pretty new to GLSL > > > For me: > vec2(-0.75, -0.5) > is fine. > > Note that integers like: > vec2(-0.75, 1) > fail. > > I will be putting the glsl validation and optimiser tool into mer-tools > 'soon'. > (Sooner now I know other people are playing with it) > > David > > > On 10/04/14 12:50, Luca Donaggio wrote: > > I replied myself: > > > > the problem was with this syntax in my fragment shader code: > > > > vec2(-0.75f, -0.5f) > > > > it's legal inside the emulator but *not on real device*. > > > > Of course, all it takes to make it work is using float() constructor: > > > > vec2(float(-0.75), float(-0.5)) > > > > Hope it could help someone else. > > > > > > > > On Thu, Apr 10, 2014 at 12:05 PM, Luca Donaggio > <mailto:donag...@gmail.com>> wrote: > > > > Hi, > > > > Is ShaderEffect QML element supposed to work on device (I'm on > 1.0.4.20)? > > > > I'm always getting this error (content of log property): > > > > QOpenGLShader::compile(Fragment): failed > > > > *** Problematic Fragment shader source code *** > > > > [W] QOpenGLShaderPrivate::compile:326 - #ifndef > GL_FRAGMENT_PRECISION_HIGH > > > > #define highp mediump > > > > #endif > > > > > > [... my shader code ...] > > > > > > *** > > > > QQuickCustomMaterialShader: Shader compilation failed: > > > > [W] QQuickCustomMaterialShader::compile:285 - "failed" > > > > *** Fragment shader *** > > > > failed > > > > > > > > It works just fine on emulator though. > > > > Are there some (known) differencies from the GLSL code "understood" > by the > > emulator and a real device? > > > > Thanks, > > > > -- > > Luca Donaggio > > > > > > > > > > -- > > Luca Donaggio > > > > > > ___ > > SailfishOS.org Devel mailing list > > > > ___ > SailfishOS.org Devel mailing list > -- Luca Donaggio ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] ShaderEffect QML element
I replied myself: the problem was with this syntax in my fragment shader code: vec2(-0.75f, -0.5f) it's legal inside the emulator but *not on real device*. Of course, all it takes to make it work is using float() constructor: vec2(float(-0.75), float(-0.5)) Hope it could help someone else. On Thu, Apr 10, 2014 at 12:05 PM, Luca Donaggio wrote: > Hi, > > Is ShaderEffect QML element supposed to work on device (I'm on 1.0.4.20)? > > I'm always getting this error (content of log property): > > QOpenGLShader::compile(Fragment): failed > > *** Problematic Fragment shader source code *** > > [W] QOpenGLShaderPrivate::compile:326 - #ifndef GL_FRAGMENT_PRECISION_HIGH > > #define highp mediump > > #endif > > > [... my shader code ...] > > > *** > > QQuickCustomMaterialShader: Shader compilation failed: > > [W] QQuickCustomMaterialShader::compile:285 - "failed" > > *** Fragment shader *** > > failed > > > > It works just fine on emulator though. > > Are there some (known) differencies from the GLSL code "understood" by the > emulator and a real device? > > Thanks, > > -- > Luca Donaggio > -- Luca Donaggio ___ SailfishOS.org Devel mailing list
[SailfishDevel] ShaderEffect QML element
Hi, Is ShaderEffect QML element supposed to work on device (I'm on 1.0.4.20)? I'm always getting this error (content of log property): QOpenGLShader::compile(Fragment): failed *** Problematic Fragment shader source code *** [W] QOpenGLShaderPrivate::compile:326 - #ifndef GL_FRAGMENT_PRECISION_HIGH #define highp mediump #endif [... my shader code ...] *** QQuickCustomMaterialShader: Shader compilation failed: [W] QQuickCustomMaterialShader::compile:285 - "failed" *** Fragment shader *** failed It works just fine on emulator though. Are there some (known) differencies from the GLSL code "understood" by the emulator and a real device? Thanks, -- Luca Donaggio ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Binding loop (again)
I have exactly the same use case as Ragnar.
Probably a bug in ContextMenu and / or the handling of a delegate with
dynamic height from SilicaListView?
Anyway, warning apart, it seems to not affect usability at all.
On Wed, Apr 2, 2014 at 10:41 PM, Ragnar Kurm wrote:
> Hello,
>
> Stumbled again into binding loop
> and asking for help
> 1) how to track down the loops on my own?
> 2) how to solve particular problem (below)?
>
> Context: Screen is filled with ListItems which can be manipulated by
> ContextMenu.
> When held on last item on screen it would open submenu below screen,
> but it is accommodated by changing contentY which:
> * causes binding loop warnings
> * but visually it actually works ok by scrolling screen
>
> I prefer to write code without warnings.
> Included minimal code below.
>
> I consider myself quite new here
> and havent seen much Silica talk here...
> Is it appropriate place for Silica related questions?
>
> Ragnar
>
>
>
> import QtQuick 2.0
> import Sailfish.Silica 1.0
>
> Page {
>
> SilicaListView { // QML SilicaListView: Binding loop detected for
> property "contentY"
>
> anchors.fill: parent // prevent "Binding loop" type 1
>
> model: ListModel {
> id: model
> Component.onCompleted: {
> for (var i=0 ; i<12 ; i++) model.append({"i": i});
> }
> }
>
> delegate: ListItem {
> menu: ContextMenu { MenuItem { text: "Delete?" } } // hold on
> last item on screen to open the menu
> Label { text: i }
> }
> }
> }
>
> ___
> SailfishOS.org Devel mailing list
>
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] Why do I get "binding loop" error?
What if the flickable is a SilicaListView? It's anchored to fill its container and the loop on contentY when showing a ContextMenu happens only when it's near the bottom of the page. On Mon, Mar 24, 2014 at 11:05 PM, Ragnar Kurm wrote: > Thank you, it works. > Now I stared to understand this conceptually! > Ragnar > > > a) give the flickable a valid geometry, and >> b) specify the content size. -- J-P Nurmi >> > > ___ > SailfishOS.org Devel mailing list > -- Luca Donaggio ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Why do I get "binding loop" error?
I'm experiencing the same in a slightly different context (a SilicaListView
with a ContextMenu dynamically created and on shown after a long press on
each ListItem delegate). To me it seems related to the ContextMenu item,
when it becomes visible and it pushes down the content below.
On Sun, Mar 23, 2014 at 12:11 PM, Ragnar Kurm wrote:
> Hello,
>
> I have problems with an error:
> Test.qml:7: QML SilicaFlickable: Binding loop detected for property
> "contentY"
>
> What do I miss?
>
> Ragnar
>
>
>
> import QtQuick 2.0
> import Sailfish.Silica 1.0
>
> Dialog {
> id: dialog
> SilicaFlickable {
> Column {
> ComboBox {
> label: "Label"
> width: dialog.width
> menu: ContextMenu {
> width: dialog.width
> MenuItem { text: "Item 1" }
> }
> }
> }
> }
> }
> ___
> SailfishOS.org Devel mailing list
>
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] QML Format and Formatter objects info
Thank you Andrey!
On Mon, Feb 24, 2014 at 11:22 AM, Andrey Kozhevnikov wrote:
> via plugins.qmltypes:
>
> Component {
> name: "DeclarativeFormatter"
> prototype: "QObject"
> exports: [
> "Formatter 1.0"
> ]
> Enum {
> name: "FormatType"
> values: {
> "Timepoint": 0,
> "TimepointRelative": 1,
> "TimepointRelativeCurrentDay": 2,
> "TimepointSectionRelative": 3,
> "WeekdayNameStandalone": 4,
> "DurationElapsed": 5,
> "TimeValueTwelveHours": 6,
> "TimeValueTwentyFourHours": 7,
> "TimeValue": 8,
> "DurationShort": 9,
> "DurationLong": 10,
> "CallTimeRelative": 1
> }
> }
> Enum {
> name: "ArticleType"
> values: {
> "AnteMeridiemIndicator": 0,
> "PostMeridiemIndicator": 1
> }
> }
> Enum {
> name: "TextFormatType"
> values: {
> "Ascii7Bit": 0,
> "PortableFilename": 1
> }
> }
> Method {
> name: "formatDate"
> type: "string"
> Parameter { name: "dateTime"; type: "QDateTime" }
> Parameter { name: "formatType"; type: "int" }
> }
> Method {
> name: "formatArticle"
> type: "string"
> Parameter { name: "articleType"; type: "int" }
> }
> Method {
> name: "formatDuration"
> type: "string"
> Parameter { name: "seconds"; type: "int" }
> Parameter { name: "formatType"; type: "int" }
> }
> Method {
> name: "formatFileSize"
> type: "string"
> Parameter { name: "bytes"; type: "qlonglong" }
> }
> Method {
> name: "formatText"
> type: "string"
> Parameter { name: "input"; type: "string" }
> Parameter { name: "formatType"; type: "int" }
>
> }
> }
>
> On 24.02.2014 16:11, Luca Donaggio wrote:
>
> Can someone point me to the documentation for Format and Formatter
> objects (QML)?
> I'm not able to find it anywhere - well, it could be it's just under my
> nose and I'm still not able to see it ;-)
>
> --
> Luca Donaggio
>
>
> ___
> SailfishOS.org Devel mailing list
>
>
>
> ___
> SailfishOS.org Devel mailing list
>
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
[SailfishDevel] QML Format and Formatter objects info
Can someone point me to the documentation for Format and Formatter objects (QML)? I'm not able to find it anywhere - well, it could be it's just under my nose and I'm still not able to see it ;-) -- Luca Donaggio ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] oauth authorization for application
I'm doing the same as Martin for my Feedly client. On auth failure, parameters attached to redirect_uri (GET method) are different; after detecting your redirect_uri you should analyze it and decode any (eventual) parameters. Auth token is among those, by the way. On Fri, Feb 14, 2014 at 10:35 AM, Oleg Linkin wrote: > I try to do as you adviced me but if I don't give access to application a > get the next url changes: > 1) https://getpocket.com/auth/approve_access > 2) linksbag:/authorizationFinished - this is my redirect_uri > > If I give access to application a get the next url changes: > 1) https://getpocket.com/auth/approve_access > 2) linksbag:/authorizationFinished > > All this changes are equal. I can't detect was access grant or not to > application > > 2014-02-14 12:10 GMT+03:00 Martin Grimme : > > Hi, >> >> the way I'm doing it in Cargo Dock for Dropbox is basically having the >> SilicaWebview watch the uri property and react to it in the >> onUriChanged signal handler, if the redirect_uri matches the one I'm >> expecting. >> >> >> Martin >> >> >> 2014-02-14 9:32 GMT+01:00, Oleg Linkin : >> > Hi, all >> > I am developing client for getPocket.com service and I have problem with >> > auth. >> > After login service send auth status (grant permissions on not to >> > application) via redirect_uri. How I should handle it or what sequence >> of >> > actions in this case? >> > >> ___ >> SailfishOS.org Devel mailing list >> > > > ___ > SailfishOS.org Devel mailing list > -- Luca Donaggio ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] dbus-sessionbus connection fails
Using "After" directive was the key! Now my user autostarts and works as
expected using systemctl-user.
Thanks again!
On Mon, Feb 3, 2014 at 11:15 AM, Andrey Kozhevnikov
wrote:
> its not Requires directive, its After
>
>
> On 03.02.2014 16:11, Luca Donaggio wrote:
>
> Hi Andrey,
>
> yes, I tried with a:
>
> Requires=dbus .service
>
> but I did so many changes to my .service file trying to make it work that
> I can't remember exactly when I did that!
> I'll re-start with a clean one and see if it works.
>
>
>
> On Mon, Feb 3, 2014 at 11:05 AM, Andrey Kozhevnikov <
> coderusin...@gmail.com> wrote:
>
>> did you added depends for your autostart rule on some system service?
>> otherwise it wont start :)
>>
>>
>> On 03.02.2014 16:01, Luca Donaggio wrote:
>>
>> I'm fighting with the same issue: starting your dbus-using daemon with
>> "systemctl-user start" does work (ie, you'll be able to connect to session
>> bus), but autostarting with "systemctl-user enable" doesn't work, while
>> making it a system daemon (plain "systemctl" command) works the other way
>> around: it doesn't acquire the session bus (even when starting as user
>> "nemo"), but it autostarts as expected!
>>
>>
>> On Sun, Feb 2, 2014 at 9:20 PM, Dmitry wrote:
>>
>>> Hi
>>>
>>> You should run your daemon form user systemd unit.
>>> https://wiki.archlinux.org/index.php/Systemd/User
>>>
>>>
>>> On 1 February 2014 21:53, Kimmo Lindholm wrote:
>>>
>>>> Hi,
>>>>
>>>> I’m using QtDBus in my daemon (systemd service), and I can register my
>>>> own service on systemBus, and also can connect to systembus signals.
>>>> When starting executable from command line it runs ok and connects also
>>>> to the sessionbus signals successfully.
>>>> but when it is started via systemctl start I can’t connect to
>>>> sessionbus signals.
>>>>
>>>> It throws following error: “Using X11 for dbus-daemon autolaunch was
>>>> disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead”
>>>>
>>>> this is printed from code below:
>>>>
>>>> if (!QDBusConnection::sessionBus().isConnected())
>>>> {
>>>> writeToLog(qPrintable(QDBusConnection
>>>> ::sessionBus().lastError().message()));
>>>> exit(EXIT_FAILURE);
>>>> }
>>>>
>>>> I figured out that DBUS_SESSION_BUS_ADDRESS is an environment
>>>> variable which obviously is not visible in this context.
>>>>
>>>> is there a way to pass this to the systemd service??
>>>>
>>>> regards,
>>>> Kimmo
>>>>
>>>>
>>>> ___
>>>> SailfishOS.org Devel mailing list
>>>>
>>>
>>>
>>> ___
>>> SailfishOS.org Devel mailing list
>>>
>>
>>
>>
>> --
>> Luca Donaggio
>>
>>
>> ___
>> SailfishOS.org Devel mailing list
>>
>>
>>
>> ___
>> SailfishOS.org Devel mailing list
>>
>
>
>
> --
> Luca Donaggio
>
>
> ___
> SailfishOS.org Devel mailing list
>
>
>
> ___
> SailfishOS.org Devel mailing list
>
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] dbus-sessionbus connection fails
Thanks Andrey, I'll try that!
On Mon, Feb 3, 2014 at 11:15 AM, Andrey Kozhevnikov
wrote:
> its not Requires directive, its After
>
>
> On 03.02.2014 16:11, Luca Donaggio wrote:
>
> Hi Andrey,
>
> yes, I tried with a:
>
> Requires=dbus .service
>
> but I did so many changes to my .service file trying to make it work that
> I can't remember exactly when I did that!
> I'll re-start with a clean one and see if it works.
>
>
>
> On Mon, Feb 3, 2014 at 11:05 AM, Andrey Kozhevnikov <
> coderusin...@gmail.com> wrote:
>
>> did you added depends for your autostart rule on some system service?
>> otherwise it wont start :)
>>
>>
>> On 03.02.2014 16:01, Luca Donaggio wrote:
>>
>> I'm fighting with the same issue: starting your dbus-using daemon with
>> "systemctl-user start" does work (ie, you'll be able to connect to session
>> bus), but autostarting with "systemctl-user enable" doesn't work, while
>> making it a system daemon (plain "systemctl" command) works the other way
>> around: it doesn't acquire the session bus (even when starting as user
>> "nemo"), but it autostarts as expected!
>>
>>
>> On Sun, Feb 2, 2014 at 9:20 PM, Dmitry wrote:
>>
>>> Hi
>>>
>>> You should run your daemon form user systemd unit.
>>> https://wiki.archlinux.org/index.php/Systemd/User
>>>
>>>
>>> On 1 February 2014 21:53, Kimmo Lindholm wrote:
>>>
>>>> Hi,
>>>>
>>>> I’m using QtDBus in my daemon (systemd service), and I can register my
>>>> own service on systemBus, and also can connect to systembus signals.
>>>> When starting executable from command line it runs ok and connects also
>>>> to the sessionbus signals successfully.
>>>> but when it is started via systemctl start I can’t connect to
>>>> sessionbus signals.
>>>>
>>>> It throws following error: “Using X11 for dbus-daemon autolaunch was
>>>> disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead”
>>>>
>>>> this is printed from code below:
>>>>
>>>> if (!QDBusConnection::sessionBus().isConnected())
>>>> {
>>>> writeToLog(qPrintable(QDBusConnection
>>>> ::sessionBus().lastError().message()));
>>>> exit(EXIT_FAILURE);
>>>> }
>>>>
>>>> I figured out that DBUS_SESSION_BUS_ADDRESS is an environment
>>>> variable which obviously is not visible in this context.
>>>>
>>>> is there a way to pass this to the systemd service??
>>>>
>>>> regards,
>>>> Kimmo
>>>>
>>>>
>>>> ___
>>>> SailfishOS.org Devel mailing list
>>>>
>>>
>>>
>>> ___
>>> SailfishOS.org Devel mailing list
>>>
>>
>>
>>
>> --
>> Luca Donaggio
>>
>>
>> ___
>> SailfishOS.org Devel mailing list
>>
>>
>>
>> ___
>> SailfishOS.org Devel mailing list
>>
>
>
>
> --
> Luca Donaggio
>
>
> ___
> SailfishOS.org Devel mailing list
>
>
>
> ___
> SailfishOS.org Devel mailing list
>
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] dbus-sessionbus connection fails
Hi Andrey,
yes, I tried with a:
Requires=dbus .service
but I did so many changes to my .service file trying to make it work that I
can't remember exactly when I did that!
I'll re-start with a clean one and see if it works.
On Mon, Feb 3, 2014 at 11:05 AM, Andrey Kozhevnikov
wrote:
> did you added depends for your autostart rule on some system service?
> otherwise it wont start :)
>
>
> On 03.02.2014 16:01, Luca Donaggio wrote:
>
> I'm fighting with the same issue: starting your dbus-using daemon with
> "systemctl-user start" does work (ie, you'll be able to connect to session
> bus), but autostarting with "systemctl-user enable" doesn't work, while
> making it a system daemon (plain "systemctl" command) works the other way
> around: it doesn't acquire the session bus (even when starting as user
> "nemo"), but it autostarts as expected!
>
>
> On Sun, Feb 2, 2014 at 9:20 PM, Dmitry wrote:
>
>> Hi
>>
>> You should run your daemon form user systemd unit.
>> https://wiki.archlinux.org/index.php/Systemd/User
>>
>>
>> On 1 February 2014 21:53, Kimmo Lindholm wrote:
>>
>>> Hi,
>>>
>>> I’m using QtDBus in my daemon (systemd service), and I can register my
>>> own service on systemBus, and also can connect to systembus signals.
>>> When starting executable from command line it runs ok and connects also
>>> to the sessionbus signals successfully.
>>> but when it is started via systemctl start I can’t connect to sessionbus
>>> signals.
>>>
>>> It throws following error: “Using X11 for dbus-daemon autolaunch was
>>> disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead”
>>>
>>> this is printed from code below:
>>>
>>> if (!QDBusConnection::sessionBus().isConnected())
>>> {
>>> writeToLog(qPrintable(QDBusConnection
>>> ::sessionBus().lastError().message()));
>>> exit(EXIT_FAILURE);
>>> }
>>>
>>> I figured out that DBUS_SESSION_BUS_ADDRESS is an environment variable
>>> which obviously is not visible in this context.
>>>
>>> is there a way to pass this to the systemd service??
>>>
>>> regards,
>>> Kimmo
>>>
>>>
>>> ___
>>> SailfishOS.org Devel mailing list
>>>
>>
>>
>> ___
>> SailfishOS.org Devel mailing list
>>
>
>
>
> --
> Luca Donaggio
>
>
> ___
> SailfishOS.org Devel mailing list
>
>
>
> ___
> SailfishOS.org Devel mailing list
>
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] dbus-sessionbus connection fails
I'm fighting with the same issue: starting your dbus-using daemon with
"systemctl-user start" does work (ie, you'll be able to connect to session
bus), but autostarting with "systemctl-user enable" doesn't work, while
making it a system daemon (plain "systemctl" command) works the other way
around: it doesn't acquire the session bus (even when starting as user
"nemo"), but it autostarts as expected!
On Sun, Feb 2, 2014 at 9:20 PM, Dmitry wrote:
> Hi
>
> You should run your daemon form user systemd unit.
> https://wiki.archlinux.org/index.php/Systemd/User
>
>
> On 1 February 2014 21:53, Kimmo Lindholm wrote:
>
>> Hi,
>>
>> I’m using QtDBus in my daemon (systemd service), and I can register my
>> own service on systemBus, and also can connect to systembus signals.
>> When starting executable from command line it runs ok and connects also
>> to the sessionbus signals successfully.
>> but when it is started via systemctl start I can’t connect to sessionbus
>> signals.
>>
>> It throws following error: “Using X11 for dbus-daemon autolaunch was
>> disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead”
>>
>> this is printed from code below:
>>
>> if (!QDBusConnection::sessionBus().isConnected())
>> {
>> writeToLog(qPrintable(QDBusConnection
>> ::sessionBus().lastError().message()));
>> exit(EXIT_FAILURE);
>> }
>>
>> I figured out that DBUS_SESSION_BUS_ADDRESS is an environment variable
>> which obviously is not visible in this context.
>>
>> is there a way to pass this to the systemd service??
>>
>> regards,
>> Kimmo
>>
>>
>> ___
>> SailfishOS.org Devel mailing list
>>
>
>
> ___
> SailfishOS.org Devel mailing list
>
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] Background Services
AFAIU this is a planned feature, but is not possible yet. On Fri, Jan 24, 2014 at 2:29 PM, سلمان الجمّاز (Salman Aljammaz) < salman.aljam...@gmail.com> wrote: > Come to mention it, is there a way to register custom services for Jolla's > built-in Accounts/Sync facilities? > > Apologies if this is documented somewhere, I couldn't find it! > > > > 2014/1/24 سلمان الجمّاز (Salman Aljammaz) > > Hi all >> >> Is there (yet) a preferred way to create background services? Stuff like >> sync/dbus services etc. >> >> At the moment I'm manually using systemd and I'm wondering if there's a >> higher level interface for long lived processes. >> >> Salman >> >> > ___ > SailfishOS.org Devel mailing list > -- Luca Donaggio ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] How to automatically start a daemon with systemd
Thank you Kimmo, maybe user daemons are not supported? I'll try to run it as a system daemon and see if it works. By the way, can someone explain what does /usr/bin/invoker do? When is it needed / useful? On Fri, Jan 24, 2014 at 12:35 PM, Kimmo Lindholm wrote: > I have put my .service file under systemd/system –folder and used > systemctl enable (not -user) and it starts successfully at boot. > > I start it without invoker (ExecStart directly calls the executable) > > > > (But I need root access for the daemon) > > > > > > > > *From:* devel-boun...@lists.sailfishos.org [mailto: > devel-boun...@lists.sailfishos.org] *On Behalf Of *Luca Donaggio > *Sent:* 24. tammikuuta 2014 11:42 > *To:* Sailfish OS Developers > *Subject:* [SailfishDevel] How to automatically start a daemon with > systemd > > > > Hi all, > > I'v written a small personal (not looking for harbour approval here) C++ > app which periodically connects to a web service and displays some > information into a notification via DBus. > > This is the .service file which I've deployed in /etc/systemd/user: > > > [Unit] > Description=My own daemon > Requires=dbus.service > > [Service] > Type=simple > ExecStart=/usr/bin/invoker --type=generic /usr/bin/myowndaemon > > [Install] > WantedBy=multi-user.target > > after the usual: > > systemctl-user daemon-reload > > systemctl-user start myowndaemon.service > > it correctly starts. > > Now if I issue a: > > systemctl-user enable myowndaemon.service > > and I reboot my Jolla, it doesn't automatically start. > > This is my first attempt with systemd, I tried googling around but I > didn't find anything helpful. > > Wht am I missing? > > Thanks a lot, > > > -- > Luca Donaggio > > ___ > SailfishOS.org Devel mailing list > -- Luca Donaggio ___ SailfishOS.org Devel mailing list
[SailfishDevel] How to automatically start a daemon with systemd
Hi all, I'v written a small personal (not looking for harbour approval here) C++ app which periodically connects to a web service and displays some information into a notification via DBus. This is the .service file which I've deployed in /etc/systemd/user: [Unit] Description=My own daemon Requires=dbus.service [Service] Type=simple ExecStart=/usr/bin/invoker --type=generic /usr/bin/myowndaemon [Install] WantedBy=multi-user.target after the usual: systemctl-user daemon-reload systemctl-user start myowndaemon.service it correctly starts. Now if I issue a: systemctl-user enable myowndaemon.service and I reboot my Jolla, it doesn't automatically start. This is my first attempt with systemd, I tried googling around but I didn't find anything helpful. Wht am I missing? Thanks a lot, -- Luca Donaggio ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] QML Timer stops running
Thanks!
On Wed, Jan 15, 2014 at 12:18 PM, Jonni Rainisto
wrote:
> Yes,
>
> You can for example listen to for activity suspend resume
> https://github.com/nemomobile/qmsystem/bvib/master/system/qmactivity.h<https://github.com/nemomobile/qmsystem/blob/master/system/qmactivity.h>
>
> And for display on/off signal is displayStateChanged:
> https://github.com/nemomobile/qmsystem/blob/master/system/qmdisplaystate.h
>
> Br, Jonni
>
> --
> *From:* devel-boun...@lists.sailfishos.org [
> devel-boun...@lists.sailfishos.org] on behalf of Luca Donaggio [
> donag...@gmail.com]
> *Sent:* Wednesday, January 15, 2014 11:29 AM
>
> *To:* Sailfish OS Developers
> *Subject:* Re: [SailfishDevel] QML Timer stops running
>
> I'm in a similar situation: I've written a small app for my personal
> use that periodically download some stats from one of my company's web
> servers.
> I'm perfectly fine with it not doing anything while in deep-sleep, but I
> would like to do a forced update as soon as the device wakes up.
> How can I detect such event from C++ side (my app is run as a daemon
> actually, so no qml involved)? Is there some DBus signal I can listen to?
>
> Thanks,
>
> Luca Donaggio
>
>
> On Wed, Jan 15, 2014 at 9:26 AM, Jonni Rainisto
> wrote:
>
>> Hi,
>>
>> For the love of ***, dont use libiphb every 5 seconds, that will kill
>> batterylife for suspend (store QA will reject apps that eat battery). Its
>> more meant to be triggered every 10, 15, 30 etc. minutes. So if you want to
>> make 25 minute timer that works even while suspended, then you should do
>> libiphb to wake up after 25 minutes.
>>
>> Or if you want to make libiphb to wake up device every 10 minutes, you
>> can make your application to check how much time has really passed since
>> last wakeup by checking hw clock (as that is the only clock which is
>> updated even while beeing suspended) timestamps like this:
>>
>> static void tv_get_monotime(struct timeval *tv)
>> {
>> #if defined(CLOCK_BOOTTIME)
>> struct timespec ts;
>> if (clock_gettime(CLOCK_BOOTTIME, &ts) < 0)
>> if (clock_gettime(CLOCK_MONOTONIC, &ts) < 0)
>> qFatal("Can't clock_gettime!");
>> TIMESPEC_TO_TIMEVAL(tv, &ts);
>> #endif
>> }
>>
>>
>>
>> From: devel-boun...@lists.sailfishos.org [
>> devel-boun...@lists.sailfishos.org] on behalf of Thomas Tanghus [
>> tho...@tanghus.net]
>> Sent: Tuesday, January 14, 2014 4:11 PM
>> To: Sailfish OS Developers
>> Subject: Re: [SailfishDevel] QML Timer stops running
>>
>> On Tuesday 14 January 2014 13:05 Graham Cobb wrote:
>> > On 14/01/14 01:14, Thomas Tanghus wrote:
>> > > On Tuesday 14 January 2014 01:53 Ove Kåven wrote:
>> > >> No matter what OS or platform you're on, counting the number of times
>> > >> your timer callback is called is *never* a good idea, even on desktop
>> > >> PCs. Timer callbacks can be skipped for any number of reasons (heavy
>> > >> system load, laptop suspend, etc).
>> >
>> > > Good point. That will also at least work around the issue when in
>> > > "pre-deep- sleep".
>> >
>> > I agree with Ove (that is how every timer function I have ever worked on
>> > works, from interrupt handlers in embedded system kernels through to the
>> > GPE Calendar app) -- repeating timers are a convenience, but are never
>> > treated as accurate.
>> >
>> > But I would also suggest that for any apps that do timing, when the app
>> > is not being displayed (and so the screen doesn't need to be updated),
>> > the code should switch to using a single-shot timer set to the time when
>> > the next event happens, instead of using repeating timers. If the
>> > kitchen timer is set for 25 minutes and the screen is blank you don't
>> > want your app waking up every second. Of course, it is a little bit
>> > tedious to write the code to cancel the long timer and restart short
>> > timers when the screen is turned back on but the user will thank you
>> for it.
>>
>> It sounds like a good idea, and should be fairly easy to implement. I just
>> don't know how to detect when the screen is off (this is my first
>> baby-steps
>> in mobile coding). We have the applicationActive property, but the cover
>> can
>> still be active and visible while it is false.
>>
>>
Re: [SailfishDevel] QML Timer stops running
I'm in a similar situation: I've written a small app for my personal use
that periodically download some stats from one of my company's web servers.
I'm perfectly fine with it not doing anything while in deep-sleep, but I
would like to do a forced update as soon as the device wakes up.
How can I detect such event from C++ side (my app is run as a daemon
actually, so no qml involved)? Is there some DBus signal I can listen to?
Thanks,
Luca Donaggio
On Wed, Jan 15, 2014 at 9:26 AM, Jonni Rainisto wrote:
> Hi,
>
> For the love of ***, dont use libiphb every 5 seconds, that will kill
> batterylife for suspend (store QA will reject apps that eat battery). Its
> more meant to be triggered every 10, 15, 30 etc. minutes. So if you want to
> make 25 minute timer that works even while suspended, then you should do
> libiphb to wake up after 25 minutes.
>
> Or if you want to make libiphb to wake up device every 10 minutes, you can
> make your application to check how much time has really passed since last
> wakeup by checking hw clock (as that is the only clock which is updated
> even while beeing suspended) timestamps like this:
>
> static void tv_get_monotime(struct timeval *tv)
> {
> #if defined(CLOCK_BOOTTIME)
> struct timespec ts;
> if (clock_gettime(CLOCK_BOOTTIME, &ts) < 0)
> if (clock_gettime(CLOCK_MONOTONIC, &ts) < 0)
> qFatal("Can't clock_gettime!");
> TIMESPEC_TO_TIMEVAL(tv, &ts);
> #endif
> }
>
>
>
> From: devel-boun...@lists.sailfishos.org [
> devel-boun...@lists.sailfishos.org] on behalf of Thomas Tanghus [
> tho...@tanghus.net]
> Sent: Tuesday, January 14, 2014 4:11 PM
> To: Sailfish OS Developers
> Subject: Re: [SailfishDevel] QML Timer stops running
>
> On Tuesday 14 January 2014 13:05 Graham Cobb wrote:
> > On 14/01/14 01:14, Thomas Tanghus wrote:
> > > On Tuesday 14 January 2014 01:53 Ove Kåven wrote:
> > >> No matter what OS or platform you're on, counting the number of times
> > >> your timer callback is called is *never* a good idea, even on desktop
> > >> PCs. Timer callbacks can be skipped for any number of reasons (heavy
> > >> system load, laptop suspend, etc).
> >
> > > Good point. That will also at least work around the issue when in
> > > "pre-deep- sleep".
> >
> > I agree with Ove (that is how every timer function I have ever worked on
> > works, from interrupt handlers in embedded system kernels through to the
> > GPE Calendar app) -- repeating timers are a convenience, but are never
> > treated as accurate.
> >
> > But I would also suggest that for any apps that do timing, when the app
> > is not being displayed (and so the screen doesn't need to be updated),
> > the code should switch to using a single-shot timer set to the time when
> > the next event happens, instead of using repeating timers. If the
> > kitchen timer is set for 25 minutes and the screen is blank you don't
> > want your app waking up every second. Of course, it is a little bit
> > tedious to write the code to cancel the long timer and restart short
> > timers when the screen is turned back on but the user will thank you for
> it.
>
> It sounds like a good idea, and should be fairly easy to implement. I just
> don't know how to detect when the screen is off (this is my first
> baby-steps
> in mobile coding). We have the applicationActive property, but the cover
> can
> still be active and visible while it is false.
>
> > Unfortunately, I have no idea how you actually set up a single shot
> > timer that will fire correctly in deep sleep from the Qt environment
> > (the last time I implemented that logic was on Maemo).
>
> Rainisto pointed to libiphb[1] which I have now implemented with a crude
> wakeup every 5-10 seconds. Not optimal, but I'm OK with it for v 0.1.1 ;)
>
> [1] http://talk.maemo.org/showpost.php?p=1401318&postcount=2
>
> --
> Med venlig hilsen / Best Regards
>
> Thomas Tanghus
> ___
> SailfishOS.org Devel mailing list
> ___
> SailfishOS.org Devel mailing list
>
--
Luca Donaggio
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] [Update] Changelog for SailfishOS update 2 (1.0.2.5)
As I am in the same situation as Mike Sheldon, I did as Martin suggested:
pkcon update store-client
pkill store-client
The Store got updated, but downloading the OS update still doesn't work.
On Fri, Dec 27, 2013 at 4:44 PM, Martin Grimme wrote:
> You're right. Those apps should not be updatable before updating the OS.
>
> I think you can revive your store-client by updating the store-client
> package and then doing a "pkill store-client".
>
>
> Martin
>
>
> 2013/12/27, Mike Sheldon :
> > On Fri, 2013-12-27 at 16:35 +0100, Martin Grimme wrote:
> >> Actually the other way round. jolla-settings-accounts was updated but
> >> store was not.
> >> Did you try to update a Jolla app before rebooting?
> >
> > Yes, a number of Jolla apps presented themselves as having updates
> > available, so I allowed them to update.
> >
> > I currently have version 0.1.41-10.23.1.jolla of jolla-settings-accounts
> > and version 0.2.28-10.22.1.jolla of store-client (with zypper showing
> > 0.2.38-10.24.1.jolla available, but not updated to).
> >
> > If updates depend on a certain OS version shouldn't they be given a
> > dependency that makes such updates impossible until that version has
> > been installed?
> >
> > Cheers,
> > Mike.
> >
> >>
> >>
> >> Martin
> >>
> >>
> >> 2013/12/27, Martin Grimme :
> >> > Ouch, this looks like a partial update. Store was updated, but some
> >> > sign in library was not.
> >> > I wonder how this can happen.
> >> > Can you check in Terminal what version of jolla-settings-accounts you
> >> > have?
> >> >
> >> >
> >> > Martin
> >> >
> >> > 2013/12/27, Mike Sheldon :
> >> >> It'd appear that store authentication isn't working, as it's
> >> >> attempting
> >> >> to load the Sign In page, which then fails with the following errors:
> >> >>
> >> >> [W] unknown:383 - file:///usr/share/store-client/main.qml:383:9: Type
> >> >> SignInPage unavailable
> >> >> SignInPage {
> >> >> ^
> >> >> [W] unknown:147 -
> >> >> file:///usr/share/store-client/pages/SignInPage.qml:147:13: Cannot
> >> >> assign to non-existent property "onLegalDocumentsAccepted"
> >> >> onLegalDocumentsAccepted: {
> >> >>
> >> >> If these are commented out in the SignInPage.qml it loads the store,
> >> >> but
> >> >> insists there aren't any accounts active. If you then try to sign in
> >> >> it
> >> >> complains that there's already an account set up on the device.
> >> >>
> >> >> So my guess would be that we just have to wait for Jolla store auth
> to
> >> >> be fixed (presumably the authentication server has died under the
> >> >> load).
> >> >>
> >> >> Cheers,
> >> >> Mike.
> >> >>
> >> >> On Fri, 2013-12-27 at 17:13 +0200, Kalle Lammenoja wrote:
> >> >>> Yah, the download for os update started, but was stuck, so i
> >> >>> rebooted,
> >> >>> and now store crashes when i launch it :/
> >> >>>
> >> >>>
> >> >>> 2013/12/27 Luca Donaggio
> >> >>> I have exactly the same problem as Henry! First I got the
> >> >>> Jolla app updates (not working as they probably depends from
> >> >>> SailfishOS update) and now cannot download OS update.
> >> >>>
> >> >>>
> >> >>> Could it be that all the sailors out there are trying to
> >> >>> download the update at the same time? :-)
> >> >>>
> >> >>>
> >> >>>
> >> >>> On Fri, Dec 27, 2013 at 4:07 PM, Henry Kwong
> >> >>> wrote:
> >> >>> I am currently on 1.0.1.12 but it is currently
> saying
> >> >>> the update is to 1.0.1.10 "Version
> >> >>> 1.0.1-10.11.10.jolla" and not 1.0.2.5 - doesnt sound
> >> >>> right. The download is currently not working (it
> >> >>> seems
> >> >>> to have stopped after
Re: [SailfishDevel] [Update] Changelog for SailfishOS update 2 (1.0.2.5)
I have exactly the same problem as Henry! First I got the Jolla app updates (not working as they probably depends from SailfishOS update) and now cannot download OS update. Could it be that all the sailors out there are trying to download the update at the same time? :-) On Fri, Dec 27, 2013 at 4:07 PM, Henry Kwong wrote: > I am currently on 1.0.1.12 but it is currently saying the update is to > 1.0.1.10 "Version 1.0.1-10.11.10.jolla" and not 1.0.2.5 - doesnt sound > right. The download is currently not working (it seems to have stopped > after less than 10% download) > > I also have the same problem Kimmo mentioned with the 8 updates and > related install errors. I had suspected that the app updates require > 1.0.2.5 which is the reason the app-updates failed - but now it appears I > cannot verify if that is true or not. > > Help! How can I update the system to 1.0.2.5? > > > > - Original Message - > From: "Kimmo Lindholm" > To: "Sailfish OS Developers" > Sent: Saturday, 28 December, 2013 1:43:29 AM > Subject: Re: [SailfishDevel] [Update] Changelog for SailfishOS update 2 > (1.0.2.5) > > And store is completely stuck > I can see 8 updates to jolla-* apps, but it gives error if trying to > install. > > For some reason i first see app updates in store, but not yet the system > update. > > Is this intention or a bug in update distribution system? > Aren't the app's updated anyway when the system is updated? > > -kimmo > > >we're releasing update2 today. The changelog can be found (and commented > >on) here: > > > > > https://together.jolla.com/question/3612/release-notes-software-update-2-1025/ > ___ > SailfishOS.org Devel mailing list > ___ > SailfishOS.org Devel mailing list > -- Luca Donaggio ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Bluetooth headset/carkit issue (and clock related feedback)
On Tue, Dec 17, 2013 at 10:59 AM, Henry Kwong wrote: > Hi, > > Have been using the Jolla more and found a big problem with the bluetooth > software (for a car kit which seems to act as a headset). > > 1. The bluetooth connects well only on the first time, after a > disconnection and reconnection, the phone says it is connected but audio is > not routed to BT. A phone reboot is needed to resolve this. > > 2. After connecting to BT and then disconnection, audio is no longer > routed to the speaker during a call (the hold-phone-to-head way), but > pressing the loud-speaker button (so it would be on handsfree mode) is ok. > Switching off the loud-speaker results in no audio again. Phone reboot is > needed to resolve. > > I can confirm this very same behaviour on 1.0.1.12 too. Switching on and off the loud-speaker button sometimes is sufficient - no reboot is needed. -- Luca Donaggio ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] A new Jolla phone user - after 2 days of use
Is there a way to be notified of incoming mails in any folder (I'm using IMAP)? Actually it seems to me that it monitors Inbox folder only. With my N9 I used to mark some folders as fovourites and I got notifications for new mails in all of them: anything like that? On Tue, Dec 17, 2013 at 2:51 PM, Gianguido Sorà wrote: > Can you give us some details about battery life? > How many battery cycles you did? > Il 17/dic/2013 14:48 "mourik jan heupink" ha > scritto: > > My list of questions/issues: >> >> - there doesn't seem to be a way to interact with facebook / twitter, >> even though I have added those accounts. (or am I missing something..?) >> >> - on my N9 I could swipe to the right/left to get to the 'running apps' >> screen. That doesn't seem to work anymore. >> >> - And yes: I too miss N9 swype to enter text. I hope we'll see that >> back..! >> >> - I'd like to see a dutch T9/swype dictionary, for me the interface >> language could stay english only >> >> - Caldav! Without it, jolla can not become my primary daily phone. (i >> depend on various caldav calendars) >> >> For the rest: great! Anxiously awaiting future updates! >> >> MJ >> ___ >> SailfishOS.org Devel mailing list >> > > ___ > SailfishOS.org Devel mailing list > -- Luca Donaggio ___ SailfishOS.org Devel mailing list
