Emeus - Constraint-based layout manager for GTK+
What is Emeus?
What's the difference between Emeus and GTK+'s layout managers?
GTK+ has two different sorts of layout managers:
- the boxes-inside-boxes model, represented by GtkBox and which is the preferred layout management mechanism
- the fixed positioning and sizing model, using the GtkFixed and the GtkLayout containers
The first model works really well in ensuring that UIs are responsive to size changes, by avoiding pixel-perfect positioning on the screen, as well as ensuring that changing the font size or margins and paddings do not break the user interface; its main down side is that it requires accurate, and often verbose packing of widgets inside boxes, inside other boxes.
The second model allows a more efficient way to construct a user interface, at the major costs of either "freezing" it, or requiring constant recalculations of the relative position and size of each UI element.
Emeus provides a third layout management policy, based on constraints; each UI element binds one of more of its attributes — like its width, or its position — to other UI elements, in a way that is more natural to describe from a UI building perspective, and hopefully more efficient that stacking piles of boxes one inside another.
EmeusLayoutConstraint is a GtkContainer that can
support multiple children; each child, in turn, is associated to one or more
EmeusConstraint instances. Each constraint is the expression of a simple
item1.attr1 = item2.attr2 × multiplier + constant
item1is the target widget, that is the widget we want to constraint; if unset, the target will be the layout itself
attr1is an attribute of the target widget, like
end, that we want to constraint
item2is the source widget, that is the widget that provides the value of the constraint; if unset, the source will be the layout itself
attr2is an attribute of the source widget that provides the value of the constraint
multiplieris a multiplication factor, expressed as a floating point value
constantis an additional constant factor, expressed as a floating point value
Using both notations, then, we can construct user interfaces like:
+-------------------------------------------+ | [ button 1 ] [ button 2 ] [ button 3] | +-------------------------------------------+
By expressing the constraints between the UI elements. For instance, we can
button2 within its parent and give it a minimum width of 250
button2.width >= 250 button2.centerX = parent.centerX button2.centerY = parent.centerY
Then, we can tie
button2, and ensure that the
width and height of all three buttons are the same:
button1.end = button2.start - 8 button1.width = button2.width button1.height = button2.height button3.start = button2.end + 8 button3.width = button2.width button3.height = button2.height
EmeusConstraintLayout widget will attempt to resolve all the
constraints, and lay out its children according to them.
- Install meson
- Install ninja
- Create a build directory:
$ mkdir _build && cd _build
- Run meson:
- Run ninja:
$ ninja test
# ninja install
The API reference for Emeus is available online.
Emeus is released under the terms of the GNU Lesser General Public License, either version 2.1 or, at your option, any later version.
The Cassowary simplex solving algorithm implementation is largely inspired by the equivalent implementations written in various other language, including:
- Cassowary — the original C++ implementation, released under the terms of the GNU Lesser General Public License, version 2.1 or later
- Cassowary — Python implementation, released under the terms of the BSD 3-clause license
You can check on the Overconstrained website for additional Cassowary implementations in various languages.