we do tap on one of these in flucoma, so if I do a fluid.dictionary it’ll be this that I use indeed. I just try to keep maintenance of codebase to minimum, and dependencies to null.
p
On 8 Feb 2026, at 20:53, Dan Wilcox danomatika@gmail.com wrote:
Unless the usage is very basic, I think plain vanilla as a requirement does not make sense for this. There are numerous C and C++ libraries which handle the basics and should be leveraged instead of reading bytes with [file] or something similar. Best of all, many of these libraries are only 1-2 files, so making a light wrapper external with minimal requirements for compilation should not be huge issue IMO.
On Feb 8, 2026, at 8:04 PM, hans w. koch hansw.koch@gmail.com wrote:
hello pierre alexandre,
a while ago i made a parser for .kml files (xml files recorded by bycicle route trackers) for a friend to sonify her tours. its plain vanilla and was a pita to make :-) if thats interesting for you, i can send you a copy of the patch.
cheers
hans
Am 08.02.2026 um 17:48 schrieb Pierre Alexandre Tremblay tremblap@gmail.com:
did you have a look at the purest_json library, does it help?
I didn’t but I saw it was neither vanilla nor available for all CPUs, so that won’t be helpful in my case (except if I decide to tackle a fluid.dictionary external which i don’t want to if I can avoid it)
hence asking if there was a native version/hack. I’ll look at Alexandre’s abstraction, that might do the trick. The idea would be to be able to dump fluid* status (mlp for instance) in text, edit, then load them back. This has been seen as useful on other platforms, so I’m trying to find a way…
BACH library for Pd.
now, that is a fun challenge ;) I was talking to both Daniele and Andrea about this in the last year… it would be a fantastic addition obviously but I don’t envy the person who will do that job
p
On 8 Feb 2026, at 17:38, João Pais jmmmpais@gmail.com wrote:
did you have a look at the purest_json library, does it help?
Dear all
Apart the fact that flucoma releases (and nightles soon) are on deken (hurray!), I am slowly getting back in trying to add the last bit missing to our interface… but the lack of native dictionary style file/data structure is not helping us to keep the structured (json style) states of objects simply yet programmatically editable (like in max and supercollider)
here is an example of one of our user’s clever use of the text object despite its limits
https://discourse.flucoma.org/t/way-of-modifying-state-of-fluid-robustscale-...
now I know there are “pd structure” magicians on here, and maybe someone has had the idea to create a sort of hack to parse json files, or even general dictionaries of associative key-values?
Ideally, I’d be able to access those in the C api… but a temp json file is also possible on the way, we do that with SuperCollider anyway.
any pointers (pun intended) welcome
p
pd-list@lists.iem.at - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/YWXEUDCIFK...
To unsubscribe send an email to pd-list-leave@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.i
pd-list@lists.iem.at - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/QI3VZVQVMY...
To unsubscribe send an email to pd-list-leave@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
pd-list@lists.iem.at - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/FDMWVTTF62...
To unsubscribe send an email to pd-list-leave@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
pd-list@lists.iem.at - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/V5ZSSTMQSA...
To unsubscribe send an email to pd-list-leave@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
Dan Wilcox danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/