Describe Projects/GTK/Meetings/PostGTK4/Notes2 here.
status updates
ebassi doing docs fixes
some discussion around getting doc checks into ci
the resizing question:
- wayland backend works, X works somewhat
- more testing needed
- big scary changes, not api compatible to land in 4.x
- Benjamin would really like to see this in 4.0
- Matthias too
- Decision: we'll all take some time to look at the branch this week, and see if this
Christian brought up Mac OS backend issues - the resizing changes look scary to him There's a bunch of other issues he filed. One is around mainloops not quitting, another is about keyboard modifiers and the hardcoded mapping.
Christian would appreciate if somebody else could test the MacOS backend
There will be a release party in 2 weeks, December 16, 16-18UTC
Topic: cell renderers
Benjamin gives a strong plea for removing the whole thing - this is the GTK5 plan of record.
Some discussion around deprecating things out of the box in 4.0 - sentiment is to rather not do that, and instead wait until 4.2 / next summer. Putting css apis into a separate library is probably not realistic, or useful, since it is too intertwined with private apis.
Lots of discussion about performance of gutter rendering with widgets instead of cell renderers.
We briefly discussed file chooser futures
Topic: animations
Georges played with layout transitions in a GTK4 port of gnome-todo. It wasn't great. Jonas talks about doing ui animation in the style of apples uikit. Ebassi has designed and implemented 3 different animation frameworks. All have problems. Important to limit scope. Implicit vs explicit animations. Implicit animations are easy and good demoware. As soon as things are complex and multiple objects are moving or multiple properties get changed, you need explicit keyframes. coreanimation/uikit is the "gold standard" for animation api. coreanimation can turn explicit animations into implicit ones, making them fire-and-forget after setting them up.
Christian points out that smoothness of animation on os x is somewhat due to input threading and bypassing layout for scrolling.
The sentiment is that this is not a GTK4 topic, since it needs api and infrastructure changes to work well.
Benjamin thinks that having performance testing in CI is a prerequisite for getting a working animation api. He hopes we can prototype how to define and stage animations.
Topic: icons
Jimmac describes all the outdated aspects of our icon machinery: inheritance, small sizes, semantic naming. Current approach to have a catch-all Adwaita icon theme, with semantic names. New approach: icon development kit. App developers request icons, icon names are descriptive.
https://flathub.org/apps/details/org.gnome.design.IconLibrary
Ideas for GTK:
- - Don't depend on Adwaita-icon-theme - Include icon assets we need ourselves - Maybe have a more standalone api for loading icons symbolically
Benjamin points out that css has properties to force symbolic or full-color loading.