If I wanted to use it, I wouldn't package it; I would load it somehow from
that file path. That's just me.
However, I would really enjoy some clarification on this, as it is truly
ridiculous to have to rely on loading things like this from file path, when
the user may have moved the location. That doesn't really make for a great
user experience, especially when anyone opening the file has OS X and a Mac,
so they should already have the file.

The actual agreement when you install the Developer Tools is probably the
most telling statement published statement about what you can or cannot do,
and the language used is very broad.

If we can't get clarification about using qtz resources like this via this
list, I would be pleased to be informed of the appropriate way to go about
obtaining this information, as it is patently absurd to think about
incurring a lawsuit over a virtual patch that does simple math.

-George Toledo

On Tue, Oct 20, 2009 at 8:33 PM, Keith Lang <[email protected]> wrote:

> Please forgive what might be a silly question;
> What the implications are on releasing commercial software including
> patches that contain an Apple copyright in their description?
>
> "Convert Pixels to Quartz Composer Units.
>
> Copyright: (c) 2003-2009 by Apple, Inc., all rights reserved.
>
> Path: /System/Library/Graphics/Quartz Composer Patches/Pixels to Units.qtz”
>
> Keith.
>  _______________________________________________
> 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/gtoledo3%40gmail.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]

Reply via email to