No no, misunderstood.
The plugin polls the OS for available window locations, window IDs,
etc. The idea was to provide a UI via a populated QCPortTypeIndex
menu. However, since the app list, window list, etc, change while the
plugin is running, the thought was to be able to update the menu, and
have that same menu be published to the plugin host application. I
actually had a horrible hack working with NSSharedWorkspace
notifications, but it was far too ugly, but it avoided the 'called
from execution' issue.
I can easily provide that app/window list as a published OUTPUT port,
however, the application host would have to know what to do with that
data, thus forcing the host to be more 'intelligent' than can be
expected. Id wrap the plugin in a macro, but, id still have to,
somewhere, provide an index/menu list as a published input, and change
it...
The ability to alter input ports like that would be very nice, unless
someone could offer a work around.
The 'keep things internal' was referencing the plugin handling
building the menu list, so the host could remain blissfully ignorant.
This is what I have so far: 60fps screen grabbing between various 'new
media' apps is pretty decent, and worth bending some rules for,
no? ;) :)
http://abstrakt.vade.info/?p=171
On Jun 16, 2008, at 2:06 AM, aram wrote:
AFAIK-NO, vade, but then I've only had a chance to just yesterday
read the
initial "QC Plugin" Apple documentation--not the more detailed ones.
I'm enthusiastically awaiting someone on this list to start talking
about
triangulating camera input. I hear there's a guy from Stanford that's
figured out how to place three cameras simultaneously in more than one
plane (unfortunately, it's coach, not a first class plane):-)
In general I'm hoping for a document concerning self-referentiality
(the infinite loop--not the address in Cupertino). I think having a
"protected" repository might help. Any thoughts?
aram
p.s. I found the following statement of yours troubling, I'm a
keyboard man and I
hope any keystrokes I make might actually find their way into a
'plugin'.
That's the primary point of the input ports:-)
Thanks, id really love to keep everything within the plugin, so the
host apps dont have to know a thing, or provide a thing, since, well,
thats the point of a plugin :)
_______________________________________________
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/aram1003%40mac.com
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]
