My 2 cents:
"subpatch" to me refers to [pd ...] aka a patch within a patch, saved within the same patch file that uses it (no object instantiation)
"abstraction" to me refers to a patch saved to and loaded from it's own file (object instantiation)
using "subpatches and abstractions" when referring to both is the is the best option, I agree that "subwindow" is problematic since there multiple types of things displayed in multiple windows already (ie. the audio dialog could conceptually be a subwindow as well...)
my preference is for "subpatch" as opposed to "sub-patch"
"canvas" is problematic as there are already two notions of canvas within Pd: the Pd patch canvas and the TK drawing canvas
On Aug 12, 2018, at 11:40 PM, pd-list-request@lists.iem.at wrote:
Message-ID: <40aca4a4-d098-f49b-4914-46180e74dc56@revolwear.com mailto:40aca4a4-d098-f49b-4914-46180e74dc56@revolwear.com> Content-Type: text/plain; charset=utf-8; format=flowed
I see, then maybe we are better off without umbrella term and just refer to subpatches and abstractions as "subpatches and abstractions".
m.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/