On Thu, Feb 13, 2014 at 11:29:47AM +0100, Filip Kłębczyk wrote:
[..]
> well if Harbour QA would be doing so well why the flashlight app
> with some hidden data gathering passed it (Artems little provocation
> :))?
Was Artems flash light gathering data?
Cheers,
On 13/02/14 12:29, Filip Kłębczyk wrote:
well if Harbour QA would be doing so well why the flashlight app with
some hidden data gathering passed it (Artems little provocation :))?
That shows that Jolla QA doesn't have to be better than community QA
in terms of user security and privacy.
Exactl
W dniu 13.02.2014 07:26, Kalle Vahlman pisze:
The other question here is will users prefer (or rather appreciate)
the Jolla-screened apps in Harbour over the user-screened apps from
OpenRepos.
And again, what could be a better argument about allowing a certain
API in Harbour than a handful of f
On 13/02/14 08:26, Kalle Vahlman wrote:
The other question here is will users prefer (or rather appreciate)
the Jolla-screened apps in Harbour over the user-screened apps from
OpenRepos.
We actually know the answer - it's not like we didn't have precedents
for "techie-device with both company
2014-02-12 Filip Kłębczyk :
> W dniu 12.02.2014 14:06, Attila Csipa pisze:
>
>> My personal advice is - don't overthink it. The bottom line/driver is
>> the user experience.
>
>
> Excellent post! The result was easy the predict - developers start to prefer
> OpenRepos than Harbour.
The other quest
W dniu 12.02.2014 14:06, Attila Csipa pisze:
My personal advice is - don't overthink it. The bottom line/driver is
the user experience.
Excellent post! The result was easy the predict - developers start to
prefer OpenRepos than Harbour. Someone really overthinked the whole
allowed API/libs st
Attila, you are totally right (in my opinion at least). Can you please post
your opinion to the together thread so that those of us who don't read mailing
lists can find it too? :)
On Wed Feb 12 2014 14:06:16 GMT+0100 (CET), Attila Csipa wrote:
>On 12/02/14 12:36, Timur Kristóf wrote:
>>
>> I p
On 12/02/14 12:36, Timur Kristóf wrote:
I posted the stuff to together so we can continue the discussion online:
https://together.jolla.com/question/27052/roundtable-discussion-jolla-harbour-apis/
My personal advice is - don't overthink it. The bottom line/driver is
the user experience.
It
We talked about this at the FOSDEM community roundtable. While no specific
solution was chosen, several alternatives and points of consideration came
up.
I posted the stuff to together so we can continue the discussion online:
https://together.jolla.com/question/27052/roundtable-discussion-jolla-h
On 09/02/14 14:52, David Greaves wrote:
On 09/02/14 11:28, Putze Sven wrote:
As pointed out from others, it's not simply done with the Qt documentation.
The Sailfish OS is built upon many libraries, frameworks and layers. But
which one is to use?
Qt.
Seriously. You asked for "an API". Jolla su
On 09/02/14 11:28, Putze Sven wrote:
> Hi,
>
> On 03.02.2014, at 16:58, David Greaves wrote:
>
>> On 03/02/14 15:29, Putze Sven wrote:
>>> What does a developer need to write quality apps? An API and a
>>> documentation of such.
>>>
>>> So far there is a quite limited API available and therefor
Hi,
2014-02-03 16:29, Putze Sven skrev:
What does a developer need to write quality apps?
An API and a documentation of such.
I would like to add "best practices" and "experience sharing", which is
exactly what StackOverflow provides me as a developer in other projects.
In my opinion is a pl
Hi,
On 03.02.2014, at 16:58, David Greaves wrote:
> On 03/02/14 15:29, Putze Sven wrote:
>> Hi there,
>>
>> during Fosdem I spoke to some people about this, even to Carsten Munk from
>> Jolla itself (not in the depth and detail of this mail, I must admit) and he
>> suggested to write this in th
+11
From: Luciano Montanaro
Date: 2014-02-04 01:10
To: Sailfish OS Developers
CC: David Greaves
Subject: Re: [SailfishDevel] When does Jolla give us an API?
Hi everybody,
I too find documentation a bit missing...
But it is not much about APIs, but system level documentation.
Qt
Hi everybody,
I too find documentation a bit missing...
But it is not much about APIs, but system level documentation.
Qt documentation is good, at least for the parts that are still
actively maintained.
But SailfishOS uses Qt, on top of wayland, systemd, pulse,gstreamer
and telepathy, and a bunc
Hi all
my experience is that are a vast amount of apis out there: There is
all the Qt stuff, the Qt add-ons, Nemo packages, and lower-level stuff
like telepathy and GST. The problem is not the lack of APIs, but the
choice of APIs. Which is the best one to use?.
Then if you hit on a likely
On 03/02/14 15:29, Putze Sven wrote:
> Hi there,
>
> during Fosdem I spoke to some people about this, even to Carsten Munk from
> Jolla itself (not in the depth and detail of this mail, I must admit) and he
> suggested to write this in the mailing list, so those of Jolla who should be
> concerned
Hi there,
during Fosdem I spoke to some people about this, even to Carsten Munk from
Jolla itself (not in the depth and detail of this mail, I must admit) and he
suggested to write this in the mailing list, so those of Jolla who should be
concerned have a chance to answer this question and I re
18 matches
Mail list logo
