I have a couple of bugfix prs that would be nice to get merged -clipping GOP objects correctly when their distance is changed using the "font" dialoghttps://github.com/pure-data/pure-data/pull/1247re-do tcl/tk key repeat bugfix for tk 8.6.11https://github.com/pure-data/pure-data/pull/1306 I understand if the feature request prs won't make it in but the color hooks has been sitting around for a few years now & I think it's ready to go, aside from some whitespace issues possiblyhttps://github.com/pure-data/pure-data/pull/196there%27s another small feature prhttps://github.com/pure-data/pure-data/pull/1324
thanks, -Seb
-----Original Message-----
Message: 1 Date: Tue, 13 Jul 2021 10:22:17 -0700 From: Miller Puckette msp@ucsd.edu To: pd-dev@lists.iem.at Subject: [PD-dev] plans for next Pd release Message-ID: 20210713172217.v4ch3b3dk7go7k5q@ucsd.edu Content-Type: text/plain; charset=us-ascii
(re-send - I had sent to pd-dev@iem.at but that now seems to be defunct...)
To Pd dev - I'm going to try to get the next Pd release (0.52) out over the next month or two. My personal priorities for this release would be putting in a message backtrace mechanism (by overriding canvas_connect and pd_bind to go through small proxy objects; this will have to be done at load time I think) and to go back and try to figure out how to do tooltips without adding cruft to the inlet structure. (There's an ancient source-patch to provide tooltips by Chris McCormichadn Guenter Geiger that I plan to start with - https://sourceforge.net/p/pure-data/patches/264/).
Before doing that I want to do some reorganizing - in porting Pd to FreeRTOS (so I can run it on an Espressif LyraT board, which I think takes only about 10 or 20% of the current that a Pi needs) I found out that I had to move a few functions from one file to another.
This might break some PRs, so... first of all would be to identify whatever PRs are ready to merge so I can do that before I make incompatible changes. Of course "stable development branch" first... then Dan's soundfile updates... then what?
PS more ideas of mine (among many): hot-reloading externs via a message to Pd use a "unix binding" socket between Pd and pd-gui instead of localhost generalize number/symbol box to allow displaying entire messages or lists
cheers Miller
Whoops, I just noticed there are now conflicts in the colors branch (probably after the recent merges). I'll try to get to those today or tomorrow anyways.
-----Original Message----- From: Sebastian Shader sebfumaster@aol.com To: pd-dev@lists.iem.at pd-dev@lists.iem.at Sent: Tue, Jul 13, 2021 2:05 pm Subject: Re: plans for next Pd release
I have a couple of bugfix prs that would be nice to get merged -clipping GOP objects correctly when their distance is changed using the "font" dialoghttps://github.com/pure-data/pure-data/pull/1247re-do tcl/tk key repeat bugfix for tk 8.6.11https://github.com/pure-data/pure-data/pull/1306 I understand if the feature request prs won't make it in but the color hooks has been sitting around for a few years now & I think it's ready to go, aside from some whitespace issues possiblyhttps://github.com/pure-data/pure-data/pull/196there%27s another small feature prhttps://github.com/pure-data/pure-data/pull/1324
thanks, -Seb
-----Original Message-----
Message: 1 Date: Tue, 13 Jul 2021 10:22:17 -0700 From: Miller Puckette msp@ucsd.edu To: pd-dev@lists.iem.at Subject: [PD-dev] plans for next Pd release Message-ID: 20210713172217.v4ch3b3dk7go7k5q@ucsd.edu Content-Type: text/plain; charset=us-ascii
(re-send - I had sent to pd-dev@iem.at but that now seems to be defunct...)
To Pd dev - I'm going to try to get the next Pd release (0.52) out over the next month or two. My personal priorities for this release would be putting in a message backtrace mechanism (by overriding canvas_connect and pd_bind to go through small proxy objects; this will have to be done at load time I think) and to go back and try to figure out how to do tooltips without adding cruft to the inlet structure. (There's an ancient source-patch to provide tooltips by Chris McCormichadn Guenter Geiger that I plan to start with - https://sourceforge.net/p/pure-data/patches/264/).
Before doing that I want to do some reorganizing - in porting Pd to FreeRTOS (so I can run it on an Espressif LyraT board, which I think takes only about 10 or 20% of the current that a Pi needs) I found out that I had to move a few functions from one file to another.
This might break some PRs, so... first of all would be to identify whatever PRs are ready to merge so I can do that before I make incompatible changes. Of course "stable development branch" first... then Dan's soundfile updates... then what?
PS more ideas of mine (among many): hot-reloading externs via a message to Pd use a "unix binding" socket between Pd and pd-gui instead of localhost generalize number/symbol box to allow displaying entire messages or lists
cheers Miller
Em ter., 13 de jul. de 2021 às 18:06, Sebastian Shader via Pd-dev < pd-dev@lists.iem.at> escreveu:
I understand if the feature request prs won't make it in but the color hooks has been sitting around for a few years now
now is the time to take them actually, and this is the oldest one, so the first in consideration list
& I think it's ready to go, aside from some whitespace issues possibly https://github.com/pure-data/pure-data/pull/196
+1000 for this one. Can't wait to setup different modes
there's another small feature pr https://github.com/pure-data/pure-data/pull/1324
thanks, -Seb
-----Original Message-----
Message: 1 Date: Tue, 13 Jul 2021 10:22:17 -0700 From: Miller Puckette msp@ucsd.edu To: pd-dev@lists.iem.at Subject: [PD-dev] plans for next Pd release Message-ID: 20210713172217.v4ch3b3dk7go7k5q@ucsd.edu Content-Type: text/plain; charset=us-ascii
(re-send - I had sent to pd-dev@iem.at but that now seems to be defunct...)
To Pd dev - I'm going to try to get the next Pd release (0.52) out over the next month or two. My personal priorities for this release would be putting in a message backtrace mechanism (by overriding canvas_connect and pd_bind to go through small proxy objects; this will have to be done at load time I think) and to go back and try to figure out how to do tooltips without adding cruft to the inlet structure. (There's an ancient source-patch to provide tooltips by Chris McCormichadn Guenter Geiger that I plan to start with - https://sourceforge.net/p/pure-data/patches/264/).
Before doing that I want to do some reorganizing - in porting Pd to FreeRTOS (so I can run it on an Espressif LyraT board, which I think takes only about 10 or 20% of the current that a Pi needs) I found out that I had to move a few functions from one file to another.
This might break some PRs, so... first of all would be to identify whatever PRs are ready to merge so I can do that before I make incompatible changes. Of course "stable development branch" first... then Dan's soundfile updates... then what?
PS more ideas of mine (among many): hot-reloading externs via a message to Pd use a "unix binding" socket between Pd and pd-gui instead of localhost generalize number/symbol box to allow displaying entire messages or lists
cheers Miller
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
-
Alexandre Torres Porres -
Sebastian Shader