Hi all. Speaking as an Haiku app developer, one of my new projects is
using the Services Kit, and I personally have no problem refactoring it to
use any new API even when it breaks the ABI (as long as a transition guide
is written to help us migrate to the new API). This is expected for a Beta
/ development release. Of course, after R1 is finally released, I do
expect the ABI to be set in stone ...
So from my personal perspective, I prefer that the core developers break
the API in Beta in order to fix deficiencies/bugs, since I would rather
have something that works than something I ignore.
On Mon, 1 Mar 2021 at 08:35, Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>
wrote:
28 février 2021 21:48 "Niels Sascha Reedijk" <niels.reedijk@xxxxxxxxx> a
écrit:
Hi all,
I have been working on adapting some of leorize's patches, and two big
changes landed in hrev54968.
I have some further ideas for improvements that I want to bring up and
land into the code at some stage, though it would probably be some
fundamental changes, and I think it is better to wait with that after
beta3 branches, so that we can drop the compatibility #ifdefs before
changing class hierarchy.
I recall that the discussion to put this code back in its own library
(for now) was to make some improvements that are going to be
beneficial for WebPositive, but I am now wondering to what extend that
there are actual blockers right now, or whether WebPositive can go
forward the way it is.
I wanted to look into WebKit today but found that my git checkout is
somehow corrupt.
So I will need to re-clone the repository.
If no one gets to it before me, I will investigate the status of leorize's
changes
there and see if further work is needed.
--
Adrien.
