September 2007 - Pro-apps-dev

Re: FxTexture & QCRenderer
by Darrin Cardani 17 Sep '07

17 Sep '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FXPlug encode in XML
by Dave Howell 17 Sep '07

17 Sep '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Rainer. Dave On Sep 17, 2007, at 9:53 AM, Rainer Standke wrote: Hello, Is this a known phenomenon? Thanks, _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This is expected. We use the UUID of the plug-in because it is not language dependent. "Soft Focus" is the "display name" of the FxPlug. "BE1A5748_322A_4D25_8107_F3961E0BC21A" is its UUID. That way, if two plug-in vendors create something called "Soft Focus," you'll get the right one when you open your project. And if you open it while running, say, in French, it will still find the plug-in (although its display name will be something a little more French then). it seems to that FXPlugs are encoded in a somewhat peculiar way in their effectid tags. Here is what I find instead of the expected "Soft Focus": "FxPlugWrapper:BE1A5748_322A_4D25_8107_F3961E0BC21A". Rainer This email sent to site_archiver(a)lists.apple.com

1 0

Re: FXPlug encode in XML - take 2
by Patrick Sheffield 17 Sep '07

17 Sep '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=B9ctcbAGmx13MXsZevwiresUwe/p4Y61IGLLTS/aoB8qc/hbWX6Rxn8RQlYzBCDz; h=Received:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer:X-ELNK-Trace:X-Originating-IP; Dunno why this didn't go the the list... On Sep 16, 2007, at 7:50 PM, Patrick Sheffield wrote: Patrick On Sep 16, 2007, at 7:21 PM, Rainer Standke wrote: Rainer Hello, Is this a known phenomenon? Thanks, _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I may be wrong, but I believe that FxPlug plugins are referred to by their UUID as opposed to their ASCII name. I should have mentioned I'm talking about XML exports from Final Cut Pro. it seems to that FXPlugs are encoded in a somewhat peculiar way in their effectid tags. Here is what I find instead of the expected "Soft Focus": "FxPlugWrapper:BE1A5748_322A_4D25_8107_F3961E0BC21A". Rainer _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/psheffield% 40earthlink.net This email sent to psheffield(a)earthlink.net This email sent to site_archiver(a)lists.apple.com

1 0

Re: FXPlug encode in XML - take 2
by Steve Christensen 17 Sep '07

17 Sep '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Sep 16, 2007, at 7:21 PM, Rainer Standke wrote: Rainer Hello, steve _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I should have mentioned I'm talking about XML exports from Final Cut Pro. it seems to that FXPlugs are encoded in a somewhat peculiar way in their effectid tags. Here is what I find instead of the expected "Soft Focus": "FxPlugWrapper:BE1A5748_322A_4D25_8107_F3961E0BC21A". Is this a known phenomenon? Just a guess, but the last part looks like a UUID, which is how effects are uniquely identified. If you're exporting, it seems more reasonable to specify an effect via its [unique] UUID rather than a localized effect name since that could conflict with another effect. This email sent to site_archiver(a)lists.apple.com

1 0

FXPlug encode in XML - take 2
by Rainer Standke 17 Sep '07

17 Sep '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Rainer Hello, Is this a known phenomenon? Thanks, Rainer _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I should have mentioned I'm talking about XML exports from Final Cut Pro. it seems to that FXPlugs are encoded in a somewhat peculiar way in their effectid tags. Here is what I find instead of the expected "Soft Focus": "FxPlugWrapper:BE1A5748_322A_4D25_8107_F3961E0BC21A". This email sent to site_archiver(a)lists.apple.com

1 0

FXPlug encode in XML
by Rainer Standke 17 Sep '07

17 Sep '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hello, Is this a known phenomenon? Thanks, Rainer _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… it seems to that FXPlugs are encoded in a somewhat peculiar way in their effectid tags. Here is what I find instead of the expected "Soft Focus": "FxPlugWrapper:BE1A5748_322A_4D25_8107_F3961E0BC21A". This email sent to site_archiver(a)lists.apple.com

1 0

FxTexture & QCRenderer
by Christoph Vonrhein 17 Sep '07

17 Sep '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: versioning Unix executables on MacOSX
by Steve Christensen 15 Sep '07

15 Sep '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Sep 14, 2007, at 9:58 AM, Darrin Cardani wrote: On Sep 14, 2007, at 3:38 AM, Valentin Dan wrote: steve _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… Is there some way to add version information to Unix executable files similar to the regular “Applications.app” ? I don't think so. Traditionally command-line apps accept a command- line argument such as "-v" to display version information. But I don't think there's any way to have that information show up in the Finder, since your application isn't a bundle. You might be able to add an old-style 'vers' resource to it. I've never tried that, though. Unix executables show up in the Finder without any "Apple-style" version information because they don't contain any in the usual places that the Finder looks. As Darrin mentioned, there are two ways to provide version info: bundling and adding a version resource. Neither of these is really a great match for a Unix executable, though. In the bundle case, your actual executable has to be buried within an appropriately-constructed folder hierarchy that conforms to the Mac's bundle requirements. In the 'vers' resource case, your executable would reside in the file's data fork and the 'vers' resource in the corresponding resource fork, and even then I'm not sure if the Finder would think to look there for a Unix executable (I've never tried). Plus, the resource fork can easily get stripped off if you move the executable to a non-HFS file system volume, or archive it via a non-Mac resource fork aware archiving mechanism. This email sent to site_archiver(a)lists.apple.com

1 0

Re: versioning Unix executables on MacOSX
by Darrin Cardani 14 Sep '07

14 Sep '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

versioning Unix executables on MacOSX
by Valentin Dan 14 Sep '07

14 Sep '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-index: Acf2u1Z9Ml81I/TSTmuhLrkdKtkOrg== Thread-topic: versioning Unix executables on MacOSX _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0