QML style guide

[Ivan Čukić]

+1

I've been using a template found somewhere on the Qt-tubes, which goes
like this

> property declarations
> signal declarations
> JavaScript functions
> object properties
> child objects
> states
> transitions

I'd argue that property and signal declarations should be moved to the
top - it is kinda a quick api overview for the users of the component.
I'd even put the meant-to-be-public functions over there, again for
api overview.

For the rest, I agree with the geometry properties -> data models ->
functions... ordering.


-- 
Cheerio,
Ivan

--
While you were hanging yourself on someone else's words
Dying to believe in what you heard
I was staring straight into the shining sun