[PD-dev] plans for next Pd release

Christof Ressi info at christofressi.com
Wed Jul 14 00:36:23 CEST 2021

Hi Miller,

great to see Pd 0.52 approaching!

Here's a list of my open PRs: 

I made sure that they all apply cleanly.


Some are trivial:

* https://github.com/pure-data/pure-data/pull/769

* https://github.com/pure-data/pure-data/pull/764


Others need more discussion:

* https://github.com/pure-data/pure-data/pull/630

* https://github.com/pure-data/pure-data/pull/849


Here are some simple feature PRs:

* [goprect( method to dynamically change the GOP rect: 

* allow to receive large UDP packets: 

* [clone]: allow resizing and always have at least one inlet: 

* "-open-with-args" command line option: 


These are bit larger, but still reasonable (at least I like to think so :-)

* new [list store] methods: [set(, [insert(, [delete(, [send(: 

* [poly]: allow resizing, dynamically set note stealing, sustain pedal 
mode: https://github.com/pure-data/pure-data/pull/661

* new [list] methods: [list foreach], [list join] and [list unjoin]: 


Finally, this one would make me very happy: 

I would definitely see this as a temporary solution. After Gem and 
ophelia (who else?) have adapted their macOS input handling code, the 
option could be removed entirely.



On 13.07.2021 19:22, Miller Puckette via Pd-dev wrote:
> (re-send - I had sent to pd-dev at 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 at lists.iem.at
> https://lists.puredata.info/listinfo/pd-dev

More information about the Pd-dev mailing list