[SailfishDevel] Repository Wishlist

[Erlend Böe]

Dear David,

As a user I would like to have a repo with the following characteristics:
* Guarantee that apps do not break my device by installing incompatible 
versions of libraries.
* App Ratings, and download numbers, and ability to sort the list of apps based 
on these.
* App comments
* Easy search functionality, categories.
* A clear statement that applications that “snoop on the user” are not welcome, 
except for sending statistics back to the repo itself.
* If possible, a guarantee that the application has been audited to not “phone 
home”. One possible option would be that applications that use the internet 
could voluntarily have a “whitelist” of sites that it will connect to. That 
will make me trust the application more!


As a developer, I would like to have a repro with the following characteristics
* Clear guidelines that show what is allowed, and how to package the apps.
* Example projects that are “ready out of the box”.
* Automated checks that I can run before I upload the package, so that most 
errors are caught before upload.
* Clear, timely feedback if my application is not compliant
* An analytics library that I can use in my application, that would send usage 
statistics to the repo.  All other “snooping” on the user would be disallowed.
* Statistics about downloads, analytics, etc

Regards,
Erlend

On 05.02.2014, at 16:00, David Greaves  wrote:

> On 04/02/14 07:40, "Thomas B. Rücker" wrote:
>> My question has been lingering for a while. (
>> https://together.jolla.com/question/13605/visible-open-source-app-community-supported-by-jolla/
>> )
>> 
>> But during FOSDEM we had a Sailfish/Jolla Community Round-Table (
>> https://together.jolla.com/question/11303/are-you-going-to-fosdem-2014-irl-floss-meeting-in-belgium/?answer=13864#post-id-13864
>> ). This topic was brought up and seems Sailors are committed to address
>> this with pushing forward towards a clean open source app repository
>> with community QA and easy on-device access after enabling developer mode.
> 
> That's my personal goal, yes.
> 
> For those who don't know, I run the infra and OBS for Mer - I used to run the
> community OBS and other infra for MeeGo too. I am a sailor - but today I'm
> mailing as a community guy.
> 
> I setup Chum as a place to build Jolla apps on an OBS. It just works. There is
> no fancy storefront or BOSS integration. We need that.
> 
> I'd like to see some public docs on the Chum rules and governance so that we 
> can
> reasonably expect Jolla to trust us to do a professional job. I know that they
> worry about reputation and customer experience. So do I.
> 
> I don't think we need full automation of the checks yet - but I do think we 
> can
> clearly state the boundaries: open source only; auditability; community QA...
> 
> I'd like to see what our target is from a user perspective ... eg how do we 
> make
> sure users can upgrade their devices. It's a technically difficult problem. We
> may well need to ask Jolla for hooks into SailfishOS ... but luckily we may 
> also
> be able to write those hooks in Mer/Nemo and have Jolla just get them.
> 
> I also recall that community QA was not terribly effective - I think this 
> needs
> adressing.
> 
> I used "Chum" as the repo title (it's the bloody fish guts you use to attract
> sharks!) - I'm not sure it's a good name but there are plenty of attacks :)
> 
>> This would provide something like Maemo Extras and would be community
>> QA'd to ensure the apps don't pose major problems when installed. On the
>> other hand it would provide an easy middle ground for apps that don't
>> fit into harbour for various reasons (API calls, dependencies, etc.).
> 
> Yes - I'd like to explore how we can add one or more library areas to devices
> for sets of shared libraries. Eg I use bullet physics engine in my 3D Dice 
> game
> - I don't want to have to ship it. But how do we cope when bullet v3 comes 
> out?
> 
>> It will be backed by an OBS project on Mer community OBS, which has
>> Sailfish targets. OBS has come a very long way since we've seen it
>> first. I've personally had several apps build out of the box by just
>> _clicking_:
>> * create package
>> * source provision through tar_git
>> If the app builds on a clean SDK, then it's highly likely to build out
>> of the box also on OBS.
> 
> Good. We need more docs though.
> 
>> You may now say "what about openrepos?". They have chosen to be a site
>> for one-click RPM hosting repositories with no QA. Despite their best
>> efforts this approach has led to significant problems. Also it does
>> binary only uploads and thus non-free/closed applications and no
>> traceable chain from source to binary.
>> That said, if the openrepos client (warehouse) passes community QA it
>> will for sure be included in the community repository. Thus allowing
>> users to install it easily, if they so wish. We're not hostile towards
>> it, it just doesn't offer the level of trust to be a viable avenue for a
>> default community r

