(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 that externals can support
registering their parameters as belonging to the state. The above only
applies to canonical Pd.
Of course if I am incorrect or presumptuous, then I'm certain others
will correct and discuss. Breaking the ice is fine too.
./d5
On Dec 16, 2006, at 6:29 PM, Miller Puckette wrote:
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 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 state? ;)
There's nothing funny or joke-like in that. I ask you: what is a
state?
What I think is funny about this question is that often it seems
people would think the answer is obvious, while I agree with you that
it's not obvious at all!
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 from what you want to
save. What I want to save also somehow defines what I don't want to
save. So the next questions are: How to tell Pd what should be saved
and
what not? Or: Can Pd make educated guesses about what should and
shouldn't be saved? Should Pd guess at all?
Ciao
--
Frank Barknecht _ ______footils.org_ __goto10.org__
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
