But if there was an in-app-purchase system, it wouldn't be so bad :)
yes...
Having built-in IAP is a must if we want some monetization. And lack of it
would reduce attractivity of the platform toward developers...
2013/11/6 Marcin M. marmistrz...@gmail.com
It's not a pity when it comes
Ahoy,
thank you for all the interest in the Harbour. First of all a big apology for
for the problems that we are having here at Harbour - we faced some unexpected
issues due to a small storm that passed by and are working hard to resolve them.
We will keep you posted when you can dock again to
Hello everyone, I repeat the question
I have a problem with a component video I want to play video in MP4 format but,
unfortunately,
after compiling the code I get the message No decoder available for type
'video/x-h264' in SDK …”
In emulator I have uploaded all the codecs using command
Will be Emoji supported by Sailfish internally by Silica components at
real devices? Or we should start prepare hacks for components for custom
Emoji support?
___
SailfishOS.org Devel mailing list
Hi,
Have been away sometime. Installed the latest SDK: Qt5.1.
5.1 supports Qt Serial Port, but somehow not in the Sailfish version.
Any hints?
Thanks.
___
SailfishOS.org Devel mailing list
Well, the whole problem with repos and deps is not about the user side but
the server side ;) Maemo.org doesn't expose DiffIndex like Debian does but
normal Packages and Release (maybe compressed). DiffIndex would greatly
reduce download time.
About the storing list of apps on-device... Hmm... In
On 07-Nov-13 12:06, Marcin M. wrote:
Well, the whole problem with repos and deps is not about the user side
but the server side ;) Maemo.org doesn't expose DiffIndex like Debian
does but normal Packages and Release (maybe compressed). DiffIndex would
greatly reduce download time.
It's like the
The same question - those two seem to be a direct contradiction.
BTW another counterexample: On BB10 you can't even read the stdout log of
signed apps, making debuging of signed applications very difficult.
Dne 07.11.2013 21:09 napsal uživatel Attila Csipa:
On 07-Nov-13 01:42, Jonni Rainisto
Hi Ronni,
Thank you very much for your reply. The only thing that worries me is how
you wrote:
Currently Jolla Harbour only supports free applications. We are
working hard on adding copy protection and application payment
support in the future. More details will be published when
DRM has nothing to to do with with copy protection. DRM on mobile devices
usually means supporting DRM PlayReady (Microsoft) or Widevine L1 L2 L3 L4
(google). And we dont have those in Sailfish OS.
There is no Aegis on the system, and after you enable developer mode, you have
_true_ root
Attila wrote:
In the context of Will you support DRM? No in your FAQ, and
having an open, hackable device environment, please do elaborate.
I sincerely hope that Jolla has learned from the Aegis experience
and general success of copy-protection schemes on other
platforms.
When asking the
Ronni wrote:
copy protection library is just supposed to make cracking
and copying process hard enough so that most of the people
will just choose to use store for getting their rpm's. And
to give app developers easier ways to give some protection
their applications so direct .rpm file copy
On 07-Nov-13 13:40, Jonni Rainisto wrote:
DRM has nothing to to do with with copy protection.
Copy protection *is* one of the cornerstones of DRM (which, arguably, is
a lot broader term). Feel free to check wikipedia :)
Hopefully that answered your question.
Not quite :) What I'm
On 07-Nov-13 13:42, Michal Jerz wrote:
So it's like with door locks. Despite none of them being 100% proof to
unauthorized opening, somehow people continue to use them in their doors
rather than just having doors without any locks only because they're not
100% secure. They at least REDUCE abuse.
Hi Attila,
On Thu, Nov 07, 2013 at 03:03:21PM -0800, Attila Csipa wrote:
[...]
Hopefully that answered your question.
Not quite :) What I'm interested in is what *will* be there (or,
rather, what resources will it limit) as opposed to what is NOT
going to be there (whether not having Aegis
Hi,
my application which I am preparing for the store uses Qts Svg module.
Compilation in the SDK works fine since I added QT += svg to the
main .pro file. Deploying/running fails however, although I added -
Qt5Svg to the PkgConfigBR section in the .yaml file.
Error message when deploying by
On 07-Nov-13 15:51, Mohammed Hassan wrote:
Not quite :) What I'm interested in is what *will* be there (or,
rather, what resources will it limit) as opposed to what is NOT
going to be there (whether not having Aegis there is good, or bad,
depends on what you will have there instead is better or
Attila wrote:
Without serious research, I will contest that as wishful
thinking. [...]
If existing stores are anything to go by, the *ease* of
how easily one can legally get to your content (at the
micro-pricing levels) will, in effect, dwarf the impact
of any DRM scheme.
Well, as
On 07-Nov-13 17:31, Michal Jerz wrote:
Well, as Ronni wrote, using their copy-protection library is going to be
entirely OPTIONAL, so its existence should not hurt anyone
That will depend on what it actually does, and what kind of support it
requires from the system. At the most benign
From what I understand,
copy protection is going to be a service on Jolla devices (usable by
applications which like to do so),
but not completely necessary, ie an application can choose if to rely on it
or not.
Is this correct?
On Fri, Nov 8, 2013 at 2:37 AM, Attila Csipa q...@csipa.in.rs
That's good, but what I don't get in that case is... does that
coincidentally mean enable developer mode == disable copy protection?
It doesn't mean that. It will be lightweight, does not limit resources and
does not care what mode you are on. People will just have to wait for untill
its ready
21 matches
Mail list logo
