[L2Ork-dev] vanilla in Purr and Purr in vanilla compatibiity
aggraef at gmail.com
Mon Sep 21 18:22:17 EDT 2020
On Mon, Sep 21, 2020 at 10:58 PM Jonathan Wilkes <jon.w.wilkes at gmail.com>
> 1. When loading a Vanilla patch in Purr Data, what is the optimal UX
> so that the user gets something as close as possible to Vanilla
> behavior/display with the least amount of work/knowledge?
> Albert has a current merge request wrt #1 here:
That's not entirely true. Jonathan wants to address all (or most) legacy
issues we encounter when exchanging patches between Purr Data and Vanilla
in a completely (or mostly) automatic way, by keeping track of the Pd
version a (sub)patch was created with (Purr or Vanilla).
My MR is much more modest (and presumably simpler). It's about enabling
some canvas-local flags (maintained with `declare`) for some specific
global options. Currently I'm concerned solely with the "legacy-bendin" and
"save/restore zoom level" flags, which are causing me woes because at
present they can only be set globally and not locally in a patch.
So the two approaches are really different (although not completely
orthogonal), and also aimed at different audiences.
But I don't want to rehash the entire discussion here, please go to
https://git.purrdata.net/jwilkes/purr-data/-/merge_requests/561 for more
Just writing out these points, I'm not wondering if #2 could be solved
> with some kind of menu button that analyzes the current patch's binbuf
> and prints out a series of "compatibility errors" so that the user can
> click the link and visit the relevant object.
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email: aggraef at gmail.com, web: https://agraef.github.io/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the L2Ork-dev