At Google IO 2016 Google introduced a brand new android developer Malaysia layout named ConstraintLayout. Regardless of the initial release being labelled being an Alpha release, it’s really pretty stable (having a couple of caveats). Within this number of articles we’ll check out this new layout-kid on the market and check out and obtain some information in terms best for doing things.
Constraint propertiesBefore we start it’s worth making some distinctions: ConstraintLayout is totally outside of the brand new layout editor. The brand new layout editor isn’t just designed to utilize ConstraintLayout, additionally, it utilizes other layout types too. Furthermore the brand new layout editor is really not only a layout editor – additionally, it enables the visual editing of menu sources in addition to designs so I’ll really think of it as the visual editor as opposed to the layout editor. There has been previous attempts at supplying visual layout editing which, although well intentioned, happen to be somewhat missing within their implementation – it normally won’t play nicely with custom Sights, for instance.
It had been these training learned from all of these previous attempts at visual layout editors the new editor continues to be re-written in the ground-up – also it shows – android developer Malaysia already a lot more able to handle custom Sights so long as you retain the constructors pretty neat and take advantage of View#isInEditMode() to make sure that it doesn’t attempt to do an excessive amount of when it’s getting used in the visual editor.So although ConstraintLayout is dissimilar to the editor, the 2 do go rather hands-in-hands and ConstraintLayout continues to be made to be crafted with the visual editor instead of hands-crafted XML. I spoke to a few Googlers who’d been having fun with ConstraintLayout and both mentioned they wouldn’t even consider hands-crafting XML due to the fact the visual editor am good.