<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for My Coding Life</title>
	<atom:link href="http://blog.johannest.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.johannest.com</link>
	<description>Flash from ActionScript to Z-index.</description>
	<lastBuildDate>Mon, 23 Aug 2010 22:12:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Runtime Font Publisher, a tool for runtime font sharing. by Johannes</title>
		<link>http://blog.johannest.com/2010/06/22/runtime-font-publisher-a-tool-for-runtime-font-sharing/comment-page-1/#comment-336</link>
		<dc:creator>Johannes</dc:creator>
		<pubDate>Mon, 23 Aug 2010 22:12:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.johannest.com/?p=84#comment-336</guid>
		<description>&lt;p&gt;Hi François. Glad you&#039;re getting use out of the tool. The newer version of the tool is using a 3rd party library to read the font information (font family and font subfamily). That library occasionally fails to read certain fonts. If you can identify a font that works in the old version but doesn&#039;t in the new version please fill out a bug here: &lt;a href=&quot;http://code.google.com/p/flash-runtime-font-publisher/issues/list&quot; rel=&quot;nofollow&quot;&gt;http://code.google.com/p/flash-runtime-font-publisher/issues/list&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Please make sure to detail the different publish settings for both versions and it&#039;ll make it easier for me to debug. I&#039;ll take a look at it, and let you know what I can do. Thanks again for your interest in the tool!&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hi François. Glad you&#8217;re getting use out of the tool. The newer version of the tool is using a 3rd party library to read the font information (font family and font subfamily). That library occasionally fails to read certain fonts. If you can identify a font that works in the old version but doesn&#8217;t in the new version please fill out a bug here: <a href="http://code.google.com/p/flash-runtime-font-publisher/issues/list" rel="nofollow">http://code.google.com/p/flash-runtime-font-publisher/issues/list</a></p>
<p>Please make sure to detail the different publish settings for both versions and it&#8217;ll make it easier for me to debug. I&#8217;ll take a look at it, and let you know what I can do. Thanks again for your interest in the tool!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Runtime Font Publisher, a tool for runtime font sharing. by François</title>
		<link>http://blog.johannest.com/2010/06/22/runtime-font-publisher-a-tool-for-runtime-font-sharing/comment-page-1/#comment-335</link>
		<dc:creator>François</dc:creator>
		<pubDate>Mon, 23 Aug 2010 20:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.johannest.com/?p=84#comment-335</guid>
		<description>I love your tool and have been using the CS4 version for a while. I just installed the CS5 one. I welcome the new feature, but this version doesn&#039;t open most of the font installed on my Mac (10.6.3).
