we should retire the public iemgui API
does this mean that mknob (or iemgui library) would have to be entirely rewritten, by copying/adapting the entire iemgui API to mkob source tree?
not caring about ABI breakage
the ABI compatibility is already broken IIUC ;-)
GUI objects aren't that common for Pd, unfortunately
obviously... there would be many more with a better (and more stable...) GUI system. We all feel that we need to move forward. @IOhannes is it for this reason that you want to retract the iemgui API? To have freer hands when modifying the GUI code?
I totally understand this reason; however, maybe we can wait here, since it's unlikely that someone starts a new GUI project on the current codebase, before we switch to a better system... I wouldn't want to have to rewrite the mknob, which would be needed by someone (not me actually...) who would need Pd 0.54 at the same time.... We could simply discourage new developers from using the API, maybe signaling it's about to be deprecated.
Antoine
Le lun. 28 nov. 2022 à 03:48, Alexandre Torres Porres porres@gmail.com a écrit :
Em dom., 27 de nov. de 2022 às 23:33, Alexandre Torres Porres < porres@gmail.com> escreveu:
We can investigate.
besides moonlib's knob, the knob from 'flatgui' also uses it.
I also found objects in "iemgui" that uses it, like [cube_sphere] (I guess "IEM" can easily take care of this one hehe).
These are all the ones found in Pd Extended. I don't remember or know of any new compiled GUIs popping up since its demise that would use this. The ones from ELSE don't use it, the ones from CEAMMC don't either.
Again, GUI objects aren't that common for Pd, unfortunately.
cheers
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev