<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Tips From The Masters</title>
<link>http://mx.sys-con.com/</link>
<description>Latest articles from Tips From The Masters</description>
<copyright>Copyright 2008 ADOBE FLEX JOURNAL</copyright>
<lastBuildDate>Sat, 05 Jul 2008 11:35:00 GMT</lastBuildDate>
<generator>ADOBE FLEX JOURNAL</generator>
<ttl>10</ttl>
<docs>http://backend.userland.com/rss</docs>

<item>
<title>Adding Enum Support to Adobe Flex AMF Protocol</title>
<guid isPermaLink="true">http://mx.sys-con.com/read/429520.htm</guid><link>http://mx.sys-con.com/read/429520.htm</link>
<pubDate>Mon, 17 Sep 2007 13:15:00 GMT</pubDate>
<description>Flex has a short learning curve for Java developers, who will find that there are a lot of familiar language constructs and patterns. It also provides excellent remoting capabilities for Java programmers, allowing transparent data transfer between ActionScript and Java 1.4 data types. With Java version 5 and above in production for a while now you have a lot of Java data structures that use enum and need marshaling to/from the Flex applications. This article provides a working example of the ActionScript language extension for an enum data type.</description>

</item><item>
<title>Job Interviews: Adobe Flex and Flash Career Guidance</title>
<guid isPermaLink="true">http://mx.sys-con.com/read/381044.htm</guid><link>http://mx.sys-con.com/read/381044.htm</link>
<pubDate>Wed, 15 Aug 2007 12:45:00 GMT</pubDate>
<description>Some things that I learned early in my career that originally helped me succeed, I believe are now hurting me in job interviews. One of the pros to typing via dynamic languages and forgiving compilers such as ActionScript 1.0, Ruby, JavaScript, and others is that you can quickly code things that work. In a lot of the early agency, multimedia, and small software company work that I did, these technologies were great. They didn&apos;t get in your way, and they empowered you to quickly create programmatic solutions that were enhanced or even driven by good designers. You could hit insane deadlines, recompile changes quickly for a client, and react flexibly to ever-changing, almost fluid requirements...if any.</description>

</item><item>
<title>Multiple Inheritance in ActionScript 3.0</title>
<guid isPermaLink="true">http://mx.sys-con.com/read/316359.htm</guid><link>http://mx.sys-con.com/read/316359.htm</link>
<pubDate>Wed, 20 Dec 2006 13:00:00 GMT</pubDate>
<description>Did you know ActionScript 3.0 supports multiple inheritance? Here&apos;s how... Multiple inheritance is actually possible with AS3, despite popular belief that it&apos;s not supported. It&apos;s not really multiple inheritance in the true sense of the word going by the strict definition... but there&apos;s a way to get the job done in AS3 that behaves almost like the real thing.</description>

</item><item>
<title>Passing parameters to Flex that works</title>
<guid isPermaLink="true">http://mx.sys-con.com/read/283888.htm</guid><link>http://mx.sys-con.com/read/283888.htm</link>
<pubDate>Thu, 12 Oct 2006 07:30:00 GMT</pubDate>
<description>The subject of this piece is how to pass parameters from HTML to a Flex 2 application using flashVars parameters.</description>

</item><item>
<title>ActionScript 3: Dynamic classes</title>
<guid isPermaLink="true">http://mx.sys-con.com/read/279512.htm</guid><link>http://mx.sys-con.com/read/279512.htm</link>
<pubDate>Tue, 03 Oct 2006 07:15:00 GMT</pubDate>
<description>In Java, if you&apos;ve created an object from a particular class, you can use only properties and methods that were defined in this class. This is not the case in ActionScript 3. This is one of the examples of unusual (from the OOP perspective) programming techniques.</description>

</item><item>
<title>Extending Adobe Flex with Flash</title>
<guid isPermaLink="true">http://mx.sys-con.com/read/274849.htm</guid><link>http://mx.sys-con.com/read/274849.htm</link>
<pubDate>Thu, 21 Sep 2006 14:45:00 GMT</pubDate>
<description>While a large Flex application is loaded, the user may experience unpleasant delays, which can be used productively to logon to this application. Besides, it&apos;ll give the user  perception that your application loads faster.</description>

</item><item>
<title>Code Reuse - Pros and Cons</title>
<guid isPermaLink="true">http://mx.sys-con.com/read/247611.htm</guid><link>http://mx.sys-con.com/read/247611.htm</link>
<pubDate>Mon, 17 Jul 2006 10:15:00 GMT</pubDate>
<description>Depending on the scope of your project, you may have the opportunity for code reuse. The reasons you might want to do so are two-fold. First, you reduce duplication of efforts. If you have already created a hyperlink enabled CellRenderer for your DataGrid once, why do it again? Second, you create, or build upon, an ever growing utility code base. While it may not be in the &apos;utils&apos; package per se, you&apos;ll soon end up with re-usable events, common GUI controls and widgets, and yes even utility classes. Whether by merely being in a different folder means the client doesn&apos;t own it is up to you or your sales team.</description>

</item></channel></rss>