Yep, it seems to work according to samples in componentgallery project.
-Original Message-
I am using GlassItem in Framrekkari and that is in official Jolla store. So it
seems to be allowed. :)
Best greetings
Buschmann
Am Sonntag, 18. Mai 2014, 07:33:13 schrieb Kimmo Lindholm:
> Is t
I am using GlassItem in Framrekkari and that is in official Jolla store. So it
seems to be allowed. :)
Best greetings
Buschmann
Am Sonntag, 18. Mai 2014, 07:33:13 schrieb Kimmo Lindholm:
> Is the GlassItem still no-no ?
>
> On Monday 06 January 2014 01:16 Martin Jones wrote:
>
> > Hi,
> >
>
Is the GlassItem still no-no ?
On Monday 06 January 2014 01:16 Martin Jones wrote:
> Hi,
>
> As a general rule, if it’s not documented then it isn’t public API.
>
> The GlassItem API hasn’t been reviewed for public use. It will
> probably change and is not safe for use.
___
Any progress on the documentation of OpacityRampEffect ?
-kimmo
> On Mon, Jan 6, 2014 at 2:16 AM, Martin Jones wrote:
>>
...
>> OpacityRampEffect has been reviewed for public use, but is not yet
>> documented. We’ll do this asap.
___
SailfishOS.org
On Monday 06 January 2014 01:16 Martin Jones wrote:
> Hi,
>
> As a general rule, if it’s not documented then it isn’t public API.
>
> The GlassItem API hasn’t been reviewed for public use. It will probably
> change and is not safe for use.
So apps using GlassItem will be rejected from harbour?
Thank you for the answer, I can live with that for now.
Regards,
Luciano
On Tue, Jan 7, 2014 at 12:24 AM, Martin Jones wrote:
>
> On 6 Jan 2014, at 9:57 pm, Timur Kristóf wrote:
>
> Hi Martin,
>
> So, we're okay with using PullDownMenu::busy and OpacityRampEffect, but we
> should avoid GlassIte
On 6 Jan 2014, at 9:57 pm, Timur Kristóf
mailto:timur.kris...@gmail.com>> wrote:
Hi Martin,
So, we're okay with using PullDownMenu::busy and OpacityRampEffect, but we
should avoid GlassItem for the moment. Right?
Yes.
For OpacityRampEffect, use only the properties used in the silica componen
Hey Robin,
What is the recommended way to use those things in a Sailfish app right now?
Thanks,
Timur
Timur
On Mon, Jan 6, 2014 at 2:10 PM, Robin Burchell wrote:
> For things in Qt itself, keep an eye on Qt upstream. When they are part
> of an official Qt release (that is: stable API), the
For things in Qt itself, keep an eye on Qt upstream. When they are part of an
official Qt release (that is: stable API), then we can look at them when we
upgrade.
As far as I know, nobody has yet prioritised work on either of those, and
platform support is scarce, so I don’t see them happening
Hi Martin,
So, we're okay with using PullDownMenu::busy and OpacityRampEffect, but we
should avoid GlassItem for the moment. Right?
What about other APIs that are there but aren't allowed yet, such as
QtDocGallery and QtFeedback? When can we use those in harbour?
Thanks,
Timur
Timur
On Mon,
Hi,
As a general rule, if it’s not documented then it isn’t public API.
The GlassItem API hasn’t been reviewed for public use. It will probably change
and is not safe for use.
The busy property of PullDownMenu is documented, but the docs have not been
updated in the SDK.
OpacityRampEffect has b
They're not documented because they might not be ready for prime time
yet or their API might still change. So I'd be careful using them.
On 03.01.2014 12:26, Timur Kristóf wrote:
Hi Luciano,
My guess is that since those components are part of Silica and their
imports are allowed in the harbour
Hi Luciano,
My guess is that since those components are part of Silica and their
imports are allowed in the harbour, it is OK to use them. I don't know
their actual official status but I guess they are simply not documented
because of a mistake, not because they are disallowed.
Would be nice to h
I don't know if this has been addresed already, but...
In my application, I would like to use a few components that the
componentgallery is demoing, but that are not documented in the
reference documentation.
Is it OK to use everything that works there?
Specifically, I want to use
* OpacityRampE
14 matches
Mail list logo
