[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Securing QC ?

Subject: Securing QC ?
From: Chilton Webb <email@hidden>
Date: Wed, 15 Feb 2006 21:28:37 -0600
Delivered-to: email@hidden
Delivered-to: email@hidden

Hi,

I'm considering writing an app in QC, but I'm concerned that someone could just open it up, yank out the code, and dump it into their own app. Or worse, any attempt to include my registration mechanism in the code could be easily circumvented.

Is there a way to 'secure' a QC composition? If not, is the QC source exposed when embedding it in a Cocoa app?

Thank you,
-Chilton
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden

This email sent to email@hidden

Follow-Ups:
- Re: Securing QC ?
  - From: michael markert <email@hidden>

Prev by Date: Re: Water?
Next by Date: Re: Securing QC ?
Previous by thread: Re: Water?
Next by thread: Re: Securing QC ?
Index(es):
- Date
- Thread

Home