[SailfishDevel] Silica issue on coverpage: Opacity value is ignored in CoverBackground if a label is truncated with fading

[Tigre-Bleu]

Hi guys,

If in a cover, a label is truncated with truncationMode: TruncationMode.Fade 
then the opacity value is ignored.

For code example and screenshot, see the following bug report: 
https://github.com/Buschtrommel/ocNews/issues/27#issuecomment-34267086

I think it is an issue with Silica component. I would expect opacity to be 
taken into account and the fading to opacity=0 still applied at the truncation 
location.

Regards,

Antoine


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] QtWebKit QWebView

[Andrey Kozhevnikov]

most of extra packages are not preinstalled by default. you should 
install development packages using SDK Control Center, and add 
dependencies to your yaml/spec for installing all required packages on 
target devices.


On 06.02.2014 01:52, Samuli Silvius wrote:

Hi,

So how to find what Qxxx classes are supported and what not?
E.g. this porting guide suggest to use
QT += webkitwidgets
http://www.jollausers.com/2013/08/harmattan2sailfish/

But if I try that Jolla SDK just says
 error: Unknown module(s) in QT: webkitwidgets

Is there any way to use "QWebPage" to be able get hands on to web 
pages DOM? I don't need to show webpage or edit it just parse and find 
something.
If it's not possible, then I guess have to try proposed 
QXmlStreamReader, it's more low level I guess?


Br
-Samuli


2014-01-28 Aaron McCarthy >:


On Fri, 24 Jan 2014 22:40:43 Hannes Rantzsch wrote:
> no, unfortunately I didn't get it working. Had no time for further
> fiddling around yet.
> Yeah, XMLHttpRequest looked nice to me too first. But the page I
want
> does not offer anything for that. Just plain html.
>
> I would still like to get QWebFrame working, as Aaron suggested.
Maybe
> now someone has an idea what kind of configurations are needed
to get it in?

Unfortunately QWebFrame seems to be part of Qt WebKit Widgets as
well. I
suggest looking at what functionality is provided by Qt WebKit and
see if that
meets you needs. Depending on the complexity of the HTML that you
want to
parse and what you want to extract out of it, it is possible to use
QXmlStreamReader perhaps with some pre-processing.

Cheers,

--
Aaron McCarthy
___
SailfishOS.org Devel mailing list




___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] QtWebKit QWebView

[Samuli Silvius]

Hi,

So how to find what Qxxx classes are supported and what not?
E.g. this porting guide suggest to use

QT += webkitwidgets

http://www.jollausers.com/2013/08/harmattan2sailfish/

But if I try that Jolla SDK just says
 error: Unknown module(s) in QT: webkitwidgets

Is there any way to use "QWebPage" to be able get hands on to web pages
DOM? I don't need to show webpage or edit it just parse and find something.
If it's not possible, then I guess have to try proposed QXmlStreamReader,
it's more low level I guess?

Br
-Samuli


2014-01-28 Aaron McCarthy :

> On Fri, 24 Jan 2014 22:40:43 Hannes Rantzsch wrote:
> > no, unfortunately I didn't get it working. Had no time for further
> > fiddling around yet.
> > Yeah, XMLHttpRequest looked nice to me too first. But the page I want
> > does not offer anything for that. Just plain html.
> >
> > I would still like to get QWebFrame working, as Aaron suggested. Maybe
> > now someone has an idea what kind of configurations are needed to get it
> in?
>
> Unfortunately QWebFrame seems to be part of Qt WebKit Widgets as well. I
> suggest looking at what functionality is provided by Qt WebKit and see if
> that
> meets you needs. Depending on the complexity of the HTML that you want to
> parse and what you want to extract out of it, it is possible to use
> QXmlStreamReader perhaps with some pre-processing.
>
> Cheers,
>
> --
> Aaron McCarthy
> ___
> SailfishOS.org Devel mailing list
>
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Preventing deep sleep for a few seconds?

