%gtkdocentities; ]> Migrating from Handy 0.0.x to Handy 1 3 Migrating from Handy 0.0.x to Handy 1Notes on migration to Handy 1. Handy 1 is a major new version of Handy that breaks both API and ABI compared to Handy 0.0.x. Thankfully, most of the changes are not hard to adapt to and there are a number of steps that you can take to prepare your Handy 0.0.x application for the switch to Handy 1. After that, there's a number of adjustments that you may have to do when you actually switch your application to build against Handy 1. The steps outlined in the following sections assume that your application is working with Handy 0.0.13, which is the final stable release of Handy 0.0.x. It includes all the necessary APIs and tools to help you port your application to Handy 1. If you are using an older version of Handy 0.0.x, you should first get your application to build and work with Handy 0.0.13. Static linking support has been removed, and so did the static build option. You must adapt you program to link to the library dynamically, using the package_subdir build option if needed. Over the years, a number of functions, and in some cases, entire widgets have been deprecated. These deprecations are clearly spelled out in the API reference, with hints about the recommended replacements. The API reference for GTK 3 also includes an index of all deprecated symbols. This section outlines porting tasks that you need to tackle when you get to the point that you actually build your application against Handy 1. Making it possible to prepare for these in Handy 0.0 would have been either impossible or impractical. hdy_init() has been modified to take no parameters. It must be called just after initializing GTK, if you are using #GtkApplication it means it must be called when the #GApplication::startup signal is emitted. It initializes the localization, the types, the themes, and the icons. All widget constructors now return the #GtkWidget type rather than the constructed widget's type, following the same convention as GTK 3. Affected widgets: #HdyActionRow, #HdyComboRow, #HdyExpanderRow, #HdyPreferencesGroup, #HdyPreferencesPage, #HdyPreferencesRow, #HdyPreferencesWindow, #HdySqueezer, #HdyTitleBar, #HdyViewSwitcherBar, #HdyViewSwitcher Some widgets are now final, if your code is deriving from them, use composition instead. Affected widgets: #HdySqueezer, #HdyViewSwitcher, #HdyViewSwitcherBar #HdyFold has been removed. This affects the API of #HdyLeaflet, see the “Adapt to HdyLeaflet API changes” section to know how. HdyColumn has been renamed #HdyClamp as it now implements #GtkOrientable, so you should replace the former by the later. Its “maximum-width” and “linear-growth-width” properties have been renamed #HdyClamp:maximum-size and #HdyClamp:tightening-threshold respectively to better reflect their role. It won't set the .narrow, .medium and .wide style classes depending on its size, but the .small, .medium and .large ones instead. HdyPaginator has been renamed HdyCarousel, so you should replace the former by the later. The “indicator-style”, “indicator-spacing” and “center-content” properties have been removed, instead use #HdyCarouselIndicatorDots or #HdyCarouselIndicatorLines widgets. The #HdyHeaderGroup object has been largely redesigned, most of its methods changed, see its documentation to know more. The child type is now #HdyHeaderGroupChild, which can represent either a #GtkHeaderBar, a #HdyHeaderBar, or a #HdyHeaderGroup. The “focus” property has been replaced by #HdyHeaderGroup:decorate-all, which works quite differently. The #HdyFold type has been removed in favor of using a boolean, and #HdyLeaflet adjusted to that as the #HdyLeaflet:fold property has been removed in favor of #HdyLeaflet:folded. Also, the hdy_leaflet_get_homogeneous() and hdy_leaflet_set_homogeneous() accessors take a boolean parameter instead of a #HdyFold. On touchscreens, swiping forward with the “over” transition and swiping back with the “under” transition can now only be done from the edge where the upper child is. The “over” and “under” transitions can draw their shadow on top of the window's transparent areas, like the rounded corners. This is a side-effect of allowing shadows to be drawn on top of OpenGL areas. It can be mitigated by using #HdyWindow or #HdyApplicationWindow as they will crop anything drawn beyond the rounded corners. The “allow-visible” child property has been renamed “navigatable”. The “none” transition type has been removed. The default value for the #HdyLeaflet:transition-type property has been changed to “over”. “over” is the recommended transition for typical #HdyLeaflet use-cases, if this isn't what you want to use, be sure to adapt your code. If transitions are undesired, set #HdyLeaflet:mode-transition-duration and #HdyLeaflet:child-transition-duration properties to 0. #HdyViewSwitcher doesn't subclass #GtkBox anymore. Instead, it subclasses #GtkBin and contains a box. The “icon-size” property has been dropped without replacement, you must stop using it. #HdyViewSwitcherBar won't be revealed if the #HdyViewSwitcherBar:stack property is %NULL or if it has less than two pages, even if you set #HdyViewSwitcherBar:reveal to %TRUE. The “icon-size” property has been dropped without replacement, you must stop using it. Widgets with a customn CSS node name got their name changed to be the class' name in lowercase, with no separation between words, and with no namespace prefix. E.g. the CSS node name of HdyViewSwitcher is viewswitcher. Action items were packed from the end toward the start of the row. It is now reversed, and widgets have to be packed from the start to the end. It isn't possible to add children at the bottom of a #HdyActionRow anymore, instead use other widgets like #HdyExpanderRow. Widgets added to a #HdyActionRow will now be added at the end of the row, and the hdy_action_row_add_action() method and the action child type have been removed. The main horizontal box of #HdyActionRow had the row-header CSS style class, it now has the header CSS style class and can hence be accessed as box.header subnode. #HdyActionRow is now unactivatable by default, giving it an activatable widget will automatically make it activatable. #HdyComboRow is now unactivatable by default, binding and unbinding a model will toggle its activatability. #HdyExpanderRow doesn't descend from #HdyActionRow anymore but from #HdyPreferencesRow. It reimplement some features from #HdyActionRow, like the #HdyExpanderRow:title, #HdyExpanderRow:subtitle, #HdyExpanderRow:use-underline and #HdyExpanderRow:icon-name, but it doesn't offer the “activate” signal nor the ability to add widgets in its header row. Widgets you add to it will be added to its inner #GtkListBox. #HdyPreferencesPage doesn't subclass #GtkScrolledWindow anymore. Instead, it subclasses #GtkBin and contains a scrolled window. #HdyPreferencesGroup doesn't subclass #GtkBox anymore. Instead, it subclasses #GtkBin and contains a box. #HdyKeypad doesn't subclass #Gtkgrid anymore. Instead, it subclasses #GtkBin and contains a grid. The “show-symbols” property has been replaced by #HdyHeaderGroup:letters-visible. The “only-digits” property has been replaced by #HdyHeaderGroup:symbols-visible, which has a inverse boolean meaning. This also affects the corresponding parameter of the constructor. The “left-action” property has been replaced by #HdyHeaderGroup:start-action, and the “right-action” property has been replaced by #HdyHeaderGroup:end-action. The “entry” property isn't a #GtkWidget anymore but a #GtkEntry. Instead, either use CSS styling (the list.content style class may fit your need), or implement it yourself as it is trivial. When the library was young and changing a lot, we required you to acknowledge that your are using an unstable API. To do so, you had to define HANDY_USE_UNSTABLE_API for compilation to succeed. The API remained stable since many versions, despite this acknowlegment still being required. To reflect that proven stability, the acknowlegment isn't necessary and you can stop defining HANDY_USE_UNSTABLE_API, either before including the &package_string; header in C-compatible languages, or with the definition option of your compiler.