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/
Totally agree with Dan on all points.
On Mon, 13 Aug 2018 at 12:32, Dan Wilcox danomatika@gmail.com wrote:
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 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 robotcowboy.com
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Likewise. Is there anyone opposing?
On 13.08.2018 13:23, Matt Davey wrote:
Totally agree with Dan on all points.
On Mon, 13 Aug 2018 at 12:32, Dan Wilcox <danomatika@gmail.com mailto:danomatika@gmail.com> wrote:
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 canvasOn Aug 12, 2018, at 11:40 PM, pd-list-request@lists.iem.at <mailto: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> _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
This is what I always believed to be true, so I'm onboard with this, and I've also extensively written this in Pd documentations. Currently I'm translating my portuguese tutorials to english and I'm just gonna stick to the subpatch/abstraction definition as this.
Max, please go ahead and make that Pull Request. If there's objection, it'll appear.
cheers
Em seg, 13 de ago de 2018 às 09:23, Max abonnements@revolwear.com escreveu:
Likewise. Is there anyone opposing?
On 13.08.2018 13:23, Matt Davey wrote:
Totally agree with Dan on all points.
On Mon, 13 Aug 2018 at 12:32, Dan Wilcox <danomatika@gmail.com mailto:danomatika@gmail.com> wrote:
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 objectinstantiation)
* "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 canvasOn Aug 12, 2018, at 11:40 PM, pd-list-request@lists.iem.at <mailto: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> _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
By the way, I'm also defining abstractions as a type of external object, as opposed to a compiled object type. That makes sense, right?
Em dom, 26 de ago de 2018 às 20:54, Alexandre Torres Porres < porres@gmail.com> escreveu:
This is what I always believed to be true, so I'm onboard with this, and I've also extensively written this in Pd documentations. Currently I'm translating my portuguese tutorials to english and I'm just gonna stick to the subpatch/abstraction definition as this.
Max, please go ahead and make that Pull Request. If there's objection, it'll appear.
cheers
Em seg, 13 de ago de 2018 às 09:23, Max abonnements@revolwear.com escreveu:
Likewise. Is there anyone opposing?
On 13.08.2018 13:23, Matt Davey wrote:
Totally agree with Dan on all points.
On Mon, 13 Aug 2018 at 12:32, Dan Wilcox <danomatika@gmail.com mailto:danomatika@gmail.com> wrote:
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 objectinstantiation)
* "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 canvasOn Aug 12, 2018, at 11:40 PM, pd-list-request@lists.iem.at <mailto: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> _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
Alexandre Torres Porres -
Dan Wilcox -
Matt Davey -
Max