[Thomas Tanghus]

On Wednesday 05 February 2014 08:16:32 Valerio Valerio wrote:
> Hi,
> 
> On 05/02/14 02:58, Thomas Tanghus wrote:
> > On Monday 03 February 2014 22:58:42 Ove Kåven wrote:
> >> But for scheduled wakeups (say I want the next synchronization to occur
> >> after 6 hours), I suppose the best option is to use "timed"?
> > 
> > I made a QML plugin including libiphb for that, and it did pass the
> > harbour
> > master ;)
> > 
> > https://github.com/tanghus/kitchen-timer-qml/tree/master/src/insomniac
> 
> Didn't checked your code carefully but this is probably not sufficient,
> if the device enters late suspend the timers will stop unless you use
> the keepalive apis (unfortunately not suited for harbour yet):
> https://github.com/nemomobile/nemo-keepalive

As I use it in the kitchen-timer app any "normal" QML timers are stopped when 
the app is no longer visible, and the Insomniac timer (using the libiphb 
included) is set to wake up a few seconds before the timeout, restart timers 
and adjust the UI.

Works flawlessly (in my tests) for waking up from "deep sleep".

-- 
Best regards / Med venlig hilsen

Thomas Tanghus
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] FOSDEM Community follow-up - open source app community

[David Greaves]

On 04/02/14 07:40, "Thomas B. Rücker" wrote:
> My question has been lingering for a while. (
> https://together.jolla.com/question/13605/visible-open-source-app-community-supported-by-jolla/
> )
> 
> But during FOSDEM we had a Sailfish/Jolla Community Round-Table (
> https://together.jolla.com/question/11303/are-you-going-to-fosdem-2014-irl-floss-meeting-in-belgium/?answer=13864#post-id-13864
> ). This topic was brought up and seems Sailors are committed to address
> this with pushing forward towards a clean open source app repository
> with community QA and easy on-device access after enabling developer mode.

That's my personal goal, yes.

For those who don't know, I run the infra and OBS for Mer - I used to run the
community OBS and other infra for MeeGo too. I am a sailor - but today I'm
mailing as a community guy.

I setup Chum as a place to build Jolla apps on an OBS. It just works. There is
no fancy storefront or BOSS integration. We need that.

I'd like to see some public docs on the Chum rules and governance so that we can
reasonably expect Jolla to trust us to do a professional job. I know that they
worry about reputation and customer experience. So do I.

I don't think we need full automation of the checks yet - but I do think we can
clearly state the boundaries: open source only; auditability; community QA...

I'd like to see what our target is from a user perspective ... eg how do we make
sure users can upgrade their devices. It's a technically difficult problem. We
may well need to ask Jolla for hooks into SailfishOS ... but luckily we may also
be able to write those hooks in Mer/Nemo and have Jolla just get them.

I also recall that community QA was not terribly effective - I think this needs
adressing.

I used "Chum" as the repo title (it's the bloody fish guts you use to attract
sharks!) - I'm not sure it's a good name but there are plenty of attacks :)

> This would provide something like Maemo Extras and would be community
> QA'd to ensure the apps don't pose major problems when installed. On the
> other hand it would provide an easy middle ground for apps that don't
> fit into harbour for various reasons (API calls, dependencies, etc.).

Yes - I'd like to explore how we can add one or more library areas to devices
for sets of shared libraries. Eg I use bullet physics engine in my 3D Dice game
- I don't want to have to ship it. But how do we cope when bullet v3 comes out?

> It will be backed by an OBS project on Mer community OBS, which has
> Sailfish targets. OBS has come a very long way since we've seen it
> first. I've personally had several apps build out of the box by just
> _clicking_:
> * create package
> * source provision through tar_git
> If the app builds on a clean SDK, then it's highly likely to build out
> of the box also on OBS.

Good. We need more docs though.

