[PD] Re: [PD-announce] pool 0.2.0 - a hierarchical storage object

guenter geiger geiger at xdv.org
Thu Aug 12 11:27:38 CEST 2004


On Thu, 12 Aug 2004, Frank Barknecht wrote:
> > You can do this easily with state using $ arguments for your abstractions.
> > The naming for each state file is name.state where "name" and "state" can
> > be chosen freely.
>
> But can I save the state(s) of a full patch which uses various levels
> of abstractions into a single file using [state]?
>
> > You can even generate all your envelopes with just one envelope
> > abstraction and later handle the setting on a file system level by
> > copying them around , duplicating, renaming and reusing in other
> > abstraction instances.
>
> But isn't this exactly the problem? It forces a user to depend on
> something like the filesystem and its tools and thus is inherently
> platform dependent.

Sorry, I didn't want to convince you to use state. state is dead.
I was just correcting a misconception about state that you had.

You are free to use the above mentioned arguments (which are definitely
valid) to demonstrate the superiority of pool.

Guenter





More information about the Pd-list mailing list