On Monday 29 October 2012, Aaron J. Seigo wrote: > i did spend some time considering why this happens ... and here's my guess > (though it is only that): one tends to start with and also change most > frequently the geometry properties (anchors, widths/heights, spacing, > margins) and so those "naturally" got promoted to the top. they are also > some of the most common things to find in items, so "id => geometry" is > just a very common pattern.
ok, since both make sense, i'm for the one that requires less adaptions of existing files > > > usually i tend to put onFooChanged immediately after the declaration of > > foo, has advantages and disadvantages, but i guess is mostly gettig used > > to > > tbh, this is one habit that really bugs me. due to the mix of property > definitions and blocks of code, it's very hard to get an overview of what > the properties actually are. worst of all, it ends up encouraging the mix > of other elements referenced by these onFoo methods in there too. running > across a Timer definition mixed in with properties QML is not entirely > uncommon, and i think it is probably due to this. good point, noted. -- Marco Martin _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel