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, Jan 6, 2014 at 2:16 AM, Martin Jones <martin.jo...@jolla.com> 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. > The busy property of PullDownMenu is documented, but the docs have not > been updated in the SDK. > OpacityRampEffect has been reviewed for public use, but is not yet > documented. We’ll do this asap. > > Best Regards, > Martin. > > > On 3 Jan 2014, at 6:58 am, Luciano Montanaro <mikel...@gmail.com> wrote: > > > 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 > > > > * OpacityRampEffect for my coverpage > > * the busy property of the PullDownMenu while fetching status updates > > * possibly the GlassItem as an indicator of the train delay > > > > Since I would like for my application to eventually be distributed > > through the Harbour, I would like to know if it is OK to do so. > > > > Best regards, > > Luciano > > > > -- > > 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 > > _______________________________________________ > SailfishOS.org Devel mailing list >
_______________________________________________ SailfishOS.org Devel mailing list