> You may now say "what about openrepos?". They have chosen to be a site
> for one-click RPM hosting repositories with no QA. Despite their best
> efforts this approach has led to significant problems. Also it does
> binary only uploads and thus non-free/closed applications and no
> traceable chain from source to binary.
> That said, if the openrepos client (warehouse) passes community QA it
> will for sure be included in the community repository. Thus allowing
> users to install it easily, if they so wish. We're not hostile towards
> it, it just doesn't offer the level of trust to be a viable avenue for a
> default community repository.

I don't mind openrepos - there are plenty of places where users can go on the
internet that expose them to greater or lesser degrees of risk. It's their
choice. I would choose to be more restrictive than openrepos on what's allowed
into the community store. I also think we have a slighly different focus -
openrepos is literally a free-for-all. I hope Chum (or whatever) will have more
of a "reliable quality for the user" goal.

If/when warehouse gets onto community store I would like to be clear about what
it provides as there would be a sense of it meeting the users expectation of
quality/safety.

> This is a PERSONAL summary of MY recollection of the FOSDEM discussion
> on this topic. I hope that Jolla will now finally back this up and we
> will see Sailors working towards this.

Still community hat! I am of the opinion that Jolla do a lot for the community
simply in how they operate. I think much of this is our job. We need to clearly
ask for things and justify why they should be granted.

Eg I think we should ask for a similar role as maemo extras - but we need to
justify why we can be trusted to essentially grant root privileges to any app
developer on any users jolla device.

As for sailors working on this - I think we may like Jolla to grant them some
company time to respond to these feature requests - but mainly how much time
they spend on community things is down to them. Some sailors love openrepos
approach; some love Mer OBS/Chum approach :)

> For those who already wan

Re: [SailfishDevel] how to get qml debug output to file

[Robin Burchell]

On 04 Feb 2014, at 22:37, Tero Siironen  wrote:
> Andrey Kozhevnikov  kirjoitti 4.2.2014 kello 23.14:
> 
>> This is messages handler i'm using in my projects:
> 
> 
> This doesn’t seem to make a difference for me, the log file still contains 
> only c++ side debug prints, qml prints (like console.log()) are not handled 
> with messagehandler.
> 
> Actually I found out that even if set in pro-file:
> DEFINES +=QT_NO_DEBUG_OUTPUT
> DEFINES +=QT_NO_WARNING_OUTPUT
> 
> I still get qml debug prints printed out to console, so it seems that those 
> prints from qml are not handled via normal debug handling at all?
> 
> I would like to get no debug printing at all, or then just to file.

DEFINES in qmake adds additional defines (-D) to the cflags used to build C++ 
affect code compiled with them. QtDeclarative was not compiled with these 
defines, so your adding them won’t affect console.log (whose C++ implementation 
lives inside QtDeclarative).

If you don’t want debug prints, you need to install a message handler (you say 
you’ve tried this and it doesn’t work, I can’t answer why that would be the 
case, it should work, as it uses the same infrastructure).

BR,
Robin
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Sideload Native App To Sailfish

[Reto Zingg]

Hi,

On 05.02.2014 09:18, christopher.l...@thurweb.ch wrote:

No rooting (or jailbreaking) pr verboten-hacks required.

Just put the phone into developer mode. In theory any user can do this
with a few clicks.

Then you can install anything that will run.

However this route does imply that the user has some idea of what they
are doing, just a a user installing on a Linux desktop will need some
idea as well. It might not be a route for a stereotypical grandma.


Developer mode is not for everybody, that is clear. And the other 
suggested methods w/o developer mode will not work out of the box much 
longer as stressed out already earlier:


https://lists.sailfishos.org/pipermail/devel/2014-January/002901.html

As stressed out in the same mail, we work on it to make it possible to 
side load rpm's, if the user sets up the device to allow untrusted 
sources (or how ever we are gonna call that setting).


br
Reto



Apologies in a advance to all the
non-stereotypical-Linux-savvy-Jolla-wielding-grandmas who are part of
this mailing list.



Grüsse

Chris

Zitat von "Network Nut" :


Hi All,



I have what I imagine to be a very common problem:



