Scripting Bridge confusion

Question

Note that this is not about scripting "Bridge", the Adobe product, but rather the Mac OS X technology "Scripting Bridge"...*that* has made googling for an answer quite difficult!
Anyway, I'm trying to use Mac's Scripting Bridge technology to do a little bit of control of Photoshop from my Cocoa app.  All I'm really trying to do at this point is to save all files currently open in PS (CS3) as JPEGs with quality = 12.
I've run the 'sdef ... | sdp ...' tool to generate the header for Scripting Bridge.  I get a handle to the application, get all the open documents, and start looping over them using this code:
AdobePhotoshopCS3Application *psApp = [SBApplication applicationWithBundleIdentifier:@"com.adobe.Photoshop"];
SBElementArray *docs = [psApp documents];
NSUInteger index ;
AdobePhotoshopCS3Document *doc, *savedDoc = nil;
AdobePhotoshopCS3JPEGSaveOptions *options = [[[psApp classForScriptingClass:@"JPEG save options"]
                                             alloc] init];
for (index = 0; index < [docs count]; index++) {
  doc = [[docs objectAtIndex:index] get];
I now wish to add in a call to -saveIn:as:copying:appending:withOptions: with options.quality=12;,  but am confused on how to use the options object.  I can create the it just fine, but  I can't set the quality property.  The docs say "Immediately after creating the object, insert it in the appropriate element array. The object is not “viable” in the application until it has been added to its container. Consequently, you cannot set or access its properties until it’s been added."  Add it to what?  Isn't it just a parameter to the -saveIn: method?
Can anyone clear up my confusion on this?
Thanks!
randy

Answer 1

I'm bumping this because I've been looking into this myself.  I've been trying to simply open a file using Scripting Bridge. What it boils down to is that Photoshop really isn't Scripting Bridge-savvy. Here's the deal...
Apple's docs really spell it out like it is. Most classes have a container, which is a mutable array, that they need to be added to before they can be acted upon, as shown in the generated header...
@interface photoshopCS4Application : SBApplication
- (SBElementArray *) documents;
- (SBElementArray *) fonts;
- (SBElementArray *) notifiers;
...and that is the complete list of top-level containers available to us. Because we don't have an array made available to us to store the newly created photoshopCS4OpenOptions object, we can't use the object and by extension can't make a document. Therefore, we can't use the open command in Scripting Bridge. The punchline here is that the same can be said of all the commands that require some kind of options object. Now I'm going to investigate the possibility of just sending an AppleEvent of some kind and bypass Scripting Bridge entirely, but my hopes are dim and I'll have to revert back to Applescript for individual commands.
If I'm wrong (and I'm praying someone will have a way to prove me exactly that), then I will be happy to edit or amend my answer here. And if I could find where to submit a bug report or feature request to Adobe in their voluminous website, I would.