I have the Adobe font collection installed but I can only open the OT files. 
With your previous version I was able to open most of them.
Am I missing something? Please advise?
Thanks.
F</description>
		<content:encoded><![CDATA[<p>I love your tool and have been using the CS4 version for a while. I just installed the CS5 one. I welcome the new feature, but this version doesn&#8217;t open most of the font installed on my Mac (10.6.3).<br />
I have the Adobe font collection installed but I can only open the OT files.<br />
With your previous version I was able to open most of them.<br />
Am I missing something? Please advise?<br />
Thanks.<br />
F</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The MovieClip life cycle, Event.FRAME_CONSTRUCTED, and Event.EXIT_FRAME. by The MovieClip life cycle, Event.FRAME_CONSTRUCTED, and Event.EXIT_FRAME. &#171; CODE@蝴蝶。夢</title>
		<link>http://blog.johannest.com/2009/05/22/the-movieclip-life-cycle-event-frame_constructed-and-event-exit_frame/comment-page-1/#comment-332</link>
		<dc:creator>The MovieClip life cycle, Event.FRAME_CONSTRUCTED, and Event.EXIT_FRAME. &#171; CODE@蝴蝶。夢</dc:creator>
		<pubDate>Mon, 09 Aug 2010 10:20:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.johannest.com/?p=23#comment-332</guid>
		<description>[...] http://blog.johannest.com/2009/05/22/the-movieclip-life-cycle-event-frame_constructed-and-event-exit...  Filed under: 編程 Leave a comment     Comments (0) Trackbacks (0) ( subscribe to comments on this post ) [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://blog.johannest.com/2009/05/22/the-movieclip-life-cycle-event-frame_constructed-and-event-exit.." rel="nofollow">http://blog.johannest.com/2009/05/22/the-movieclip-life-cycle-event-frame_constructed-and-event-exit..</a>.  Filed under: 編程 Leave a comment     Comments (0) Trackbacks (0) ( subscribe to comments on this post ) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Unit testing Flash panels within the Flash authoring environment using FlexUnit 4 and Flash Builder. by Tweets that mention My Coding Life – Unit testing Flash panels within the Flash authoring environment using FlexUnit 4 and Flash Builder. -- Topsy.com</title>
		<link>http://blog.johannest.com/2010/07/01/unit-testing-flash-panels-within-the-flash-authoring-environment-using-flexunit-4-and-flash-builder/comment-page-1/#comment-313</link>
		<dc:creator>Tweets that mention My Coding Life – Unit testing Flash panels within the Flash authoring environment using FlexUnit 4 and Flash Builder. -- Topsy.com</dc:creator>
		<pubDate>Thu, 01 Jul 2010 20:01:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.johannest.com/?p=104#comment-313</guid>
		<description>[...] This post was mentioned on Twitter by CT. CT said: Fireworks News: Unit testing Flash panels within the Flash authoring environment using FlexUnit 4 and Flash Builde... http://bit.ly/aAK4FE [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by CT. CT said: Fireworks News: Unit testing Flash panels within the Flash authoring environment using FlexUnit 4 and Flash Builde&#8230; <a href="http://bit.ly/aAK4FE" rel="nofollow">http://bit.ly/aAK4FE</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Unit testing Flash panels within the Flash authoring environment using FlexUnit 4 and Flash Builder. by Michael Labriola</title>
		<link>http://blog.johannest.com/2010/07/01/unit-testing-flash-panels-within-the-flash-authoring-environment-using-flexunit-4-and-flash-builder/comment-page-1/#comment-312</link>
		<dc:creator>Michael Labriola</dc:creator>
		<pubDate>Thu, 01 Jul 2010 17:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.johannest.com/?p=104#comment-312</guid>
		<description>We are actually working on providing support in CS4 and CS5 for FlexUnit to make sure this is really trivial for users to build and run tests from within Flash Authoring. This is a really interesting way to resolve the current workflow though and I like it.

Let me know if you are interested in working with us when we get a little closer to full support with our idea too.

Cheers,
Mike</description>
		<content:encoded><![CDATA[<p>We are actually working on providing support in CS4 and CS5 for FlexUnit to make sure this is really trivial for users to build and run tests from within Flash Authoring. This is a really interesting way to resolve the current workflow though and I like it.</p>
<p>Let me know if you are interested in working with us when we get a little closer to full support with our idea too.</p>
<p>Cheers,<br />
Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Runtime Font Publisher, a tool for runtime font sharing. by My Coding Life &#8211; Unit testing Flash panels within the Flash authoring environment using FlexUnit 4 and Flash Builder.</title>
		<link>http://blog.johannest.com/2010/06/22/runtime-font-publisher-a-tool-for-runtime-font-sharing/comment-page-1/#comment-310</link>
		<dc:creator>My Coding Life &#8211; Unit testing Flash panels within the Flash authoring environment using FlexUnit 4 and Flash Builder.</dc:creator>
		<pubDate>Thu, 01 Jul 2010 08:05:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.johannest.com/?p=84#comment-310</guid>
		<description>[...] a recent project of mine I created an ActionScript 3.0 API for JSFL. The API is used as a communication layer [...]</description>
		<content:encoded><![CDATA[<p>[...] a recent project of mine I created an ActionScript 3.0 API for JSFL. The API is used as a communication layer [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The MovieClip life cycle, Event.FRAME_CONSTRUCTED, and Event.EXIT_FRAME. by イナヅマtvログ &#187; Actionscript3, フレームレートに関係する3つのイベント(Event)</title>
		<link>http://blog.johannest.com/2009/05/22/the-movieclip-life-cycle-event-frame_constructed-and-event-exit_frame/comment-page-1/#comment-294</link>
		<dc:creator>イナヅマtvログ &#187; Actionscript3, フレームレートに関係する3つのイベント(Event)</dc:creator>
		<pubDate>Tue, 08 Jun 2010 15:23:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.johannest.com/?p=23#comment-294</guid>
		<description>[...] 毎フレームごとに発生するEventに関するお話。 元ネタはMy Coding Life – The MovieClip life cycle, Event.FRAME_CONSTRUCTED, and Event.EXIT_FRAME.です。 [...]</description>
		<content:encoded><![CDATA[<p>[...] 毎フレームごとに発生するEventに関するお話。 元ネタはMy Coding Life – The MovieClip life cycle, Event.FRAME_CONSTRUCTED, and Event.EXIT_FRAME.です。 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on On using the [Embed] tag with fontStyle &amp; fontWeight properties. by Keith W</title>
		<link>http://blog.johannest.com/2010/05/19/on-using-the-embed-tag-with-fontstyle-fontweight-properties/comment-page-1/#comment-284</link>
		<dc:creator>Keith W</dc:creator>
		<pubDate>Mon, 24 May 2010 00:43:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.johannest.com/?p=53#comment-284</guid>
		<description>Very informative article.</description>
		<content:encoded><![CDATA[<p>Very informative article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A property list for embedding fonts with the [Emded] metadata tag. by Johannes</title>
		<link>http://blog.johannest.com/2010/01/20/a-property-list-for-embedding-fonts-with-the-emded-metadata-tag/comment-page-1/#comment-278</link>
		<dc:creator>Johannes</dc:creator>
		<pubDate>Thu, 06 May 2010 07:20:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.johannest.com/?p=44#comment-278</guid>
		<description>Hi Karen,
Sorry, I haven&#039;t personally run into issues with multiple OTF files and various weights. For different font weights of a font family, have you tried not including the fontStyle and fontWeight parameters in your embed tag? Still doing some more testing to confirm, but so far when using the Flex 4.0 SDK I&#039;ve noticed that those parameters seem to be only used for system fonts.

Also, I ran into &lt;a href=&quot;http://www.actionscript.org/forums/showthread.php3?t=165106&quot; rel=&quot;nofollow&quot;&gt;this thread&lt;/a&gt; recently. It suggests that OTF files with multiple weights will only work with system fonts. Which I think is a little strange because the &lt;a href=&quot;http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7e09.html&quot; rel=&quot;nofollow&quot;&gt;Adobe documentation&lt;/a&gt; suggests that this was only possible with the CFF font manager that was introduced with the Flex 4 SDK. Still worth a shot!</description>
		<content:encoded><![CDATA[<p>Hi Karen,<br />
Sorry, I haven&#8217;t personally run into issues with multiple OTF files and various weights. For different font weights of a font family, have you tried not including the fontStyle and fontWeight parameters in your embed tag? Still doing some more testing to confirm, but so far when using the Flex 4.0 SDK I&#8217;ve noticed that those parameters seem to be only used for system fonts.</p>
<p>Also, I ran into <a href="http://www.actionscript.org/forums/showthread.php3?t=165106" rel="nofollow">this thread</a> recently. It suggests that OTF files with multiple weights will only work with system fonts. Which I think is a little strange because the <a href="http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7e09.html" rel="nofollow">Adobe documentation</a> suggests that this was only possible with the CFF font manager that was introduced with the Flex 4 SDK. Still worth a shot!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A property list for embedding fonts with the [Emded] metadata tag. by Johannes</title>
		<link>http://blog.johannest.com/2010/01/20/a-property-list-for-embedding-fonts-with-the-emded-metadata-tag/comment-page-1/#comment-277</link>
		<dc:creator>Johannes</dc:creator>
		<pubDate>Wed, 05 May 2010 07:32:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.johannest.com/?p=44#comment-277</guid>
		<description>The cff property name was incorrect. The correct property name to embed a font as a Compact Font Format is embedAsCFF. Using cff as a property would yield the following compile time error using the Flex 4 SDK, &quot;transcoding parameter &#039;cff&#039; is not supported by &#039;flex2.compiler.media.FontTranscoder&#039;.&quot; This post has been updated.</description>
		<content:encoded><![CDATA[<p>The cff property name was incorrect. The correct property name to embed a font as a Compact Font Format is embedAsCFF. Using cff as a property would yield the following compile time error using the Flex 4 SDK, &#8220;transcoding parameter &#8216;cff&#8217; is not supported by &#8216;flex2.compiler.media.FontTranscoder&#8217;.&#8221; This post has been updated.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
