Conversation

Notices

1. Chris 🌱 (brainblasted@jade.moe)'s status on Saturday, 11-Feb-2023 12:01:40 JST Chris 🌱

   One thing I really like to do when we're working on new API for libadwaita is test it in the apps that need it most, before we land the API in main. This makes it easy to verify what apps need and what use cases we've forgotten to account for.

   This also means that once we merge the new API, we can rapidly roll it out to apps with confidence.

   • Adrian Cochrane repeated this.
   • Adrián Pérez (aperezdc@mastodon.social)'s status on Saturday, 11-Feb-2023 17:24:15 JST Adrián Pérez

     in reply to

     • WebKitGTK

     @brainblasted we have done this with @WebKitGTK in the latest years as well! For nontrivial API changes we often try it with Epiphany (our test mule!) during development, sometimes with Devhelp. We itere until the API feels right in a C application, then add documentation and auxiliary functions which might be needed for languages using introspection. It's more effort upfront, but the outcomes are better 🛠️

   • Adrian Cochrane (alcinnz@floss.social)'s status on Sunday, 12-Feb-2023 03:31:23 JST Adrian Cochrane

     in reply to

     • WebKitGTK
     • Adrián Pérez

     @aperezdc @brainblasted @WebKitGTK One reason I've started running my own (SourceHut) codeforge: So I can fork it & test out new HTML/CSS features I want to implement.

     But first I need the basics working...