It sounds like we're all wanting about the same thing here.
Here is what I'm thinking:
You could create an NSMutableArray where each element corresponds to
one preset.
Each element (preset) contains an NSDictionary of parms. (name-value
pairs).
I believe you can use the serialization hooks to store and retrieve
the NSMutableArray, but I'm not sure exactly what that would look
like, syntax-wise.
(examples, anyone?)
I want to be able to edit the presets using the settings pane.
The first "setting" would be the preset number.
Whenever that changes, you'd have to get the system to let you know
so that you could load the new preset into the other fields of the
settings pane.
***This is one thing that I'm not sure is possible*** but it seems
like it should be doable by overriding the correct function. (hmmm -
I suppose I could simply "cache and compare - that should work")
Side note: there is still a lot of mystery for me in this environment
- there's a lot of stuff going on automatically under the hood. It'd
be great if someone could point me to documentation on exactly what
is done by:
@dynamic
@synthesize
Interface Builder
QC - in relation to loading and running of plugins
Otherwise, I'll have to keep re-reading the docs and playing around
with this stuff until it flies.
Anyways, I was thinking that the output could be a struct containing
all the parms... a "parameter buss" if you will.
Then, it would be cool to be able to change the number of parameters
per preset at runtime with one of those little +/- boxes, and enter
the parameter names as a field in the settings pane.
My first problem is getting *anything* to show up in the settings
pane (per previous email).
Jack
On Dec 18, 2007, at Dec 18, 2007 | 1:36 PM, Alex Drinkwater wrote:
Hi,
I've been looking at the the compositions mentioned in
this thread.
I notice both Jelly and Arabesque have JavaScript
patches containing 'hard-wired' presets. This isn't
quite what I was after- what I really wanted is a way
to temporarily save the current settings of the
composition into one of a number of 'Memory
Locations'. Having said that, I can see that having a
number of hard-coded presets could also be useful.
I'm intrigued by the idea of creating a
preset-management plugin. I've been working up to
creating a few of my own custom QC objects myself.
Long way to go though, as I've only just started my
'Beginning MacOS X Programming' book ;)
I'm not sure how it would be possible to save presets
with the composition, however, unless they can somehow
be written on-the-fly into the file as
meta-information. The ideal might be to be able to
write presets into an XML file in
~/Library/Preferences.
alx
--- Alessandro Sabatelli <[EMAIL PROTECTED]> wrote:
It's more or less the same as the one found in
Arabesque though it
will output a formatted string of the current
inputs. This is needed
because you have to add presets manually, as
JavaScript cannot save
data within the composition. A plugin would be very
helpful in this
case.
.xX
On Dec 18, 2007, at 11:51 AM, Jack Hayward wrote:
I haven't had time to read through all these
mails, but ...
Have you guys seen the preset manager in the
"Jelly" composition?
It's in System/Library/Compositions/
J
_______________________________________________
Do not post admin requests to the list. They will be
ignored.
Quartzcomposer-dev mailing list
([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/the_voder%
40yahoo.co.uk
This email sent to [EMAIL PROTECTED]
__________________________________________________________
Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-
[EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/
jack.hayward%40comcast.net
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
