<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Carbon: How to print to PDF</title>
	<atom:link href="http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/</link>
	<description>i saw that</description>
	<pubDate>Fri, 05 Dec 2008 09:23:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Andy</title>
		<link>http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1105</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Sat, 02 Dec 2006 21:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1105</guid>
		<description>No, the Cocoa route simply wasn't viable then. Now, you can mix and match Cocoa and Carbon windows, but then it wasn't possible. That meant the transition from Carbon to Cocoa would have to be total, and simply wasn't feasible economically or timewise.

These days, I would recommend adding Cocoa windows for new features (instead of using Carbon windows), for the apps that could handle that. However, because of internal framework architectures, some applications wouldn't be able to even take advantage of that. Their framework would dictate an entire transition to Cocoa, which is questionable, even with Adobe's resources.

Futhermore, some internal frameworks are too low level to sit on top of Cocoa, so from a technical standpoint, aren't feasible.</description>
		<content:encoded><![CDATA[<p>No, the Cocoa route simply wasn&#8217;t viable then. Now, you can mix and match Cocoa and Carbon windows, but then it wasn&#8217;t possible. That meant the transition from Carbon to Cocoa would have to be total, and simply wasn&#8217;t feasible economically or timewise.</p>
<p>These days, I would recommend adding Cocoa windows for new features (instead of using Carbon windows), for the apps that could handle that. However, because of internal framework architectures, some applications wouldn&#8217;t be able to even take advantage of that. Their framework would dictate an entire transition to Cocoa, which is questionable, even with Adobe&#8217;s resources.</p>
<p>Futhermore, some internal frameworks are too low level to sit on top of Cocoa, so from a technical standpoint, aren&#8217;t feasible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Stevenson</title>
		<link>http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1066</link>
		<dc:creator>Scott Stevenson</dc:creator>
		<pubDate>Thu, 30 Nov 2006 08:57:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1066</guid>
		<description>&lt;i&gt;The interesting story behind this was, at the start of Mac OS X 10.0, Apple actually trying to get Macromedia to port their applications to Cocoa&lt;/i&gt;

If you were given the chance to go back in time with everything you know now, would you try to convince the Macromedia folks to just go the Cocoa route?</description>
		<content:encoded><![CDATA[<p><i>The interesting story behind this was, at the start of Mac OS X 10.0, Apple actually trying to get Macromedia to port their applications to Cocoa</i></p>
<p>If you were given the chance to go back in time with everything you know now, would you try to convince the Macromedia folks to just go the Cocoa route?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Anguish</title>
		<link>http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1057</link>
		<dc:creator>Scott Anguish</dc:creator>
		<pubDate>Wed, 29 Nov 2006 20:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1057</guid>
		<description>Interesting... that search does now bring up another set of links (the first one is the same, but the second is different)

So I tried "Save as PDF Carvon" in Xcode... second link is still the right document, with the example code.</description>
		<content:encoded><![CDATA[<p>Interesting&#8230; that search does now bring up another set of links (the first one is the same, but the second is different)</p>
<p>So I tried &#8220;Save as PDF Carvon&#8221; in Xcode&#8230; second link is still the right document, with the example code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1054</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 29 Nov 2006 18:46:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1054</guid>
		<description>&lt;i&gt;But the first 499k lines just setup the main window&lt;/i&gt;

The interesting story behind this was, at the start of Mac OS X 10.0, Apple actually trying to get Macromedia to port their applications to Cocoa. At least, that's what some of the Apple reps were telling some of the Macromedia engineers.

I'm not sure if that was an official direction Apple was going in, but talking to the engineers about it seems like the last thing you want to do in that situation. They're the ones who know how much work it would be to make it happen. 

Of course, sometimes Apple seems oblivious to how much work something is going to be when they really want it. There was that one time they were wanting Spotlight plugins... oy.</description>
		<content:encoded><![CDATA[<p><i>But the first 499k lines just setup the main window</i></p>
<p>The interesting story behind this was, at the start of Mac OS X 10.0, Apple actually trying to get Macromedia to port their applications to Cocoa. At least, that&#8217;s what some of the Apple reps were telling some of the Macromedia engineers.</p>
<p>I&#8217;m not sure if that was an official direction Apple was going in, but talking to the engineers about it seems like the last thing you want to do in that situation. They&#8217;re the ones who know how much work it would be to make it happen. </p>
<p>Of course, sometimes Apple seems oblivious to how much work something is going to be when they really want it. There was that one time they were wanting Spotlight plugins&#8230; oy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1053</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 29 Nov 2006 18:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1053</guid>
		<description>This will teach me to post about not being able to find documentation. Or maybe it will teach me to whine about it &lt;i&gt;before&lt;/i&gt; I find it, that way someone does the work for me.

I actually did try google several times. I even now just tried "Save as PDF File Carbon Mac OS X", and none of the links on the first page show how to programmatically print to a PDF file. The &lt;a href="http://developer.apple.com/documentation/MacOSX/Conceptual/OSX_Technology_Overview/SystemTechnology/chapter_4_section_3.html#//apple_ref/doc/uid/TP40001067-CH207-TPXREF159" rel="nofollow"&gt;second link&lt;/a&gt; just seems to mention that it's possible  (as does the first link), but with no links or discussion on how it's actually done. Maybe I'm missing something obvious here?

I will admit that I was able to find the "Saving a Document as a PDF file" page after it was mentioned, and it was quite useful and documented the necessary API. However, I was only able to find it by searching for the API, PMSessionSetDestination.</description>
		<content:encoded><![CDATA[<p>This will teach me to post about not being able to find documentation. Or maybe it will teach me to whine about it <i>before</i> I find it, that way someone does the work for me.</p>
<p>I actually did try google several times. I even now just tried &#8220;Save as PDF File Carbon Mac OS X&#8221;, and none of the links on the first page show how to programmatically print to a PDF file. The <a href="http://developer.apple.com/documentation/MacOSX/Conceptual/OSX_Technology_Overview/SystemTechnology/chapter_4_section_3.html#//apple_ref/doc/uid/TP40001067-CH207-TPXREF159" rel="nofollow">second link</a> just seems to mention that it&#8217;s possible  (as does the first link), but with no links or discussion on how it&#8217;s actually done. Maybe I&#8217;m missing something obvious here?</p>
<p>I will admit that I was able to find the &#8220;Saving a Document as a PDF file&#8221; page after it was mentioned, and it was quite useful and documented the necessary API. However, I was only able to find it by searching for the API, PMSessionSetDestination.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Stevenson</title>
		<link>http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1048</link>
		<dc:creator>Scott Stevenson</dc:creator>
		<pubDate>Wed, 29 Nov 2006 09:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1048</guid>
		<description>&lt;i&gt;I can’t figure out how to do something in Carbon, I should just port this 500kloc+ application to Cocoa&lt;/i&gt;

But the first 499k lines just setup the main window.</description>
		<content:encoded><![CDATA[<p><i>I can’t figure out how to do something in Carbon, I should just port this 500kloc+ application to Cocoa</i></p>
<p>But the first 499k lines just setup the main window.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Anguish</title>
		<link>http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1036</link>
		<dc:creator>Scott Anguish</dc:creator>
		<pubDate>Tue, 28 Nov 2006 08:11:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1036</guid>
		<description>I did a quick google search on

Save as PDF File Carbon Mac OS X


and the chapter with the example code was the second link. The first was the porting guide for Windows (which also covers this, although lacks the source and specific wording, but does point to the Carbon Printing Manager book).</description>
		<content:encoded><![CDATA[<p>I did a quick google search on</p>
<p>Save as PDF File Carbon Mac OS X</p>
<p>and the chapter with the example code was the second link. The first was the porting guide for Windows (which also covers this, although lacks the source and specific wording, but does point to the Carbon Printing Manager book).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Anguish</title>
		<link>http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1035</link>
		<dc:creator>Scott Anguish</dc:creator>
		<pubDate>Tue, 28 Nov 2006 08:03:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.losingfight.com/blog/2006/11/27/carbon-how-to-print-to-pdf/#comment-1035</guid>
		<description>PMSessionSetDestination is documented in the Printing Manager doc - and it appears to have been since 2002. And the same documentation file discusses both PDF and saving to a file.
Heck, there is even a chapter in the book "Supporting Printing in Your Carbon Application" called "Saving a Document as a PDF File". I'm not sure how much easier to find  that could be. And seems to have been there for quite a while as well according to the Revision History</description>
		<content:encoded><![CDATA[<p>PMSessionSetDestination is documented in the Printing Manager doc - and it appears to have been since 2002. And the same documentation file discusses both PDF and saving to a file.<br />
Heck, there is even a chapter in the book &#8220;Supporting Printing in Your Carbon Application&#8221; called &#8220;Saving a Document as a PDF File&#8221;. I&#8217;m not sure how much easier to find  that could be. And seems to have been there for quite a while as well according to the Revision History</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.395 seconds -->
