Thanks for the explanation, Chris. Generally, if there was a JS
function that I needed--I would certainly write it/
use it--performance be damned! Running on these faster modern
machines my concern over JS was probably
slightly silly. Somewhere I'm going to have to write a patch that
takes a "log" of keystrokes and produces an
output file of some sort. Strings would be fine. Does your
("kineme") textWrite patch work under Leopard--
I saw a brief comment about that on the kineme web-site.
thanks again.
aram
On May 13, 2008, at 7:17 PM, Christopher Wright wrote:
A more specific question--is all the Java support and overhead
present when i use QC, even
if I have no use for it?
The support is there, probably lazily loaded (so not really, unless
something makes use of it). memory-wise, the same -- likely not
loaded unless something else touches it. Core Image filters do a
bit with javascript, so that may cause it to get loaded etc.
As for CPU overhead, none at all -- QC doesn't appear to have any
per-frame dependance upon JS aside from the JS patch (a good
thing ;). It's loaded via the ExtraPatches.plugin bundle. with
CoreImage filters, I'm not sure whether or not that's evaluated by
default (I've not profiled/inspected that aspect of filtering) --
but if you make a more elaborate filter function, it's almost
certainly evaluated per-frame. :(
--
[ christopher wright ]
[EMAIL PROTECTED]
http://kineme.net/
_______________________________________________
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]
