QML style guide

[Marco Martin]

On Monday 29 October 2012, Aaron J. Seigo wrote:
> On Monday, October 29, 2012 21:52:38 Ivan Čukić wrote:
> > > property declarations
> > > signal declarations
> > > JavaScript functions
> > > object properties
> > > child objects
> > > states
> > > transitions
> 
> other than object properties following functions, this looks nice. the
> example on that wiki page does not have signals, states or transitions
> which do indeed all need to be added.
> 
> i don't like objects properties following functions for 2 "imho" reasons:
> 
> * it's nicer to see an overview of all properties at once
> * otherwise you get JS functions which are typically blocks of code, then
> properties which are usually one-liners, then child objects which are
> blocks of code again. this back-and-forth of styles is visually messy.

agree for functions before object properties
but still before child objects, that can be more seen as the private: section


-- 
Marco Martin