Hi Sebastien!
* Use GtkOrientation interface when possible * Remove GdlDockObject macros and replace them with access functions * Remove public member as far as possible, replacing them with function when needed. * Change some functions normally used only inside GDL. * Make API easier to use for introspection.
That all looks good to me.
What do you think about this? Do you think that some points are more important. Do you see other things more important for GDL? What do we do with the compatibility?
In general we make no guarantees API/ABI-wise so it's fine to change API where it makes sense by removing public structure members and remove public functions that should be private from the headers. It would be nice to reduce the amount of work that needs to be done by users to a minimum though. Maybe we can add a section explaining the changes between 3.4 and 3.6 somewhere in the docs where it's non-obvious. For stuff that is still maintained and on git.gnome.org it would be good to provide patches so people don't run into build issues with jhbuild. inkscape doesn't use upstream, yet, so they have to adapt to the changes when the want to. Regards, Johannes
Attachment:
signature.asc
Description: This is a digitally signed message part