Hi,

I didn't really know sssad-saving system, i think i tried it once... i gonna look at how this is done and try to continue learning... ....But afterall, no matter, it was a good exercise.

Cheers Guillaume Rabusseau

From: Frank Barknecht fbar@footils.org To: pd-list@iem.at, pd-announce@iem.at Subject: Re: [PD] g_save-0.1 Storage system with pool Date: Tue, 13 Feb 2007 19:48:02 +0100

Hallo, guillaume rabusseau hat gesagt: // guillaume rabusseau wrote:

...

I've just finished to make a clean release of the saving system i mostly use. It's two abstractions (a "console" and an object you have to create for each variable (floats or symbols) to store), you can store 16

presets

...

(with as many variable as you want) and save them into a file.

You will need pool, iemlib (dollarg) and zexy..

I tried to make a clear help file, i hope it will not be to hard to understand...

[TODO : * Allow multiple instance * Allow storage of lists * A lot of other things i think...]

Nice work, but it seems to do not much more than the sssad-saving system in CVS. Additionally sssad already can store lists, allows multiple instances, is less intrusive regarding the send/receive namespace compared to g_save and doesn't require any externals.

Ciao

Frank Barknecht _ ______footils.org_ __goto10.org__

---

PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

Avec Windows Live OneCare éliminez tous les virus de votre PC ! http://www.windowslive.fr/liveonecare/default.asp

On Feb 13, 2007, at 5:50 PM, Frank Barknecht wrote:

Hallo, guillaume rabusseau hat gesagt: // guillaume rabusseau wrote:

...

I didn't really know sssad-saving system, i think i tried it
once... i gonna look at how this is done and try to continue learning... ....But afterall, no matter, it was a good exercise.

Yes, writing a state saving system is a really good exercise, as it touches a lot of the deep, important parts of Pd, like execution order, local and global scoping, abstractions, list processing etc.

I guess you will find several of your ideas realised in sssad as well, as I saw several of the sssad idioms in your state saver. Another good one is included in netpd.

Since there are now a number of state saving systems out there, and a
number of ideas have been tried, I'd really like to see one that's
very well integrated with Pd, with a library of GUI objects (like
Max's [preset]), and all the other goodies. Perhaps this could spur
some collaboration?

.hc

Ciao

Frank Barknecht _ ______footils.org_ __goto10.org__

---

PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list

All information should be free. - the hacker ethic

Hallo, guillaume rabusseau hat gesagt: // guillaume rabusseau wrote:

Yep, that sound good. I would be very glad to help... maybe integrating a nice gui interface on sssad?

Okay, I added some of the GUI stuff for sssad I had already built to the CVS now. Though I'm convinced, that this stuff is better built by every user on his/her own. Why? sssad has the saving completely seperated from the state collecting. You can use sssad to save to textfiles, messages, pool-files, netsend or whatever you choose to use for the actualy saving. IMO it doesn't make sense to completely standardize this area, as saving needs are different.

Anyway included the CVS now are examples how to use sssad in to save to pool, textfile and message boxes.

The problem is that you'll always have to put specific symbol for send and receive pair on gui objects or to link your gui objects with some sssad object... Maybe it could be nice to have gui objects that automatically send their data with a determined symbol like patchname-$1-var_number (with the $1 only for abstractions)

One of my priciples is, that state saving is not tied to GUI elements. One may want to save different things than just the state of a slider, and one may want to not save the state of some sliders. See http://footils.org/cms/show/1 for a longer take on my motivation for this.

But in sssad/gui you can find some examples of GUI elements that are created like [sssad-hslider SAVEME]. They will look like normal sliders, but in fact they are slider-abstraction with graph on parent and "hide object names" enabled. Additionally inside they have a [sssad $1/slider] object already connected.

Of course you cannot directly reach the sliders "Properties" dialog directly anymore, so I don't want to advocate using these directly, they are more intented as an illustration of the idiom. As I wrote above I prefer to let users make their own choices and have their own thoughts, because my way often is wrong and it is so more often for others. ;)

Ciao

Frank Barknecht _ ______footils.org_ __goto10.org__