<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Calling bullshit on a &#8220;resolved&#8221; Flex bug</title>
	<link>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/</link>
	<description>A blog about Adobe Flex</description>
	<pubDate>Fri, 08 Aug 2008 00:55:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: san</title>
		<link>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-76889</link>
		<pubDate>Fri, 25 Apr 2008 13:21:39 +0000</pubDate>
		<guid>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-76889</guid>
					<description>very serious bug.. the response by adobe is definitely bs.. i just upgraded my flex builder and when i recompiled it with the new SDK i see all the UI had just gone whack.. I am using the compatibility flag approach for now, but I really hate doing it this way.. They should seriously reconsider this one again.. 

P.S. all the skins on scalenine including Yahoo!'s skin has stopped working because of this too :/</description>
		<content:encoded><![CDATA[<p>very serious bug.. the response by adobe is definitely bs.. i just upgraded my flex builder and when i recompiled it with the new SDK i see all the UI had just gone whack.. I am using the compatibility flag approach for now, but I really hate doing it this way.. They should seriously reconsider this one again.. </p>
<p>P.S. all the skins on scalenine including Yahoo!&#8217;s skin has stopped working because of this too :/
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ryan Gardner</title>
		<link>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-68645</link>
		<pubDate>Wed, 26 Mar 2008 17:26:16 +0000</pubDate>
		<guid>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-68645</guid>
					<description>Hey - I found this post when searching for something else - but yeah, this bug sucks... I'm the one who reported it in http://bugs.adobe.com/jira/browse/SDK-13012 (And that's my screenshot you're showing there in your blog! :)  )

Yeah, this bug sucked. Glad to know I'm not the only one who feels this way :)</description>
		<content:encoded><![CDATA[<p>Hey - I found this post when searching for something else - but yeah, this bug sucks&#8230; I&#8217;m the one who reported it in <a href="http://bugs.adobe.com/jira/browse/SDK-13012" rel="nofollow">http://bugs.adobe.com/jira/browse/SDK-13012</a> (And that&#8217;s my screenshot you&#8217;re showing there in your blog! <img src='http://dougmccune.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   )</p>
<p>Yeah, this bug sucked. Glad to know I&#8217;m not the only one who feels this way <img src='http://dougmccune.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: david</title>
		<link>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-66638</link>
		<pubDate>Wed, 19 Mar 2008 06:25:10 +0000</pubDate>
		<guid>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-66638</guid>
					<description>sorry,D8TitleWindow function shoud be CTitleWindow</description>
		<content:encoded><![CDATA[<p>sorry,D8TitleWindow function shoud be CTitleWindow
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: david</title>
		<link>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-66637</link>
		<pubDate>Wed, 19 Mar 2008 06:23:44 +0000</pubDate>
		<guid>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-66637</guid>
					<description>package
{
	import flash.display.DisplayObject;
	
	import mx.containers.Canvas;
	import mx.containers.TitleWindow;
	
	public class CTitleWindow extends TitleWindow
	{
		var canvas:Canvas=new Canvas();
		public function D8TitleWindow()
		{
			canvas.x=20;
			canvas.y=30;
			super.addChild(canvas);
		}
		public override function addChild(child:DisplayObject):DisplayObject
		{
			return canvas.addChild(child);
		}
	}
}</description>
		<content:encoded><![CDATA[<p>package<br />
{<br />
	import flash.display.DisplayObject;</p>
<p>	import mx.containers.Canvas;<br />
	import mx.containers.TitleWindow;</p>
<p>	public class CTitleWindow extends TitleWindow<br />
	{<br />
		var canvas:Canvas=new Canvas();<br />
		public function D8TitleWindow()<br />
		{<br />
			canvas.x=20;<br />
			canvas.y=30;<br />
			super.addChild(canvas);<br />
		}<br />
		public override function addChild(child:DisplayObject):DisplayObject<br />
		{<br />
			return canvas.addChild(child);<br />
		}<br />
	}<br />
}
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: dougmccune.com &#187; Blog Archive &#187; My 360&#124;Flex Survey Results - did I offend you?</title>
		<link>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-63878</link>
		<pubDate>Sun, 09 Mar 2008 00:14:49 +0000</pubDate>
		<guid>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-63878</guid>
					<description>[...] The language issue So let&#8217;s get this out in the open: I say fuck and shit a lot. Sometimes this comes through on my blog, but even more so when I actually speak. Given the session feedback I think a lot of people find my use of language refreshing and funny (what am I? a clown?). I like to think my presentations are informal, we all just get to hang out and talk about cool stuff, so since it&#8217;s just like chilling with friends I don&#8217;t censor my language. A lot of the comments in the feedback referenced my use of language in a positive way and said how &#8220;fun&#8221; and &#8220;hilarious&#8221; the session was. I like to think we had a good time and it wasn&#8217;t dry or boring. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The language issue So let&#8217;s get this out in the open: I say fuck and shit a lot. Sometimes this comes through on my blog, but even more so when I actually speak. Given the session feedback I think a lot of people find my use of language refreshing and funny (what am I? a clown?). I like to think my presentations are informal, we all just get to hang out and talk about cool stuff, so since it&#8217;s just like chilling with friends I don&#8217;t censor my language. A lot of the comments in the feedback referenced my use of language in a positive way and said how &#8220;fun&#8221; and &#8220;hilarious&#8221; the session was. I like to think we had a good time and it wasn&#8217;t dry or boring. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Harry</title>
		<link>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-59892</link>
		<pubDate>Wed, 27 Feb 2008 19:52:17 +0000</pubDate>
		<guid>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-59892</guid>
					<description>FYI - I just logged this here:
https://bugs.adobe.com/jira/browse/FB-12157

This bug is different than the one on this blog post because it does not involve borderStyle; it is a new bug that involves borderSkin, which is a much worse bug because borderSkin supersedes the abilities of borderStyle.  Also, this bug only started happening after the bug on this blog post was committed to being fixed.</description>
		<content:encoded><![CDATA[<p>FYI - I just logged this here:<br />
<a href="https://bugs.adobe.com/jira/browse/FB-12157" rel="nofollow">https://bugs.adobe.com/jira/browse/FB-12157</a></p>
<p>This bug is different than the one on this blog post because it does not involve borderStyle; it is a new bug that involves borderSkin, which is a much worse bug because borderSkin supersedes the abilities of borderStyle.  Also, this bug only started happening after the bug on this blog post was committed to being fixed.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Harry</title>
		<link>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-59877</link>
		<pubDate>Wed, 27 Feb 2008 19:12:43 +0000</pubDate>
		<guid>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-59877</guid>
					<description>In Flex 3 public release, you cannot extend Panel in mxml and add children to it when using a custom borderskin.  Panel with a borderSkin is as worthless as a canvas with a background image.  Nothing I do will get the children of a panel to appear in the panel.  I wish I had Flex Beta 3 back, and I wish Adobe never released Flex 3.</description>
		<content:encoded><![CDATA[<p>In Flex 3 public release, you cannot extend Panel in mxml and add children to it when using a custom borderskin.  Panel with a borderSkin is as worthless as a canvas with a background image.  Nothing I do will get the children of a panel to appear in the panel.  I wish I had Flex Beta 3 back, and I wish Adobe never released Flex 3.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Samuel Wan</title>
		<link>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-59450</link>
		<pubDate>Tue, 26 Feb 2008 19:03:02 +0000</pubDate>
		<guid>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-59450</guid>
					<description>I found this post after I got screwed by the change of behavior in the public Flex 3 release.

The Panel skinning implementation is inconsistent with the semantics of what the terms "border", "fill", "padding", and "content" really mean. The current implementation confuses "border" with padding, and it confuses "content" with "component chrome".

In general though, I love the simplicity of the Flex framework. Nice job.</description>
		<content:encoded><![CDATA[<p>I found this post after I got screwed by the change of behavior in the public Flex 3 release.</p>
<p>The Panel skinning implementation is inconsistent with the semantics of what the terms &#8220;border&#8221;, &#8220;fill&#8221;, &#8220;padding&#8221;, and &#8220;content&#8221; really mean. The current implementation confuses &#8220;border&#8221; with padding, and it confuses &#8220;content&#8221; with &#8220;component chrome&#8221;.</p>
<p>In general though, I love the simplicity of the Flex framework. Nice job.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ScaleNine Blog &#187; Blog Archive &#187; ScaleNine Themes and Flex 3</title>
		<link>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-58187</link>
		<pubDate>Thu, 21 Feb 2008 23:07:15 +0000</pubDate>
		<guid>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-58187</guid>
					<description>[...] I&#8217;ve been getting emails regarding some of the themes featured on ScaleNine not working properly with Flex 3. There have been some changes to the framework that have caused this, like Panel changes and name changes for some styles. However, there are things that were added to Flex 3 that you can take advantage of now, like iconColor and popUpIcon to further customize an app. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I&#8217;ve been getting emails regarding some of the themes featured on ScaleNine not working properly with Flex 3. There have been some changes to the framework that have caused this, like Panel changes and name changes for some styles. However, there are things that were added to Flex 3 that you can take advantage of now, like iconColor and popUpIcon to further customize an app. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: thibaud</title>
		<link>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-46020</link>
		<pubDate>Thu, 17 Jan 2008 19:18:07 +0000</pubDate>
		<guid>http://dougmccune.com/blog/2008/01/12/calling-bullshit-on-a-resolved-flex-bug/#comment-46020</guid>
					<description>After spending 2 full days making my flex 2 app looking half decent when compiled in plain flex 3 (who would want to use that compatibility flag), i feel like I should add my rant to it.

flex team, I love you too,(for real) but please, get the containers style together, the whole panel skin and border is... a mess, it has a great potential and flexibility with good ideas, that just needs to be streamlined.

Panels and border types are the raw material of all flex ui designer. and yet that part is probably the most obscure part of flex at the moment.

I really believe the panel styling (through borders types or anything) deserve much more than a "hack" to make them half "working" or backward compatible. As a Flex lover, I was really hopping to see them evolve into a strong and flexible styling base for ui designers.</description>
		<content:encoded><![CDATA[<p>After spending 2 full days making my flex 2 app looking half decent when compiled in plain flex 3 (who would want to use that compatibility flag), i feel like I should add my rant to it.</p>
<p>flex team, I love you too,(for real) but please, get the containers style together, the whole panel skin and border is&#8230; a mess, it has a great potential and flexibility with good ideas, that just needs to be streamlined.</p>
<p>Panels and border types are the raw material of all flex ui designer. and yet that part is probably the most obscure part of flex at the moment.</p>
<p>I really believe the panel styling (through borders types or anything) deserve much more than a &#8220;hack&#8221; to make them half &#8220;working&#8221; or backward compatible. As a Flex lover, I was really hopping to see them evolve into a strong and flexible styling base for ui designers.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
