Thursday, April 8, 2010
Flex: Better Form Validation Messages
http://aralbalkan.com/1125
Wednesday, February 3, 2010
Flex: The World Factbook
Tuesday, December 15, 2009
Flex: Conditionally hide a child in Accordion.
check out the link for possible solutions:
http://stackoverflow.com/questions/410842/flex-accordion-conditionally-hide-a-child
Wednesday, December 9, 2009
Flash, Flex & AIR: A brief survey
Monday, December 7, 2009
Flex: Difference between invalidatelist and invalidatedisplaylist
http://stackoverflow.com/questions/74269/what-is-the-difference-between-invalidatelist-and-invalidatedisplaylist
invalidateList tells the component that the data has changed, and it needs to reload it and re-render it.
invalidateDisplayList tells the component that it needs to redraw itself (but not necessarily reload its data).
Flex: Difference between rollOver and mouseOver
http://polygeek.com/1519_flex_the-difference-between-rollover-and-mouseover
http://www.zedia.net/2008/difference-between-mouseeventroll_over-and-mouseeventmouse_over-in-as3/
The basic difference is that rollOut checks to see if the mouse is over the component that is listening for the event or a child of the component. mouseOut doesn’t do that so it fires causing the style to change before it can be corrected by mouseOver firing again.
Sunday, December 6, 2009
Flex: HBox implementation in reverse order
package com
{
import flash.display.DisplayObject;
import mx.containers.HBox;
public class MyHBox extends HBox
{
public function MyHBox()
{
super();
}
public override function addChild
(child:DisplayObject):DisplayObject
{
this.addChildAt(child,0);
return child
}
}
Wednesday, December 2, 2009
10 topics I want to learn
1) Flex
2) ActionScript
3) Flash
4) Photoshop
5) Adobe Air
6) ColdFusion
7) BlazeDS
8) WebORB
9) PureMVC
10) Cairngorm
Monday, November 23, 2009
Flex: ImageRail
Check it out:
http://www.flexer.info/2008/05/29/image-gallery-component-imagerail/
Thursday, November 19, 2009
Flex: FlowBox Container
visit:
http://www.munkiihouse.com/?p=60
http://www.munkiihouse.com/flexapps/FlowBox/Main.html
(view source enabled)
Monday, November 16, 2009
Flex: Customizing TileList selection
Visit:
http://mariosh.com/codes/customizing-tilelist-selection/
Sunday, November 15, 2009
Excellent Example Of Using Flex-Ajax Together.
- Ajax is very good for content-centric applications, while Flex is very good for interactive, media, and data-centric applications.
- If your application is somewhere in between the two sides of that spectrum, then you can use the Flex Ajax Bridge to combine the two technologies.
Saturday, November 14, 2009
Flex: Error #2148
Solution (a workaround maybe):
Add the following arguments to the compiler (via Properties - Flex Compiler) :
-use-network=false
Friday, November 13, 2009
Tuesday, November 10, 2009
Flex: Slow response time of weborb/remote object call?
Get them here:
http://www.adobe.com/support/flashplayer/downloads.html
Monday, November 9, 2009
Flex: Stop Event Propogation
Stopping propagation
During any phase, you can stop the traversal of the display list by calling one of the following methods on the Event object:
You can call either the event's stopPropagation() method or the stopImmediatePropagation() method to prevent an Event object from continuing on its way through the event flow. The two methods are nearly identical and differ only in whether the current node's remaining event listeners are allowed to execute. The stopPropagation() method prevents the Event object from moving on to the next node, but only after any other event listeners on the current node are allowed to execute.
The stopImmediatePropagation() method also prevents the Event objects from moving on to the next node, but it does not allow any other event listeners on the current node to execute.
(source: Adobe Livedocs)
Flex: Magic line to remove event listener.
Sunday, November 8, 2009
Flex: Difference between event.target and event.currentTarget properties in an event object.
In Flex, an event object is created whenever an event is dispatched. The event object has two important properties – event.target and event.currentTarget. The event.target property references the event dispatcher while event.currentTarget property refers to the node which is currently being checked for event listeners. While event.target property stays the same throughout the event flow (capturing, targeting and bubbling phases), the event.currentTarget property changes on each node.
For example, if an event is fired from a TextInput component placed inside a Panel, event.target in this case will be TextInput throughout the event flow while event.currentTarget will vary from Application to Panel to TextInput as the event object goes up or down the flow chain.
An important point to note over here is that when an event is fired from a component, event.target property does not necessarily reference the component which dispatched the event. It may refer to a subcomponent which is part of that component. This means that if you click on a button’s label, the event object’s event.target property won’t be button (as you might have hoped) but will be a subcomponent (within the button class) – UITextField (renders label in a button).This is a very important point while handling events. In this case, if the button component was listening for the click event, the event handler will be called if you are using event.currentTarget property since (sooner or later) event.currentTarget will refer to the button component as the mouse event bubbles through the chain. But, if you were using event.target property, the event handler will never get called as a subcomponent (UITextField) fired the event and is referred to in event.target property. Hence, you should always use event.currentTarget property instead of event.target.