elementary-dev-community team mailing list archive

[Cassidy James <cassidy@xxxxxxxxxxxxxxxx>]

I don't think we want any code in the HIG. As I said earlier, it's a set of
guidelines for design, not developer documentation for implementation. Code
would be great in the developer guide which we're working on. :)
On Apr 7, 2013 9:42 AM, "Nishant Agrwal" <nishantagrwal12993@xxxxxxxxx>
wrote:

> Should the example code be in the HIG or the granite doocuentation? Maybe
> we could link to the API reference for our own wigdets, and demonstrate
> techniques like padding and background tasks in the HIG itself?
>
> On Sun, Apr 7, 2013 at 6:03 PM, Sergey Shnatsel Davidoff <
> sergey@xxxxxxxxxxxxxxxx> wrote:
>
> Hey guys,
>
> Our HIG feels a little abstract right now. It communicates the ideals but
> gives little idea about how to implement the recommendations.
>
> I thought it would be cool to include example code that implements the
> recommendations in Vala/GTK/Granite. For example it's hard for me to get
> all the padding right in
> http://elementaryos.org/docs/human-interface-guidelines/ui-toolkit-elements/windows/dialogsor implement proper handling of background tasks (btw, are we updating the
> relevant HIG article or not?). A side-by-side layout where you can see the
> recommendations AND example code that implements them would be great IMO.
>
> Thoughts?
>
> --
> Sergey "Shnatsel" Davidoff
> OS architect @ elementary
>
>
> --
> Mailing list: https://launchpad.net/~elementary-dev-community
> Post to     : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~elementary-dev-community
> More help   : https://help.launchpad.net/ListHelp
>
>