I'd like to add my vote for the return of this feature.
Surely if someone really wanted to use a quartz composition to
intentionally crash computers they could use any number of other
techniques using maliciously coded javascript or core image kernal
patches?
I agree with Roger that there is a difference between running a qtz
file in QuickTime Player and in QC or a custom built application and
this could be reflected in security related permissions and
functionality (as it already is in the case of RSS etc), but being
able to run a composition in another composition and then export as a
playable QuickTime movie to encode for dvd/video/tv is such a
valuable feature I've come to rely on I'd hate to see it stay missing.
Dave
On 19/07/2006, at 8:37 PM, Roger Bolton wrote:
what about allowing different functions when qc is running inside
qc player or as standalone
or in an application?
that really didn't come out very clearly.
want I meant was, the qc engine in the quicktime player or when
running through quicktime in
an application can be sandboxed.
when qc is used directly in an application it should allow more
freedom to access the operating
system, because then as a developer you should know what you are
doing and the potential
security issues (i hope).
Roger
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-
email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/dpwolf%
40mac.com
