First off, I would like to say that OFC is a great piece of work. So much so that we're thinking of integrating it with one of our Flex applications. The difficulty we have is that OFC was not designed to be used inside another application. The two main issues are (1) it sizes itself to the full size of the stage and (2) event handlers attempt to call Javascript methods via ExternalInterface.
The approach I'm taking right now is to have our app load the OFC swf at runtime. This won't work out-of-the-box so I've already begun making some changes to allow for this. Basically, OFC needs to be aware of when it's been loaded by another swf. Once it knows this, it can then:
(1) Accept width/height values from the parent and size itself accordingly
(2) Dispatch events to the parent instead of calling out via ExternalInterface
Alternatively, another approach I had thought of was to turn OFC into an AS3 component of sorts. This way it can be linked into an application instead of being loaded at runtime. This will require quite a bit more work, so I've decided against it for now. However, I believe this component approach is the cleanest in the long run.
Like I said, I've already begun work in this area (in an R&D fashion) and have a working prototype. My question is whether there is any interest in adding this as a general feature to OFC?
Thanks,
Jason