1.   There will be billions of people who own smartphones.

2.   I have a 100% native Linux C++ app that I would like a few of
those
billions of people to use. These are my future customers.

3.   I do not necessarily want to use an app store of any kind, if I
choose not to use any.

4.   I would like for my customers to decide, at their own
discretion,
whether to side-load my native app onto their smartphone by going to
my web
site, and not an app store.

5.   I would like to avoid having my customers call my
tech-support line
and listen on the phone for 30 minutes as one of my tech-support
representatives tells him/her how to root their phone so that they can
side-load my app.



In other words, I would like the same situation that exists now under the
desktop model, where anyone who owns a desktop computer has full
discretion
of what they do with their computer, without (significant)
restrictions from
the OS vendor.



I understand that Jolla allows 100% true native C++ apps, but I was
unable
to determine, with a quick search on the WWW, whether Jolla allows 100%
native C++ apps under the acquisition model above.



Can anyone clarify? Is it true that the owner of a Jolla smartphone
will be
able to determine for himself/herself whether to side-load a third-party
native application without jumping through hoops to bypass restrictions
created by the OS?



Regards,



-Nut






___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Preventing deep sleep for a few seconds?

[Valerio Valerio]

On 05/02/14 10:04, Ove Kåven wrote:

Den 05. feb. 2014 07:16, skrev Valerio Valerio:

Hi,

On 05/02/14 02:58, Thomas Tanghus wrote:

On Monday 03 February 2014 22:58:42 Ove Kåven wrote:
But for scheduled wakeups (say I want the next synchronization to 
occur

after 6 hours), I suppose the best option is to use "timed"?

I made a QML plugin including libiphb for that, and it did pass the
harbour
master ;)

https://github.com/tanghus/kitchen-timer-qml/tree/master/src/insomniac


Didn't checked your code carefully but this is probably not sufficient,
if the device enters late suspend the timers will stop unless you use
the keepalive apis (unfortunately not suited for harbour yet):
https://github.com/nemomobile/nemo-keepalive


But he does. From that README, it sounds like nemo-keepalive's 
PeriodicBackgroundProcessing is using libiphb, just like he is...


Not only, if you check the code it also pings MCE preventing the device 
to go into late suspend, at least for me libiphb alone was not sufficient.





Perhaps I could just use the nemo-keepalive API anyway since I'm not 
currently targeting harbour anyway because of its other restrictions.


There's also QML interface there in case you haven't noticed.

Best regards,

Valério


___
SailfishOS.org Devel mailing list


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Sideload Native App To Sailfish

[Janne Kokko]

And infact you don't even need Filemanager for that:

1) download an RPM using Jolla Browser
2) Open Jolla Store and keep it open in background
3) Go to Settings -> Transfers
4) Click the downloaded rpm file (nothing seems to happen)
5) Switch to Jolla Store and click "Install"

This method also works also without developer mode.

--
Janne

2014-02-05 A. Wickert :
> You don't need the developermode to install RPMs. You can install RPMs
> easily from the FileManager.
>
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Preventing deep sleep for a few seconds?

[Ove Kåven]

Den 05. feb. 2014 07:16, skrev Valerio Valerio:

Hi,

On 05/02/14 02:58, Thomas Tanghus wrote:

On Monday 03 February 2014 22:58:42 Ove Kåven wrote:

But for scheduled wakeups (say I want the next synchronization to occur
after 6 hours), I suppose the best option is to use "timed"?

I made a QML plugin including libiphb for that, and it did pass the
harbour
master ;)

https://github.com/tanghus/kitchen-timer-qml/tree/master/src/insomniac


Didn't checked your code carefully but this is probably not sufficient,
if the device enters late suspend the timers will stop unless you use
the keepalive apis (unfortunately not suited for harbour yet):
https://github.com/nemomobile/nemo-keepalive


But he does. From that README, it sounds like nemo-keepalive's 
PeriodicBackgroundProcessing is using libiphb, just like he is...


Perhaps I could just use the nemo-keepalive API anyway since I'm not 
currently targeting harbour anyway because of its other restrictions.


___
SailfishOS.org Devel mailing list