On Sun, 17 Dec 2006, Frank Barknecht wrote:
Mathieu Bouchard hat gesagt: // Mathieu Bouchard wrote:
I'd say, a state is whatever you may want to save. Is that a good
definition?
This would be my basic definition as well. Even this has some direct
consequences: What I want to save is different
Frank Barknecht wrote:
Hallo,
Cesare Marilungo hat gesagt: // Cesare Marilungo wrote:
I don't want to sound pretentious. But i think that there's an easy
answer: save *everything* as a default behavior. I should load a patch
and have the very same situation I had when I saved it.
It
Hallo,
Cesare Marilungo hat gesagt: // Cesare Marilungo wrote:
No. Because the state is saved in the patch which use the abstraction.
But which state should be saved if you edit an abstraction itself?
Ciao
--
Frank Barknecht _ __footils.org_ __goto10.org__
Hallo,
Cesare Marilungo hat gesagt: // Cesare Marilungo wrote:
Frank Barknecht wrote:
You mean if you open it from inside a patch which use the abstraction?
Well... uhm... :-[
I'm tempted to answer that if you open an abstraction, and you modify it
(even adding object and repatching
i think it'd be worth having the option to just bundle
abstractions etc. as well as bundle everything (inc
externals)
mostly in the interests of keeping file sizes down, i
can see that as well as using this to distribute
patches easily, it'd be a nice tool for archiving
patches in one particular
On Fri, 15 Dec 2006, Kyle Klipowicz wrote:
Similarly with encapsulation, I am still thinking that being able to
encapsulate a selected group of objects into a pd object while
preserving the connections would be great.
This is called subpatcherising. It would have been already finished in
On Fri, 15 Dec 2006, Frank Barknecht wrote:
A further step would be some easy way to read and write the state of
objects without having to watch their communication through senders and
receivers, but that's the hard part, because it touches philosophical
questions like: What actually is a
Hallo,
Mathieu Bouchard hat gesagt: // Mathieu Bouchard wrote:
On Fri, 15 Dec 2006, Frank Barknecht wrote:
A further step would be some easy way to read and write the state of
objects without having to watch their communication through senders and
receivers, but that's the hard part,
Exactly. If I could answer those questions I'd code it up right now...
cheers
Miller
On Sun, Dec 17, 2006 at 01:21:29AM +0100, Frank Barknecht wrote:
Hallo,
Mathieu Bouchard hat gesagt: // Mathieu Bouchard wrote:
On Fri, 15 Dec 2006, Frank Barknecht wrote:
A further step would be
(IMHO) `State saving` would nominally be all data stored in
* Toggle
* Number
* Number2
* Symbol
* Internally in [f ]/[i ] objects (and permutations involving [t ])
* Messages exactly as they are at save time
* V/Hslider
* V/Hradio
* Tables
* Arrays
Optionally
|_ Add a mechanism to the API so
I don't want to sound pretentious. But i think that there's an easy
answer: save *everything* as a default behavior. I should load a patch
and have the very same situation I had when I saved it.
It's true that we all use Pd in different ways and to accomplish various
things. But it would be
Hi,
Just to add to the noise, I'd like to say that I wholeheartedly support
this feature request.
On Fri, Dec 15, 2006 at 11:44:54PM +0100, Frank Barknecht wrote:
I am a big fan of the way that you have done it, Frank, using only
existing objects. I think to make the whole thing complete,
I've been thinking about some other ways to do that (also would like to
figure out how to bundle externs, files for 'qlist', etc in a single
gesture) but there's something about this particular idea I like...
(OK here are some others:
2. Have a bundle file type that causes Pd actually to build
Did I have too much wax in my ears, or did I just hear Miller say something
about integrating a state saving system in Pd!?!?! Is it April 1st?
Please do this! It would make my decade.
~Kyle
On 12/15/06, Miller Puckette [EMAIL PROTECTED] wrote:
4. write a general state-saving mechanism
On Dec 15, 2006, at 12:16 PM, Miller Puckette wrote:
I've been thinking about some other ways to do that (also would
like to
figure out how to bundle externs, files for 'qlist', etc in a single
gesture) but there's something about this particular idea I like...
(OK here are some others:
2.
Hallo,
Miller Puckette hat gesagt: // Miller Puckette wrote:
I've been thinking about some other ways to do that (also would like to
figure out how to bundle externs, files for 'qlist', etc in a single
gesture) but there's something about this particular idea I like...
(OK here are some
On Dec 15, 2006, at 5:14 PM, Frank Barknecht wrote:
Hallo,
Miller Puckette hat gesagt: // Miller Puckette wrote:
I've been thinking about some other ways to do that (also would
like to
figure out how to bundle externs, files for 'qlist', etc in a single
gesture) but there's something about
On Dec 15, 2006, at 5:44 PM, Frank Barknecht wrote:
Hallo,
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
From what I gather you are looking for, a libdir is almost ready for
that. AFAIK, the only missing piece is a mechanism to open a libdir
like a patch. I think this
I just thought I'd propose an idea I had driving home : ):
As a supplement to the subpatcher functionality, what about having a
[pddefine] object that took a name as its argument, and a patch built
inside would then be callable within the parent patch patch, acting
functionally equivalent to an
19 matches
Mail list logo
