>> I'll use this as an opportunity to mention that the "Components Gallery" 
>> application which comes pre-installed ...
Yep, That gallery-demo I run on the phone to find out how things work and look, 
and then by trial-and-error finally reach the spectacular UX of my own app.
But written documentation (which Silica Reference does fulfill ok'ish) around 
clear code sample (not always true for Silica Reference) and screenshot would 
be - astonishing.

>> ah, sorry, understood the topic in wrong way :)  
I did wrote topic while my 1st cup of coffee was still warm.

>> And it could be nice to discuss Silica API docs for next SFOS meeting, what 
>> do you think ? Will add it in the agenda. 
Yes please

-kimmo


-----Original Message-----
From: devel-boun...@lists.sailfishos.org 
[mailto:devel-boun...@lists.sailfishos.org] On Behalf Of Juha Kallioinen
Sent: 23. toukokuuta 2014 13:18
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] Screenshots in silica reference

On 23.05.2014 08:21, Kimmo Lindholm wrote:
> Hi,
>
> I so would like to see screenshots in silica reference.
>
> Like there is on "common pitfails" -page.
>
> -kimmo

I'll use this as an opportunity to mention that the "Components Gallery" 
application which comes pre-installed in the SDK emulator has 
interactive examples of the Silica components.

The Components Gallery can also be built as a project in Qt Creator and 
it can be found from the Qt Creator Welcome page/Examples tab/Sailfish 
Silica Component. If you're not using Qt Creator, then the project 
sources can be found from SDK installdir/examples/componentgallery.

This is not discrediting the idea of having screenshots in the Silica 
reference page.

Best regards,
  Juha

_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Reply via email to