Flex Monkey Patches » Flex http://blog.flexmonkeypatches.com Mon, 14 Dec 2009 17:17:31 +0000 http://wordpress.org/?v=2.8.6 en hourly 1 Troubleshooting network calls from the client-side in Flex using mx:TraceTarget http://blog.flexmonkeypatches.com/2009/12/09/troubleshooting-network-calls-from-the-client-side-in-flex-using-mxtracetarget/ http://blog.flexmonkeypatches.com/2009/12/09/troubleshooting-network-calls-from-the-client-side-in-flex-using-mxtracetarget/#comments Wed, 09 Dec 2009 23:21:41 +0000 Kyle http://blog.flexmonkeypatches.com/?p=460 Here are some tips on troubleshooting from the client side, data request issues via network calls that may be failing for you:

In main the flex application add the TraceTarget component which will log client side networking calls (in and out) to the flashlog.txt

Basically just add this to your flex app anywhere in the main mxml page:

Then when you run the flex app, if you are running in the debug Flash Player (which you can check here: http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_15507), you will generate info in the flashlog.txt (which on windows should be located here: C:\Documents and Settings\{username}\Application Data\Macromedia\Flash Player\Logs\)

If you don’t have the debug Flash Player you can get it from here:
http://www.adobe.com/support/flashplayer/downloads.html

