Re: [PD-dev] release time?
Em dom., 27 de nov. de 2022 às 14:58, Miller Puckette via Pd-dev < pd-dev@lists.iem.at> escreveu: > TO pd dev - > > I'm fixing to make a bugfix release. I just merged 'develop' and > 'Documentation'. > Anything else (fixes only, please, no new features) that I should look at? > This one fell out of my radar but it's something I consider a bug and have been hoping for ages to be fixed :) https://github.com/pure-data/pure-data/pull/708 cheers > > thanks > Miller > > > > > ___ > Pd-dev mailing list > Pd-dev@lists.iem.at > https://lists.puredata.info/listinfo/pd-dev > ___ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] release time?
Em ter., 29 de nov. de 2022 às 13:32, Antoine Rousseau escreveu: > 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? > I think that adapting is really simple, just copy and use the old public iemgui API, no need to entirely rewrite, right? ___ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] release time?
> > 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 a écrit : > > > Em dom., 27 de nov. de 2022 às 23:33, Alexandre Torres Porres < > por...@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 > ___ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] release time?
Em dom., 27 de nov. de 2022 às 23:33, Alexandre Torres Porres < por...@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
Re: [PD-dev] release time?
Em dom., 27 de nov. de 2022 às 18:11, IOhannes m zmölnig escreveu: > i also do not have any numbers, on how many externals are actually > affected by the current breakage (i only know of moonlib and iemgui; but > there might be others) > I also believe iemguis should not be used as a public API We can investigate. There aren't that many GUI externals. Worst case scenario, we update them. cheers ___ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] release time?
On 11/27/22 18:57, Miller Puckette via Pd-dev wrote: TO pd dev - I'm fixing to make a bugfix release. I just merged 'develop' and 'Documentation'. Anything else (fixes only, please, no new features) that I should look at? i'm wondering about the major iemgui regression. as of now, any external library that uses the g_all_guis.h infrastructure (e.g. the "iemgui" library, or moonlib's mknob) crashes with Pd-0.53. antoine has updated moonlib to use the new infrastructure (but the binaries are now Pd-0.53 only). i started updating the "iemgui" library (but i haven't completed that yet). so i wonder whether: - we should keep binary compatibility with old binaries, probably at the cost of keeping two distinct iemgui-frameworks in the sources (g_all_guis-legacy and g_all_guis-new) - we should retire the public iemgui API (just like we did for "error()"), so the only API for creating GUI externals is directly via the widgetbehaviour functions. the two questions are somewhat orthogonal, but i think the question ought to be tackled. as i've said before, my personal perference would be at retracting the API and not caring about ABI breakage, but that is a very radical approach, and rather unusual for the Pd world. i am not very optimistic about being able to merge the new-style and legacy g_all_guis into a single ABI-compatible (with older binaries) interface. hence my radical approach. but i can totally understang if such an approach is not acceptable. i also do not have any numbers, on how many externals are actually affected by the current breakage (i only know of moonlib and iemgui; but there might be others) gfmdsa IOhannes OpenPGP_signature Description: OpenPGP digital signature ___ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] release time?
this one also seems stupid enough to get in https://github.com/pure-data/pure-data/pull/1034 Em dom., 27 de nov. de 2022 às 16:20, Lucas Cordiviola < lucard...@hotmail.com> escreveu: > html: there's branch > https://github.com/pure-data/pure-data/tree/htmldocs with no PR. It > mostly contains updates to chapter6. you can do a local merge. > > > > -- > > Mensaje telepatico asistido por maquinas. > > On 27/11/2022 14:57, Miller Puckette via Pd-dev wrote: > > TO pd dev - > > > > I'm fixing to make a bugfix release. I just merged 'develop' and > 'Documentation'. > > Anything else (fixes only, please, no new features) that I should look > at? > > > > thanks > > Miller > > > > > > > > > > ___ > > Pd-dev mailing list > > Pd-dev@lists.iem.at > > https://lists.puredata.info/listinfo/pd-dev > > > > ___ > Pd-dev mailing list > Pd-dev@lists.iem.at > https://lists.puredata.info/listinfo/pd-dev > ___ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] release time?
html: there's branch https://github.com/pure-data/pure-data/tree/htmldocs with no PR. It mostly contains updates to chapter6. you can do a local merge. -- Mensaje telepatico asistido por maquinas. On 27/11/2022 14:57, Miller Puckette via Pd-dev wrote: TO pd dev - I'm fixing to make a bugfix release. I just merged 'develop' and 'Documentation'. Anything else (fixes only, please, no new features) that I should look at? thanks Miller ___ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev ___ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] release time?
Em dom., 27 de nov. de 2022 às 14:58, Miller Puckette via Pd-dev < pd-dev@lists.iem.at> escreveu: > TO pd dev - > > I'm fixing to make a bugfix release. I just merged 'develop' and > 'Documentation'. > Anything else (fixes only, please, no new features) that I should look at? > Hi! Yay!!! This one for sure, it missed getting into develop - https://github.com/pure-data/pure-data/pull/1840 This is something that is in conflict with how things are documented, you made some remarks and I revised it. I think it's good to go. - https://github.com/pure-data/pure-data/pull/1618 these both issues/fixes also get into conflicts with how things are documented - https://github.com/pure-data/pure-data/pull/1581 - https://github.com/pure-data/pure-data/pull/1683 anyway, here's the full list of things marked as bug fixes on github https://github.com/pure-data/pure-data/pulls?q=is%3Apr+is%3Aopen+label%3Abug%2Ffix cheers > > thanks > Miller > > > > > ___ > Pd-dev mailing list > Pd-dev@lists.iem.at > https://lists.puredata.info/listinfo/pd-dev > ___ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
[PD-dev] release time?
TO pd dev - I'm fixing to make a bugfix release. I just merged 'develop' and 'Documentation'. Anything else (fixes only, please, no new features) that I should look at? thanks Miller ___ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
