Comments on: Tip: Tapping into the mx framework for component development http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/ actionscript, flex, flash and other fun stuff Sat, 14 Nov 2009 16:04:03 +0000 http://wordpress.com/ hourly 1 By: Idetrorce http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-3643 Idetrorce Sat, 15 Dec 2007 23:38:17 +0000 http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-3643 very interesting, but I don't agree with you Idetrorce very interesting, but I don’t agree with you
Idetrorce

]]> By: Professional Monkey Keyboard Operator » Blog Archive » Sharing Links Is Good Karma http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-576 Professional Monkey Keyboard Operator » Blog Archive » Sharing Links Is Good Karma Fri, 01 Jun 2007 06:31:02 +0000 http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-576 [...] Adobe’s ActionScript 3.0 Language and Components Reference Adobe’s Flex 2 Language Reference Flex and ActionScript Error Codes Wiki Good, Fast, Cheap Oscar Trelles jwopitz - flex/flash exploration [...] [...] Adobe’s ActionScript 3.0 Language and Components Reference Adobe’s Flex 2 Language Reference Flex and ActionScript Error Codes Wiki Good, Fast, Cheap Oscar Trelles jwopitz – flex/flash exploration [...]

]]> By: An Ugly, Anti-OOP Way to Infiltrate the MX Framework « jwopitz - flex/flash exploration http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-387 An Ugly, Anti-OOP Way to Infiltrate the MX Framework « jwopitz - flex/flash exploration Mon, 14 May 2007 20:23:08 +0000 http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-387 [...] 14th, 2007 You may have remembered a post about tapping into the mx framework awhile back. Basically I was griping about Adobe’s excessive use of private (instead of [...] [...] 14th, 2007 You may have remembered a post about tapping into the mx framework awhile back. Basically I was griping about Adobe’s excessive use of private (instead of [...]

]]> By: Tips (and reckless behaviour) for Component Developers « jwopitz - flex/flash exploration http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-247 Tips (and reckless behaviour) for Component Developers « jwopitz - flex/flash exploration Wed, 25 Apr 2007 21:29:22 +0000 http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-247 [...] Tap into the mx_internal namespace. [...] [...] Tap into the mx_internal namespace. [...]

]]> By: cluebcke http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-90 cluebcke Tue, 03 Apr 2007 21:22:10 +0000 http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-90 Cool post. Inspired me to share an experience I had with needing to use mx_internal, here: http://chrisluebcke.com/2007/04/03/mx_internal-boo/ Might be useful for somebody someday. Cool post. Inspired me to share an experience I had with needing to use mx_internal, here: http://chrisluebcke.com/2007/04/03/mx_internal-boo/

Might be useful for somebody someday.

]]> By: mx_internal... Boo! « Good, Fast, Cheap http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-89 mx_internal... Boo! « Good, Fast, Cheap Tue, 03 Apr 2007 21:12:51 +0000 http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-89 [...] Posted April 3, 2007 A colleague points me to this blog by Justin Wopitz (Maiden Rulezzzz!), a good summary of what the mx_internal namespace is used for. I’ve [...] [EDIT] Not a biggie, but the name is Justin W. Opitz [...] Posted April 3, 2007 A colleague points me to this blog by Justin Wopitz (Maiden Rulezzzz!), a good summary of what the mx_internal namespace is used for. I’ve [...]

[EDIT]
Not a biggie, but the name is Justin W. Opitz

]]> By: jwopitz http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-47 jwopitz Thu, 29 Mar 2007 15:14:50 +0000 http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-47 Thanks for the comment. I have heard of BFPUG but haven't gone to it yet. I plan to someday soon. Also thanks for the tip on namespaces. I didn't know that since I rarely use them, however that makes alot of sense for why it doesn't code hint. Maybe in Flex 3? Thanks for the comment. I have heard of BFPUG but haven’t gone to it yet. I plan to someday soon.

Also thanks for the tip on namespaces. I didn’t know that since I rarely use them, however that makes alot of sense for why it doesn’t code hint. Maybe in Flex 3?

]]> By: Brian http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-46 Brian Thu, 29 Mar 2007 15:09:13 +0000 http://jwopitz.wordpress.com/2007/03/25/tip-tapping-into-the-mx-framework-for-component-development/#comment-46 Just found your blog, lots of good posts on here. I'm not sure if you go to the Boston Flash User Group, but lots of Flex folks there if you're interested. Anyways, as for point #2, the reason for this is actually because Flex Builder doesn't deal correctly with any namespaces. So if you create your own namespace, it won't correctly code-hint for it either. Just found your blog, lots of good posts on here. I’m not sure if you go to the Boston Flash User Group, but lots of Flex folks there if you’re interested. Anyways, as for point #2, the reason for this is actually because Flex Builder doesn’t deal correctly with any namespaces. So if you create your own namespace, it won’t correctly code-hint for it either.

]]>