(Note you can upgrade to a higher version# of the flash player, but if you are trying to install debug player with the same version number over top of the release player, that won’t work. You’ll have to uninstall the Flash Player first. The uninstaller can be found here:
http://kb2.adobe.com/cps/141/tn_14157.html)

More info on flashlog.txt:
http://livedocs.adobe.com/flex/3/html/logging_04.html
(including where to find the flashlog.txt on other platforms.)
More info on TraceTarget:
http://livedocs.adobe.com/flex/3/html/logging_09.html

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> Here are some tips on troubleshooting from the client side, data request issues via network calls that may be failing for you:

In main the flex application add the TraceTarget component which will log client side networking calls (in and out) to the flashlog.txt

Basically just add this to your flex app anywhere in the main mxml page:

Then when you run the flex app, if you are running in the debug Flash Player (which you can check here: http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_15507), you will generate info in the flashlog.txt (which on windows should be located here: C:\Documents and Settings\{username}\Application Data\Macromedia\Flash Player\Logs\)

If you don’t have the debug Flash Player you can get it from here:
http://www.adobe.com/support/flashplayer/downloads.html

(Note you can upgrade to a higher version# of the flash player, but if you are trying to install debug player with the same version number over top of the release player, that won’t work. You’ll have to uninstall the Flash Player first. The uninstaller can be found here:
http://kb2.adobe.com/cps/141/tn_14157.html)

More info on flashlog.txt:
http://livedocs.adobe.com/flex/3/html/logging_04.html
(including where to find the flashlog.txt on other platforms.)
More info on TraceTarget:
http://livedocs.adobe.com/flex/3/html/logging_09.html

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> http://blog.flexmonkeypatches.com/2009/12/09/troubleshooting-network-calls-from-the-client-side-in-flex-using-mxtracetarget/feed/ 0 Getting the version of the Flex SDK that was used to compile a SWC http://blog.flexmonkeypatches.com/2009/02/25/getting-the-version-of-the-flex-sdk-that-was-used-to-compile-a-swc/ http://blog.flexmonkeypatches.com/2009/02/25/getting-the-version-of-the-flex-sdk-that-was-used-to-compile-a-swc/#comments Wed, 25 Feb 2009 15:02:48 +0000 Kyle http://blog.flexmonkeypatches.com/?p=407 I am not sure if this is common knowledge. I googled and didn’t find any other reference to it. (At least not in 10 minutes of googling.)

I wasn’t sure this was possible, but then I decided to look in the Flex bugbase. This is what I found:

https://bugs.adobe.com/jira/browse/SDK-5308

Whaddaya know? An enhancement request that I logged that had actually addressed this issue back in the Flex 2.x days.

Basically if you change the extension of a swc to .zip, you can open the archive with winzip (or similar) and look at the top of the catalog.xml file. You should see something like this:

<?xml version="1.0" encoding ="utf-8"?>
<swc xmlns="http://www.adobe.com/flash/swccatalog/9">
  <versions>
    <swc version="1.2" />
    <flex version="3.2.0" build="3958" />
  </versions>
 

Hopefully this will help some folks out.

Incidentally such a thing does not exist for compiled swfs. There is an enhancement request:
https://bugs.adobe.com/jira/browse/SDK-14042

If you think such a thing would be valuable, please vote for the bug.

And one more thing…I actually had an AIR app back in the pre-release of AIR 1.0 days:
http://blog.flexmonkeypatches.com/2007/11/12/flex-sdk-fds-lcds-version-detection-adobe-air-application/

You could point it at a fds/lcds war or sdk directory and it would tell you the version (of LCDS and the SDK).
Maybe this should be resurrected and updated to AIR 1.5.1 and to use this new version info (at least new since I built the original AIR app). It could also be enhanced to read version info from individual swcs as well. Oh and maybe allow users to drag and drop directories, or wars or swcs onto the app to read the info. Hmmm….if only I had the time.

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> I am not sure if this is common knowledge. I googled and didn’t find any other reference to it. (At least not in 10 minutes of googling.)

I wasn’t sure this was possible, but then I decided to look in the Flex bugbase. This is what I found:

https://bugs.adobe.com/jira/browse/SDK-5308

Whaddaya know? An enhancement request that I logged that had actually addressed this issue back in the Flex 2.x days.

Basically if you change the extension of a swc to .zip, you can open the archive with winzip (or similar) and look at the top of the catalog.xml file. You should see something like this:

<?xml version="1.0" encoding ="utf-8"?>
<swc xmlns="http://www.adobe.com/flash/swccatalog/9">
  <versions>
    <swc version="1.2" />
    <flex version="3.2.0" build="3958" />
  </versions>
 

Hopefully this will help some folks out.

Incidentally such a thing does not exist for compiled swfs. There is an enhancement request:
https://bugs.adobe.com/jira/browse/SDK-14042

If you think such a thing would be valuable, please vote for the bug.

And one more thing…I actually had an AIR app back in the pre-release of AIR 1.0 days:
http://blog.flexmonkeypatches.com/2007/11/12/flex-sdk-fds-lcds-version-detection-adobe-air-application/

You could point it at a fds/lcds war or sdk directory and it would tell you the version (of LCDS and the SDK).
Maybe this should be resurrected and updated to AIR 1.5.1 and to use this new version info (at least new since I built the original AIR app). It could also be enhanced to read version info from individual swcs as well. Oh and maybe allow users to drag and drop directories, or wars or swcs onto the app to read the info. Hmmm….if only I had the time.

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> http://blog.flexmonkeypatches.com/2009/02/25/getting-the-version-of-the-flex-sdk-that-was-used-to-compile-a-swc/feed/ 3 Poor man’s zooming Flex TileList http://blog.flexmonkeypatches.com/2009/01/20/poor-mans-zooming-flex-tilelist/ http://blog.flexmonkeypatches.com/2009/01/20/poor-mans-zooming-flex-tilelist/#comments Tue, 20 Jan 2009 19:46:25 +0000 Kyle http://blog.flexmonkeypatches.com/?p=377 I was looking into how one might implement zooming in on an item in a Tilelist or zooming out to view more of the items in a Tilelist and stumbled upon a “poor man’s solution”. Implementing true zooming with gradual easing in/out would be much more involved and take you into the depths of Listbase (and probably into private methods, etc).
This is based on code from one of my previous blog posts:

TileList with popup that deletes from dataProvider

Here is the sample and code that demonstrates the approach one might take:

Download a zipfile containing the source to this sample.

Browse the source of this example.

Or continue into the blog entry to see the source:

Here is the app code:

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"  
    layout="horizontal">

<mx:Script>
<![CDATA[
    import mx.effects.effectClasses.AnimatePropertyInstance;
    import mx.managers.PopUpManager;
    import mx.managers.PopUpManagerChildList;
    import mx.events.ListEvent;
    import mx.events.SliderEvent;
    import mx.controls.sliderClasses.Slider;
    import mx.collections.ArrayCollection;
    import mx.effects.easing.Cubic;
   
   
    [Bindable]
    private var catalog:ArrayCollection;
   
    private var assets:Array = ["assets/putty.jpg", "assets/cantena.jpg", "assets/orb.jpg", "assets/globe.jpg", "assets/usbfan.jpg", "assets/hotsauce.jpg"];
        
    private function initCatalog():void
    {
        catalog = new ArrayCollection();
        for (var i:int=0;i<assets.length;i++){
            var vo:MyVO=new MyVO(assets[i],assets[i]);
            catalog.addItem(vo);
        }
    }
   
   
    public function createPopup(event:ListEvent):void
    {
        var foo:String="bar";
        var renderer:MyRenderer = event.itemRenderer as MyRenderer;
        var pop:MyPopup = MyPopup(PopUpManager.createPopUp(this,MyPopup,false,PopUpManagerChildList.POPUP));
        pop.vo=(event.target as TileList).selectedItem as MyVO;
        pop.myparentDP=(event.target as TileList).dataProvider as ArrayCollection;

        tilePopUps();
       
    }
   
    private function tilePopUps():void{
        for (var i:int=0;i<systemManager.popUpChildren.numChildren;i++){
            var o:* = systemManager.popUpChildren.getChildAt(i);
            PopUpManager.centerPopUp(o)
            if(i!=0){
                o.x+=10*i;
                o.y+=10*i; 
            }
        }
    }
    //http://www.actionscript.org/forums/showthread.php3?t=116021
    private function sliderChange(target:TileList, event:SliderEvent):void {
        var currentSlider:Slider=Slider(event.currentTarget);
        target.columnCount = Math.floor(target.width/currentSlider.value);
        target.rowCount= Math.floor(target.height/currentSlider.value);
        target.columnWidth = currentSlider.value;
        target.rowHeight = currentSlider.value;
    }
]]>
</mx:Script>
<mx:VBox>
    <mx:Button label="grow" click="gr.play()" />            
   
    <mx:VSlider
        id="dim"
        value="25"
        tickInterval="5"
        snapInterval="5"
        labels="['0', '200']"
        height="146"
        minimum="25"
        maximum="200"
        change="sliderChange(tileList,event)"/>
       
    <mx:Button label="shrink" click="shr.play()"/>

</mx:VBox>
<mx:TileList id="tileList"
    dataProvider="{catalog}"
    itemRenderer="MyRenderer"
    themeColor="haloSilver"
    rowHeight="25"
    columnWidth="25"
    verticalScrollPolicy="on"
    itemClick="createPopup(event);"
    creationComplete="initCatalog();tileList.selectedIndex=0;"
    height="200"
    width="200"
    itemsChangeEffect="{myTileListEffect}"
    />

 <mx:DefaultTileListEffect id="myTileListEffect"
            fadeOutDuration="500"
            fadeInDuration="500"
            moveDuration="1500" />
           
<mx:AnimateProperty id="shr" target="{dim}" property="value" fromValue="200" toValue="25" duration="2500" easingFunction="Cubic.easeOut"/>
   
<mx:Parallel id="gr">
    <mx:AnimateProperty target="{dim}" property="value" fromValue="25" toValue="200" duration="2500" easingFunction="Cubic.easeIn"/>
    <mx:AnimateProperty target="{tileList}" startDelay="1000" property="verticalScrollPosition" fromValue="0" toValue="{tileList.selectedIndex}" duration="1500" />
</mx:Parallel>            
           
</mx:Application>
 

Here is the popup:

<?xml version="1.0" encoding="utf-8"?>
<mx:TitleWindow xmlns:mx="http://www.adobe.com/2006/mxml"
        horizontalAlign="center"
        verticalAlign="middle">

    <mx:Script>
        <![CDATA[
            import mx.collections.ArrayCollection;
            import mx.managers.PopUpManager;
           
            public var myparentDP:ArrayCollection;
            [Bindable]
            public var vo:MyVO;
           
            private function removeItem():void{
                var i:int = myparentDP.getItemIndex(vo);
                if (i!=-1){
                    myparentDP.removeItemAt(i);
                }   
                PopUpManager.removePopUp(this);
            }
           
           
        ]]>
    </mx:Script>

    <mx:Image source="{vo.asset}" />
    <mx:Label text="{vo.title}" />
    <mx:HBox>
        <mx:Button label="close" click="PopUpManager.removePopUp(this)"/>
        <mx:Button label="remove item" click="removeItem()"/>
    </mx:HBox>
</mx:TitleWindow>
 

Here is the custom renderer:

<?xml version="1.0" encoding="utf-8"?>
<mx:Image xmlns:mx="http://www.adobe.com/2006/mxml"
    horizontalAlign="center"
    verticalAlign="middle"
    source="{data.asset}"
    toolTip="{data.title}"
>

</mx:Image>
 

Here is the value object:

package
{
    [Bindable]
    public class MyVO
    {
       
        private var _asset:String;
        private var _title:String;
       
        public function MyVO(title:String, asset:String)
        {
            this.title=title;
            this.asset=asset;
        }
       
        public function set title(title:String):void{
            _title=title;
        }
       
        public function get title():String{
            return _title; 
        }
       
        public function set asset(asset:String):void{
            _asset=asset;
        }
       
        public function get asset():String{
            return _asset; 
        }

    }
}
 

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> I was looking into how one might implement zooming in on an item in a Tilelist or zooming out to view more of the items in a Tilelist and stumbled upon a “poor man’s solution”. Implementing true zooming with gradual easing in/out would be much more involved and take you into the depths of Listbase (and probably into private methods, etc).
This is based on code from one of my previous blog posts:

TileList with popup that deletes from dataProvider

Here is the sample and code that demonstrates the approach one might take:

Download a zipfile containing the source to this sample.

Browse the source of this example.

Or continue into the blog entry to see the source:

Here is the app code:

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"  
    layout="horizontal">

<mx:Script>
<![CDATA[
    import mx.effects.effectClasses.AnimatePropertyInstance;
    import mx.managers.PopUpManager;
    import mx.managers.PopUpManagerChildList;
    import mx.events.ListEvent;
    import mx.events.SliderEvent;
    import mx.controls.sliderClasses.Slider;
    import mx.collections.ArrayCollection;
    import mx.effects.easing.Cubic;
   
   
    [Bindable]
    private var catalog:ArrayCollection;
   
    private var assets:Array = ["assets/putty.jpg", "assets/cantena.jpg", "assets/orb.jpg", "assets/globe.jpg", "assets/usbfan.jpg", "assets/hotsauce.jpg"];
        
    private function initCatalog():void
    {
        catalog = new ArrayCollection();
        for (var i:int=0;i<assets.length;i++){
            var vo:MyVO=new MyVO(assets[i],assets[i]);
            catalog.addItem(vo);
        }
    }
   
   
    public function createPopup(event:ListEvent):void
    {
        var foo:String="bar";
        var renderer:MyRenderer = event.itemRenderer as MyRenderer;
        var pop:MyPopup = MyPopup(PopUpManager.createPopUp(this,MyPopup,false,PopUpManagerChildList.POPUP));
        pop.vo=(event.target as TileList).selectedItem as MyVO;
        pop.myparentDP=(event.target as TileList).dataProvider as ArrayCollection;

        tilePopUps();
       
    }
   
    private function tilePopUps():void{
        for (var i:int=0;i<systemManager.popUpChildren.numChildren;i++){
            var o:* = systemManager.popUpChildren.getChildAt(i);
            PopUpManager.centerPopUp(o)
            if(i!=0){
                o.x+=10*i;
                o.y+=10*i; 
            }
        }
    }
    //http://www.actionscript.org/forums/showthread.php3?t=116021
    private function sliderChange(target:TileList, event:SliderEvent):void {
        var currentSlider:Slider=Slider(event.currentTarget);
        target.columnCount = Math.floor(target.width/currentSlider.value);
        target.rowCount= Math.floor(target.height/currentSlider.value);
        target.columnWidth = currentSlider.value;
        target.rowHeight = currentSlider.value;
    }
]]>
</mx:Script>
<mx:VBox>
    <mx:Button label="grow" click="gr.play()" />            
   
    <mx:VSlider
        id="dim"
        value="25"
        tickInterval="5"
        snapInterval="5"
        labels="['0', '200']"
        height="146"
        minimum="25"
        maximum="200"
        change="sliderChange(tileList,event)"/>
       
    <mx:Button label="shrink" click="shr.play()"/>

</mx:VBox>
<mx:TileList id="tileList"
    dataProvider="{catalog}"
    itemRenderer="MyRenderer"
    themeColor="haloSilver"
    rowHeight="25"
    columnWidth="25"
    verticalScrollPolicy="on"
    itemClick="createPopup(event);"
    creationComplete="initCatalog();tileList.selectedIndex=0;"
    height="200"
    width="200"
    itemsChangeEffect="{myTileListEffect}"
    />

 <mx:DefaultTileListEffect id="myTileListEffect"
            fadeOutDuration="500"
            fadeInDuration="500"
            moveDuration="1500" />
           
<mx:AnimateProperty id="shr" target="{dim}" property="value" fromValue="200" toValue="25" duration="2500" easingFunction="Cubic.easeOut"/>
   
<mx:Parallel id="gr">
    <mx:AnimateProperty target="{dim}" property="value" fromValue="25" toValue="200" duration="2500" easingFunction="Cubic.easeIn"/>
    <mx:AnimateProperty target="{tileList}" startDelay="1000" property="verticalScrollPosition" fromValue="0" toValue="{tileList.selectedIndex}" duration="1500" />
</mx:Parallel>            
           
</mx:Application>
 

Here is the popup:

<?xml version="1.0" encoding="utf-8"?>
<mx:TitleWindow xmlns:mx="http://www.adobe.com/2006/mxml"
        horizontalAlign="center"
        verticalAlign="middle">

    <mx:Script>
        <![CDATA[
            import mx.collections.ArrayCollection;
            import mx.managers.PopUpManager;
           
            public var myparentDP:ArrayCollection;
            [Bindable]
            public var vo:MyVO;
           
            private function removeItem():void{
                var i:int = myparentDP.getItemIndex(vo);
                if (i!=-1){
                    myparentDP.removeItemAt(i);
                }   
                PopUpManager.removePopUp(this);
            }
           
           
        ]]>
    </mx:Script>

    <mx:Image source="{vo.asset}" />
    <mx:Label text="{vo.title}" />
    <mx:HBox>
        <mx:Button label="close" click="PopUpManager.removePopUp(this)"/>
        <mx:Button label="remove item" click="removeItem()"/>
    </mx:HBox>
</mx:TitleWindow>
 

Here is the custom renderer:

<?xml version="1.0" encoding="utf-8"?>
<mx:Image xmlns:mx="http://www.adobe.com/2006/mxml"
    horizontalAlign="center"
    verticalAlign="middle"
    source="{data.asset}"
    toolTip="{data.title}"
>

</mx:Image>
 

Here is the value object:

package
{
    [Bindable]
    public class MyVO
    {
       
        private var _asset:String;
        private var _title:String;
       
        public function MyVO(title:String, asset:String)
        {
            this.title=title;
            this.asset=asset;
        }
       
        public function set title(title:String):void{
            _title=title;
        }
       
        public function get title():String{
            return _title; 
        }
       
        public function set asset(asset:String):void{
            _asset=asset;
        }
       
        public function get asset():String{
            return _asset; 
        }

    }
}
 

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> http://blog.flexmonkeypatches.com/2009/01/20/poor-mans-zooming-flex-tilelist/feed/ 4 New Flex Builder, Flex SDK, LCDS and BlazeDS releases http://blog.flexmonkeypatches.com/2008/11/19/new-flex-builder-flex-sdk-lcds-and-blazeds-releases/ http://blog.flexmonkeypatches.com/2008/11/19/new-flex-builder-flex-sdk-lcds-and-blazeds-releases/#comments Wed, 19 Nov 2008 14:55:40 +0000 Kyle http://blog.flexmonkeypatches.com/?p=356 OK…so I guess I kind of passed over these yesterday in my announcements. To me, the fact that there would be new releases timed with MAX was known and to anyone in the community there was probably a strong suspicion that there would at least be a new point release at MAX 2008. But in an effort to correct my oversight, here are links to the announcements by the product managers:

Matt Chotin (PM for Flex SDK) announces Flex Builder 3.0.2 and Flex SDK 3.2 (with support for AIR 1.5 and Flash Player 10).

Anil Channappa (PM for LCDS and BlazeDS) announces LCDS 2.6.1 and BlazeDS 3.2.

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> OK…so I guess I kind of passed over these yesterday in my announcements. To me, the fact that there would be new releases timed with MAX was known and to anyone in the community there was probably a strong suspicion that there would at least be a new point release at MAX 2008. But in an effort to correct my oversight, here are links to the announcements by the product managers:

Matt Chotin (PM for Flex SDK) announces Flex Builder 3.0.2 and Flex SDK 3.2 (with support for AIR 1.5 and Flash Player 10).

Anil Channappa (PM for LCDS and BlazeDS) announces LCDS 2.6.1 and BlazeDS 3.2.

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> http://blog.flexmonkeypatches.com/2008/11/19/new-flex-builder-flex-sdk-lcds-and-blazeds-releases/feed/ 1 New and Exciting on Adobe Labs! http://blog.flexmonkeypatches.com/2008/11/17/new-and-exciting-on-adobe-labs/ http://blog.flexmonkeypatches.com/2008/11/17/new-and-exciting-on-adobe-labs/#comments Mon, 17 Nov 2008 20:53:57 +0000 Kyle http://blog.flexmonkeypatches.com/?p=347 There were lots of exciting new things at Adobe MAX 2008 today, plus a lot of new stuff landed on Adobe LABs. Here are the things I think are cool and showcase the innovation of the people at Adobe:

http://labs.adobe.com/technologies/alchemy/

Alchemy is a research project that allows users to compile C and C++ code that is targeted to run on the open source ActionScript Virtual Machine (AVM2). The purpose of this preview is to assess the level of community interest in reusing existing C and C++ libraries in Web applications that run on Adobe® Flash® Player and Adobe AIR®.

http://labs.adobe.com/technologies/flashcatalyst/(formerly Thermo)

“Adobe® Flash® Catalyst is a new professional interaction design tool for rapidly creating application interfaces and interactive content without coding. These can range from interactive Ads, product guides and design portfolios to user interfaces for applications. Flash Catalyst enables designers to start from static compositions created in Adobe Photoshop® CS4, Illustrator® CS4, or Adobe Fireworks® CS4 and convert the artwork into applications and interactive content. The designer does this by visually defining events, transitions and motion. Flash Catalyst can output a finished Flash SWF or AIR application that’s ready to publish on the web. In addition designers can provide the project file to developers who can use Adobe Flex® Builder™ to add additional functionality such as connection to back-end systems.”

http://labs.adobe.com/technologies/cocomo/

Codename “Cocomo” is a Platform as a Service that allows Flex developers to easily add real-time social capabilities into their RIA (rich Internet applications). Comprised of both Flex-based client components and a hosted services infrastructure, Cocomo allows you to build real-time, multi-user applications with Flex in less time than ever before. And because Acrobat.com hosts the service, issues like deployment, maintenance, and scalability are taken care of for you.

Add social features to your existing Flex apps or build totally new ones, such as real-time productivity/collaboration apps, multiplayer games, and audio/video chat.

http://labs.adobe.com/wiki/index.php/Genesis

Genesis is the code-name for a new product initiative at Adobe with the objective of joining business applications, documents and the web on every knowledge workers desktop with integrated collaboration capabilities. Using the very intuitive interface of the Genesis desktop client (built on Adobe AIR) knowledge workers are able to create custom workspaces combining views into business applications, analytics, web sites and documents. Workspaces can be easily and securely shared with other colleagues or business partners outside the company and provide out-of-the-box real time collaboration capabilities like instant messaging, voice and video as well as screen sharing and white boarding.

http://labs.adobe.com/wiki/index.php/Adobe_Wave

Adobe® Wave™ is an Adobe AIR application and Adobe hosted service that work together to enable desktop notifications. It helps publishers stay connected to your customers and lets users avoid the email clutter of dozens of newsletters and social network update messages. Adobe Wave is a single web service call that lets publishers reach users directly on their desktop: there’s no need to make them download a custom application or build it yourself. The Adobe Wave pre-release program is geared towards developers, so if you’re a user who wants to try it out, click here to send us an email. We’ll let you know when Adobe Wave is available for you to try!

http://labs.adobe.com/wiki/index.php/Stratus

Flash Player 10 and Adobe AIR 1.5 introduce a new communications protocol called the Real-Time Media Flow Protocol (RTMFP). The most important features of RTMFP include low latency, end-to-end peering capability, security and scalability. These properties make RTMFP especially well suited for developing real-time collaboration applications by not only providing superior user experience but also reducing cost for operators.

In order to use RTMFP, Flash Player endpoints must connect to an RTMFP-capable server, such as the Adobe Stratus service. Stratus is a Beta hosted rendezvous service that aids establishing communications between Flash Player endpoints. Unlike Flash Media Server, Stratus does not support media relay, shared objects, scripting, etc. So by using Stratus, you can only develop applications where Flash Player endpoints are directly communicating with each other.

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> There were lots of exciting new things at Adobe MAX 2008 today, plus a lot of new stuff landed on Adobe LABs. Here are the things I think are cool and showcase the innovation of the people at Adobe:

http://labs.adobe.com/technologies/alchemy/

Alchemy is a research project that allows users to compile C and C++ code that is targeted to run on the open source ActionScript Virtual Machine (AVM2). The purpose of this preview is to assess the level of community interest in reusing existing C and C++ libraries in Web applications that run on Adobe® Flash® Player and Adobe AIR®.

http://labs.adobe.com/technologies/flashcatalyst/(formerly Thermo)

“Adobe® Flash® Catalyst is a new professional interaction design tool for rapidly creating application interfaces and interactive content without coding. These can range from interactive Ads, product guides and design portfolios to user interfaces for applications. Flash Catalyst enables designers to start from static compositions created in Adobe Photoshop® CS4, Illustrator® CS4, or Adobe Fireworks® CS4 and convert the artwork into applications and interactive content. The designer does this by visually defining events, transitions and motion. Flash Catalyst can output a finished Flash SWF or AIR application that’s ready to publish on the web. In addition designers can provide the project file to developers who can use Adobe Flex® Builder™ to add additional functionality such as connection to back-end systems.”

http://labs.adobe.com/technologies/cocomo/

Codename “Cocomo” is a Platform as a Service that allows Flex developers to easily add real-time social capabilities into their RIA (rich Internet applications). Comprised of both Flex-based client components and a hosted services infrastructure, Cocomo allows you to build real-time, multi-user applications with Flex in less time than ever before. And because Acrobat.com hosts the service, issues like deployment, maintenance, and scalability are taken care of for you.

Add social features to your existing Flex apps or build totally new ones, such as real-time productivity/collaboration apps, multiplayer games, and audio/video chat.

http://labs.adobe.com/wiki/index.php/Genesis

Genesis is the code-name for a new product initiative at Adobe with the objective of joining business applications, documents and the web on every knowledge workers desktop with integrated collaboration capabilities. Using the very intuitive interface of the Genesis desktop client (built on Adobe AIR) knowledge workers are able to create custom workspaces combining views into business applications, analytics, web sites and documents. Workspaces can be easily and securely shared with other colleagues or business partners outside the company and provide out-of-the-box real time collaboration capabilities like instant messaging, voice and video as well as screen sharing and white boarding.

http://labs.adobe.com/wiki/index.php/Adobe_Wave

Adobe® Wave™ is an Adobe AIR application and Adobe hosted service that work together to enable desktop notifications. It helps publishers stay connected to your customers and lets users avoid the email clutter of dozens of newsletters and social network update messages. Adobe Wave is a single web service call that lets publishers reach users directly on their desktop: there’s no need to make them download a custom application or build it yourself. The Adobe Wave pre-release program is geared towards developers, so if you’re a user who wants to try it out, click here to send us an email. We’ll let you know when Adobe Wave is available for you to try!

http://labs.adobe.com/wiki/index.php/Stratus

Flash Player 10 and Adobe AIR 1.5 introduce a new communications protocol called the Real-Time Media Flow Protocol (RTMFP). The most important features of RTMFP include low latency, end-to-end peering capability, security and scalability. These properties make RTMFP especially well suited for developing real-time collaboration applications by not only providing superior user experience but also reducing cost for operators.

In order to use RTMFP, Flash Player endpoints must connect to an RTMFP-capable server, such as the Adobe Stratus service. Stratus is a Beta hosted rendezvous service that aids establishing communications between Flash Player endpoints. Unlike Flash Media Server, Stratus does not support media relay, shared objects, scripting, etc. So by using Stratus, you can only develop applications where Flash Player endpoints are directly communicating with each other.

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> http://blog.flexmonkeypatches.com/2008/11/17/new-and-exciting-on-adobe-labs/feed/ 2 Flex Showcase app – Tour de Flex http://blog.flexmonkeypatches.com/2008/11/17/flex-showcase-app-tour-de-flex/ http://blog.flexmonkeypatches.com/2008/11/17/flex-showcase-app-tour-de-flex/#comments Mon, 17 Nov 2008 18:41:38 +0000 Kyle http://blog.flexmonkeypatches.com/?p=341 I pointed one of my customers at this app last week. I had no idea it would be all the rage at MAX :)

http://flex.org/tour

“Tour de Flex is a desktop application for exploring Flex capabilities and resources, including the core Flex components, Adobe AIR and data integration, as well as a variety of third-party components, effects, skins, and more.”

I have posted an install badge in my sidebar (below my paypal badge)…check it out.

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> I pointed one of my customers at this app last week. I had no idea it would be all the rage at MAX :)

http://flex.org/tour

“Tour de Flex is a desktop application for exploring Flex capabilities and resources, including the core Flex components, Adobe AIR and data integration, as well as a variety of third-party components, effects, skins, and more.”

I have posted an install badge in my sidebar (below my paypal badge)…check it out.

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> http://blog.flexmonkeypatches.com/2008/11/17/flex-showcase-app-tour-de-flex/feed/ 1 Sessions not to miss at Adobe MAX 2008 http://blog.flexmonkeypatches.com/2008/11/17/sessions-not-to-miss-at-adobe-max-2008/ http://blog.flexmonkeypatches.com/2008/11/17/sessions-not-to-miss-at-adobe-max-2008/#comments Mon, 17 Nov 2008 17:13:39 +0000 Kyle http://blog.flexmonkeypatches.com/?p=336 Two things really excite me that there will be more info on at MAX NA, 2008.

Cocomo and Genesis.

Cocomo is now on Adobe Labs: http://labs.adobe.com/technologies/cocomo/

Do not miss these sessions:
Real-Time Collaboration Apps with Flex and Cocomo
Explore Cocomo, Adobe’s new Platform-as-a-Service for developing real-time, multiuser Flex applications. Learn how any Flex developer can use Adobe’s services infrastructure to build stunningly rich real-time social apps, including robust data messaging and streaming live video and VoIP. In this session we’ll be showing live coding with the Cocomo Flex SDK and Adobe’s services. Bring a laptop and be ready to join in.

Speakers: Nigel Pegg
Audience: IS/IT, Creative Designer, Business Decision Maker, Architect, Application Developer
Skill: Intermediate
Products: Flex Builder, Flex, Flash Player, Flash Media Server, Connect, AIR, ActionScript, Acrobat
When: Monday, November 17, 3:30 pm – 4:30 pm, Moscone West 2007

Cocomo Deep Dive: Building Social RIAs with Flex + Adobe Hosted Services
Learn to build your first multiuser Adobe AIR application using the new Cocomo Flex SDK. In this session, we’ll walk you through the philosophy and design considerations of this new breed of application, all the way to the nuts and bolts of coding, debugging, and deploying it. Follow along as a real-time collaborative AIR app is built from scratch and deployed on stage. There will be code — bring a laptop!

Speakers: Nigel Pegg
Audience: IS/IT, Creative Designer, Business Decision Maker, Architect, Application Developer
Skill: Intermediate
Products: Flex Builder, Flex, Flash Player, Flash Media Server, Connect, AIR, ActionScript, Acrobat
When: Wednesday, November 19, 3:30 pm – 4:30 pm, Moscone West 2003

The Genesis Blog is here: http://blogs.adobe.com/mashup/

Don’t miss this session either:

Genesis: A Collaborative Mashup Client for Business Users
Learn how Genesis enables knowledge workers to combine web applications, enterprise apps, and documents within one workspace on their desktop and provides sharing as well as real-time collaboration. Genesis is a code name for a new Adobe product in development that includes a desktop client based on Adobe AIR and Flex as well as hosted collaboration services that leverage Adobe Acrobat Connect via Cocomo. We’ll discuss business use cases for Genesis and demonstrate features and functionality. For Flex developers, we’ll explain the architecture and opportunities to create Flex widgets that can be distributed via the Genesis catalog.

Speakers: Mattias Zeller, Steve Yankovich
Audience: Partner Decision Maker, IS/IT, Business Decision Maker, Architect
Skill: General Audience
Products: Flex
When:
Monday, November 17, 2:00 pm – 3:00 pm, Moscone West 2014

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> Two things really excite me that there will be more info on at MAX NA, 2008.

Cocomo and Genesis.

Cocomo is now on Adobe Labs: http://labs.adobe.com/technologies/cocomo/

Do not miss these sessions:
Real-Time Collaboration Apps with Flex and Cocomo
Explore Cocomo, Adobe’s new Platform-as-a-Service for developing real-time, multiuser Flex applications. Learn how any Flex developer can use Adobe’s services infrastructure to build stunningly rich real-time social apps, including robust data messaging and streaming live video and VoIP. In this session we’ll be showing live coding with the Cocomo Flex SDK and Adobe’s services. Bring a laptop and be ready to join in.

Speakers: Nigel Pegg
Audience: IS/IT, Creative Designer, Business Decision Maker, Architect, Application Developer
Skill: Intermediate
Products: Flex Builder, Flex, Flash Player, Flash Media Server, Connect, AIR, ActionScript, Acrobat
When: Monday, November 17, 3:30 pm – 4:30 pm, Moscone West 2007

Cocomo Deep Dive: Building Social RIAs with Flex + Adobe Hosted Services
Learn to build your first multiuser Adobe AIR application using the new Cocomo Flex SDK. In this session, we’ll walk you through the philosophy and design considerations of this new breed of application, all the way to the nuts and bolts of coding, debugging, and deploying it. Follow along as a real-time collaborative AIR app is built from scratch and deployed on stage. There will be code — bring a laptop!

Speakers: Nigel Pegg
Audience: IS/IT, Creative Designer, Business Decision Maker, Architect, Application Developer
Skill: Intermediate
Products: Flex Builder, Flex, Flash Player, Flash Media Server, Connect, AIR, ActionScript, Acrobat
When: Wednesday, November 19, 3:30 pm – 4:30 pm, Moscone West 2003

The Genesis Blog is here: http://blogs.adobe.com/mashup/

Don’t miss this session either:

Genesis: A Collaborative Mashup Client for Business Users
Learn how Genesis enables knowledge workers to combine web applications, enterprise apps, and documents within one workspace on their desktop and provides sharing as well as real-time collaboration. Genesis is a code name for a new Adobe product in development that includes a desktop client based on Adobe AIR and Flex as well as hosted collaboration services that leverage Adobe Acrobat Connect via Cocomo. We’ll discuss business use cases for Genesis and demonstrate features and functionality. For Flex developers, we’ll explain the architecture and opportunities to create Flex widgets that can be distributed via the Genesis catalog.

Speakers: Mattias Zeller, Steve Yankovich
Audience: Partner Decision Maker, IS/IT, Business Decision Maker, Architect
Skill: General Audience
Products: Flex
When:
Monday, November 17, 2:00 pm – 3:00 pm, Moscone West 2014

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> http://blog.flexmonkeypatches.com/2008/11/17/sessions-not-to-miss-at-adobe-max-2008/feed/ 0 Specifying BlazeDS/LCDS Configuration token as JVM args http://blog.flexmonkeypatches.com/2008/11/17/specifying-blazedslcds-configuration-token-as-jvm-args/ http://blog.flexmonkeypatches.com/2008/11/17/specifying-blazedslcds-configuration-token-as-jvm-args/#comments Mon, 17 Nov 2008 14:47:54 +0000 Kyle http://blog.flexmonkeypatches.com/?p=333 Kind of related to an earlier post: Deploying Multiple LCDS wars to the same servlet container

I found out that you can specify config file tokens as JVM args. This makes deploying the same war file to various deployments that have slight variations for certain parameters easier, since you can deploy the same war, but “tokenize” (and/or use some of the default tokens).

http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/lcds/help.html?content=lcarch_4.html

“You can also use custom run-time tokens in service configuration files; for example, {messaging-channel} and {my.token}. You specify values for these tokens in Java Virtual Machine (JVM) options. The server reads these JVM options to determine what values are defined for them, and replaces the tokens with the specified values. If you have a custom token for which a value cannot be found, an error is thrown. Because {server.name}, {server.port}, and {context.root} are special tokens, no errors occur when these tokens are not specified in JVM options.”

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> Kind of related to an earlier post: Deploying Multiple LCDS wars to the same servlet container

I found out that you can specify config file tokens as JVM args. This makes deploying the same war file to various deployments that have slight variations for certain parameters easier, since you can deploy the same war, but “tokenize” (and/or use some of the default tokens).

http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/lcds/help.html?content=lcarch_4.html

“You can also use custom run-time tokens in service configuration files; for example, {messaging-channel} and {my.token}. You specify values for these tokens in Java Virtual Machine (JVM) options. The server reads these JVM options to determine what values are defined for them, and replaces the tokens with the specified values. If you have a custom token for which a value cannot be found, an error is thrown. Because {server.name}, {server.port}, and {context.root} are special tokens, no errors occur when these tokens are not specified in JVM options.”

Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

]]> http://blog.flexmonkeypatches.com/2008/11/17/specifying-blazedslcds-configuration-token-as-jvm-args/feed/ 0 TileList with popup that deletes from dataProvider http://blog.flexmonkeypatches.com/2008/10/29/tilelist-with-popup-that-deletes-from-dataprovider/ http://blog.flexmonkeypatches.com/2008/10/29/tilelist-with-popup-that-deletes-from-dataprovider/#comments Wed, 29 Oct 2008 17:16:22 +0000 Kyle http://blog.flexmonkeypatches.com/?p=319 I wrote a demo a while back for a customer to demonstrate the following scenario:

  • Tilelist populated by an arrayCollection of typed objects.
  • Tilelist has a custom itemRender that pops up a “view” of the data for the item in the tilelist that was clicked.
  • The popup can delete the related object from the dataProvider of the TileList, removing the popup and the corresponding item from the Tilelist.

    Here is the app:

    Download a zipfile containing the source to this sample.

    Browse the source of this example.

    Or continue into the blog entry to see the source:

    Here is the app code:

    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"  viewSourceURL="srcview/index.html">

    <mx:Script>
    <![CDATA[
        import mx.managers.PopUpManager;
        import mx.managers.PopUpManagerChildList;
        import mx.events.ListEvent;
        import mx.collections.ArrayCollection;
       
       [Bindable]
       private var catalog:ArrayCollection;

       private var assets:Array = ["assets/putty.jpg", "assets/cantena.jpg", "assets/orb.jpg", "assets/globe.jpg", "assets/usbfan.jpg", "assets/hotsauce.jpg"];
            
        private function initCatalog():void
        {
            catalog = new ArrayCollection();
            for (var i:int=0;i<assets.length;i++){
                var vo:MyVO=new MyVO(assets[i],assets[i]);
                catalog.addItem(vo);
            }
        }
       
       
        public function createPopup(event:ListEvent):void
        {
            var foo:String="bar";
            var renderer:MyRenderer = event.itemRenderer as MyRenderer;
            var pop:MyPopup = MyPopup(PopUpManager.createPopUp(this,MyPopup,false,PopUpManagerChildList.POPUP));
            pop.vo=(event.target as TileList).selectedItem as MyVO;
            pop.myparentDP=(event.target as TileList).dataProvider as ArrayCollection;

            tilePopUps();
           
        }
       
        private function tilePopUps():void{
            for (var i:int=0;i<systemManager.popUpChildren.numChildren;i++){
                var o:* = systemManager.popUpChildren.getChildAt(i);
                PopUpManager.centerPopUp(o)
                if(i!=0){
                    o.x+=10*i;
                    o.y+=10*i; 
                }
            }
        }
       
    ]]>
    </mx:Script>

    <mx:TileList id="tileList"
                dataProvider="{catalog}"
                itemRenderer="MyRenderer"
                columnCount="3"
                columnWidth="140"
                rowCount="1"
                rowHeight="140"
                themeColor="haloSilver"
                verticalScrollPolicy="on"
                itemClick="createPopup(event);"
                creationComplete="initCatalog();"/>

    </mx:Application>
     

    Here is the itemRenderer:

    <?xml version="1.0" encoding="utf-8"?>
    <mx:VBox xmlns:mx="http://www.adobe.com/2006/mxml"
            horizontalAlign="center"
            verticalAlign="middle">

        <mx:Image source="{data.asset}" scaleX=".25" scaleY=".25"/>
        <mx:Label text="{data.title}" />
    </mx:VBox>
     

    Here is the simple popup:

    <?xml version="1.0" encoding="utf-8"?>
    <mx:TitleWindow xmlns:mx="http://www.adobe.com/2006/mxml"
            horizontalAlign="center"
            verticalAlign="middle">

        <mx:Script>
            <![CDATA[
                import mx.collections.ArrayCollection;
                import mx.managers.PopUpManager;
               
                public var myparentDP:ArrayCollection;
                [Bindable]
                public var vo:MyVO;
               
                private function removeItem():void{
                    var i:int = myparentDP.getItemIndex(vo);
                    if (i!=-1){
                        myparentDP.removeItemAt(i);
                    }   
                    PopUpManager.removePopUp(this);
                }
               
               
            ]]>
        </mx:Script>

        <mx:Image source="{vo.asset}" />
        <mx:Label text="{vo.title}" />
        <mx:HBox>
            <mx:Button label="close" click="PopUpManager.removePopUp(this)"/>
            <mx:Button label="remove item" click="removeItem()"/>
        </mx:HBox>
    </mx:TitleWindow>
     

    Here is the type value object that populates the ArrayCollection:

    package
    {
        [Bindable]
        public class MyVO
        {
           
            private var _asset:String;
            private var _title:String;
           
            public function MyVO(title:String, asset:String)
            {
                this.title=title;
                this.asset=asset;
            }
           
            public function set title(title:String):void{
                _title=title;
            }
           
            public function get title():String{
                return _title; 
            }
           
            public function set asset(asset:String):void{
                _asset=asset;
            }
           
            public function get asset():String{
                return _asset; 
            }

        }
    }
     

    Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

    ]]> I wrote a demo a while back for a customer to demonstrate the following scenario:

  • Tilelist populated by an arrayCollection of typed objects.
  • Tilelist has a custom itemRender that pops up a “view” of the data for the item in the tilelist that was clicked.
  • The popup can delete the related object from the dataProvider of the TileList, removing the popup and the corresponding item from the Tilelist.

    Here is the app:

    Download a zipfile containing the source to this sample.

    Browse the source of this example.

    Or continue into the blog entry to see the source:

    Here is the app code:

    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"  viewSourceURL="srcview/index.html">

    <mx:Script>
    <![CDATA[
        import mx.managers.PopUpManager;
        import mx.managers.PopUpManagerChildList;
        import mx.events.ListEvent;
        import mx.collections.ArrayCollection;
       
       [Bindable]
       private var catalog:ArrayCollection;

       private var assets:Array = ["assets/putty.jpg", "assets/cantena.jpg", "assets/orb.jpg", "assets/globe.jpg", "assets/usbfan.jpg", "assets/hotsauce.jpg"];
            
        private function initCatalog():void
        {
            catalog = new ArrayCollection();
            for (var i:int=0;i<assets.length;i++){
                var vo:MyVO=new MyVO(assets[i],assets[i]);
                catalog.addItem(vo);
            }
        }
       
       
        public function createPopup(event:ListEvent):void
        {
            var foo:String="bar";
            var renderer:MyRenderer = event.itemRenderer as MyRenderer;
            var pop:MyPopup = MyPopup(PopUpManager.createPopUp(this,MyPopup,false,PopUpManagerChildList.POPUP));
            pop.vo=(event.target as TileList).selectedItem as MyVO;
            pop.myparentDP=(event.target as TileList).dataProvider as ArrayCollection;

            tilePopUps();
           
        }
       
        private function tilePopUps():void{
            for (var i:int=0;i<systemManager.popUpChildren.numChildren;i++){
                var o:* = systemManager.popUpChildren.getChildAt(i);
                PopUpManager.centerPopUp(o)
                if(i!=0){
                    o.x+=10*i;
                    o.y+=10*i; 
                }
            }
        }
       
    ]]>
    </mx:Script>

    <mx:TileList id="tileList"
                dataProvider="{catalog}"
                itemRenderer="MyRenderer"
                columnCount="3"
                columnWidth="140"
                rowCount="1"
                rowHeight="140"
                themeColor="haloSilver"
                verticalScrollPolicy="on"
                itemClick="createPopup(event);"
                creationComplete="initCatalog();"/>

    </mx:Application>
     

    Here is the itemRenderer:

    <?xml version="1.0" encoding="utf-8"?>
    <mx:VBox xmlns:mx="http://www.adobe.com/2006/mxml"
            horizontalAlign="center"
            verticalAlign="middle">

        <mx:Image source="{data.asset}" scaleX=".25" scaleY=".25"/>
        <mx:Label text="{data.title}" />
    </mx:VBox>
     

    Here is the simple popup:

    <?xml version="1.0" encoding="utf-8"?>
    <mx:TitleWindow xmlns:mx="http://www.adobe.com/2006/mxml"
            horizontalAlign="center"
            verticalAlign="middle">

        <mx:Script>
            <![CDATA[
                import mx.collections.ArrayCollection;
                import mx.managers.PopUpManager;
               
                public var myparentDP:ArrayCollection;
                [Bindable]
                public var vo:MyVO;
               
                private function removeItem():void{
                    var i:int = myparentDP.getItemIndex(vo);
                    if (i!=-1){
                        myparentDP.removeItemAt(i);
                    }   
                    PopUpManager.removePopUp(this);
                }
               
               
            ]]>
        </mx:Script>

        <mx:Image source="{vo.asset}" />
        <mx:Label text="{vo.title}" />
        <mx:HBox>
            <mx:Button label="close" click="PopUpManager.removePopUp(this)"/>
            <mx:Button label="remove item" click="removeItem()"/>
        </mx:HBox>
    </mx:TitleWindow>
     

    Here is the type value object that populates the ArrayCollection:

    package
    {
        [Bindable]
        public class MyVO
        {
           
            private var _asset:String;
            private var _title:String;
           
            public function MyVO(title:String, asset:String)
            {
                this.title=title;
                this.asset=asset;
            }
           
            public function set title(title:String):void{
                _title=title;
            }
           
            public function get title():String{
                return _title; 
            }
           
            public function set asset(asset:String):void{
                _asset=asset;
            }
           
            public function get asset():String{
                return _asset; 
            }

        }
    }
     

    Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

    ]]> http://blog.flexmonkeypatches.com/2008/10/29/tilelist-with-popup-that-deletes-from-dataprovider/feed/ 3 Use the focus, Luke…er, force combobox focus on mouseover http://blog.flexmonkeypatches.com/2008/10/24/use-the-focus-lukeer-force-combobox-focus-on-mouseover/ http://blog.flexmonkeypatches.com/2008/10/24/use-the-focus-lukeer-force-combobox-focus-on-mouseover/#comments Fri, 24 Oct 2008 15:05:15 +0000 Kyle http://blog.flexmonkeypatches.com/?p=310 I was helping a customer with an interesting question and it resulted in a nice little bit of code that I am demoing here.

    The basic idea was to force the combobox to receive focus when it is moused over rather than when clicked. Also, it would be useful to have the combobox get focus only if the previously focused component was a particular component.

    If you look at the docs:
    http://livedocs.adobe.com/flex/3/langref/mx/managers/FocusManager.html

    you will see that:

    Each FocusManager instance is responsible for a set of components that comprise a “tab loop”. If you hit Tab enough times, focus traverses through a set of components and eventually get back to the first component that had focus. That is a “tab loop” and a FocusManager instance manages that loop.

    You can use the focusManager.getFocus(); method to get the currently focussed item and you can also use focusManager. getNextFocusManagerComponent(backward:Boolean = false):IFocusManagerComponent to get you the next and previous items in the loop.

    The sample shows how to set the focus to the combobox when you hover over the combobox instead of setting focus only when you click on it(watch the blue focus ring), but only if the textInput whose id is “ti” first had focus. If the “ti2″ textinput had focus (or nothing had focus) before you hover over the combobox, then focus is not stolen.

    Download a zipfile containing the source to this sample.

    Browse the source of this example.

    Or continue into the blog entry to see the source:

    Here is the app code:

    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" backgroundColor="white" viewSourceURL="srcview/index.html">

        <mx:Script>
            <![CDATA[
                import mx.managers.FocusManager;
           
                private function checkFocus(event:Event):void{
                    //find component that has focus
                    var c:* = focusManager.getFocus();
                    trace((c ? c.id:”));
                    if (c && c.id=="ti"){
                        //target is actually the button encapsulated within the cbo box…
                        //currentTarget is the cbo
                        event.currentTarget.setFocus();
                    }
                }
               
            ]]>
        </mx:Script>

        <mx:TextInput id="ti" width="200" />
           
        <mx:ComboBox id="cbo" mouseOver="checkFocus(event)" >
          <mx:ArrayCollection>
             <mx:String>AK</mx:String>
             <mx:String>AL</mx:String>
             <mx:String>AR</mx:String>
          </mx:ArrayCollection>
       </mx:ComboBox>
       
       <mx:TextInput id="ti2" width="200" />
    </mx:Application>
     

    Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

    ]]>     I was helping a customer with an interesting question and it resulted in a nice little bit of code that I am demoing here.

    The basic idea was to force the combobox to receive focus when it is moused over rather than when clicked. Also, it would be useful to have the combobox get focus only if the previously focused component was a particular component.

    If you look at the docs:
    http://livedocs.adobe.com/flex/3/langref/mx/managers/FocusManager.html

    you will see that:

    Each FocusManager instance is responsible for a set of components that comprise a “tab loop”. If you hit Tab enough times, focus traverses through a set of components and eventually get back to the first component that had focus. That is a “tab loop” and a FocusManager instance manages that loop.

    You can use the focusManager.getFocus(); method to get the currently focussed item and you can also use focusManager. getNextFocusManagerComponent(backward:Boolean = false):IFocusManagerComponent to get you the next and previous items in the loop.

    The sample shows how to set the focus to the combobox when you hover over the combobox instead of setting focus only when you click on it(watch the blue focus ring), but only if the textInput whose id is “ti” first had focus. If the “ti2″ textinput had focus (or nothing had focus) before you hover over the combobox, then focus is not stolen.

    Download a zipfile containing the source to this sample.

    Browse the source of this example.

    Or continue into the blog entry to see the source:

    Here is the app code:

    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" backgroundColor="white" viewSourceURL="srcview/index.html">

        <mx:Script>
            <![CDATA[
                import mx.managers.FocusManager;
           
                private function checkFocus(event:Event):void{
                    //find component that has focus
                    var c:* = focusManager.getFocus();
                    trace((c ? c.id:”));
                    if (c && c.id=="ti"){
                        //target is actually the button encapsulated within the cbo box…
                        //currentTarget is the cbo
                        event.currentTarget.setFocus();
                    }
                }
               
            ]]>
        </mx:Script>

        <mx:TextInput id="ti" width="200" />
           
        <mx:ComboBox id="cbo" mouseOver="checkFocus(event)" >
          <mx:ArrayCollection>
             <mx:String>AK</mx:String>
             <mx:String>AL</mx:String>
             <mx:String>AR</mx:String>
          </mx:ArrayCollection>
       </mx:ComboBox>
       
       <mx:TextInput id="ti2" width="200" />
    </mx:Application>
     

    Share and Enjoy: Digg Sphinn del.icio.us Facebook Mixx Google Slashdot StumbleUpon Technorati TwitThis

    ]]>     http://blog.flexmonkeypatches.com/2008/10/24/use-the-focus-lukeer-force-combobox-focus-on-mouseover/feed/ 1