Hi, I have recently included into ELSE (though it is not part of any release yet) a [dictionary] object that is a very simple external based on vanilla's [text] (hence, it's an abstraction). It works more like a simplified Max [coll]: address/key lookup returning stored data. It’s not a hierarchical JSON-style structure, but it might cover part of the associative key–value use case. Curious what specific features you need on the C side and I am also interested in this whole topic.
I am still using some objects from ELSE into this abstraction, so it can't be fully Vanilla. I am using some dynamic patching hacks that need "initbang", which is a functionality I have included into my [loadbanger] object. One thing that I am struggling with in [text] is being able to set commas into a line via external messages, see https://github.com/pure-data/pure-data/issues/1262 - I am now doing a very dirty hack to overcome this issue. And also, getting a whole line with things separated by commas is not quite easy with [text], but I've managed to do so with my [dictionary] abstraction. By the way, I was trying to use Pd's Data Structures to deal with some Lisp-like Linked Lists, hoping to be able to work with arrays of arrays, but it was just too limited and impossible. This is for another project, which is like the BACH library for Pd. The way around was to use LUA, and I also have LUA in ELSE. Maybe dealing with LUA can help and we have also already discussed about natively supporting LUA in PD, see https://github.com/pure-data/pure-data/issues/687 As far as parsing JSON files goes into Pd vanilla, I think that besides importing it into a [text], you can think about maybe using [file]? Maybe that's overkill, I don't know. cheers Em dom., 8 de fev. de 2026 às 11:47, Pierre Alexandre Tremblay < [email protected]> escreveu: > 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-in-puredata/2717/16 > > 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 > --- > [email protected] - the Pure Data mailinglist > > https://lists.iem.at/hyperkitty/list/[email protected]/message/YWXEUDCIFKZH5ZHUAPXYZSCA6Q2J4OBX/ > > To unsubscribe send an email to [email protected] mailing list > UNSUBSCRIBE and account-management -> https://lists.iem.at/
--- [email protected] - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/[email protected]/message/43MFISAJZGGGXZXY6FMWCPGU36GCMUNM/ To unsubscribe send an email to [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
