OLAP DataGrid

Hi Folks, Today I learned the concept of OLAP DataGrid in Adobe Flex.The OLAPDataGrid control expands on the functionality of the AdvancedDataGrid control to add support for the display of the results of OLAP queries. Like all Flex data grid controls, the OLAPDataGrid control is designed to display data in a two-dimensional representation of rows and columns.

AdvancedDataGrid control:
Column dragging is not allowed in the OLAPDataGrid control.
You cannot edit cells in the OLAPDataGrid control because cell data is a result of a query and does not correspond to a single data value in the OLAP cube.
You cannot sort columns by clicking on header in the OLAPDataGrid control. Sorting is supported at the dimension level so that you can change the order of members of that dimension.
Properties
defaultCellString=”NaN”
headerRendererProviders=”[]“
itemRendererProviders=”[]“

Styles
columnAxisHeaderStyleName=”undefined”
rowAxisHeaderStyleName=”undefined”
/>
program:

dataProvider=”{flatData}”
id=”myMXMLCube”
complete=”runQuery(event);”>

Screen Shot:

HDividedBox

Good Evening Folks, Today I learned a concept of HDividedBox.

The HDividedBox container lays out its children horizontally in the same way as HBox container, but it inserts a draggable divider in the gap between each child. A user can drag the divider to resize the area allotted to each child.

The <mx:HDividedBox/> tag is the same as <mx:DividedBox direction="horizontal"/>.

The <mx:HDividedBox> tag inherits all of the tag attributes of its superclass except direction and adds no new tag attributes.

//

Characteristic:

Default size:

Description:

Width is large enough to hold all of its children at the default or explicit widths of the children, plus any horizontal gap between the children, plus the left and right padding of the container. Height is the default or explicit height of the tallest child plus the top and bottom padding of the container.

Default padding:

0 pixels for the top, bottom, left, and right values.

Default gap:

10 pixels for the horizontal and vertical gaps.

Program:

<mx:Panel title=”HDividedBox Container Example” width=”90%” height=”90%”
paddingTop=”10″ paddingLeft=”10″ paddingRight=”10″ paddingBottom=”10″>
<mx:Text width=”100%” color=”blue”
text=”Drag the divider side to side to resize the children.”/>
<mx:HDividedBox width=”100%” height=”100%”>
<mx:Canvas label=”Canvas 1″ width=”100%” height=”100%” backgroundColor=”#FFFFCC”>
<mx:Label text=”Add components here” fontWeight=”bold”/>
</mx:Canvas>
<mx:Canvas label=”Canvas 2″ width=”100%” height=”100%” backgroundColor=”#99CCFF”>
<mx:Label text=”Add components here” fontWeight=”bold”/>
</mx:Canvas>
</mx:HDividedBox>
</mx:Panel>

CreditCardValidation

The CreditCardValidatorCardType class defines value constants for specifying the type of credit card to validate. These values are used in the CreditCardValidator.cardType property.

Constants:

AMERICAN_EXPRESS : String = “American Express” [static] Specifies the card type as American Express.

Program:

<mx:Model id=”creditcard”>
<card>
<cardType>{cardTypeCombo.selectedItem.data}</cardType>
<cardNumber>{cardNumberInput.text}</cardNumber>
</card>
</mx:Model>
<mx:CreditCardValidator id=”ccV”
cardTypeSource=”{creditcard}” cardTypeProperty=”cardType”
cardNumberSource=”{creditcard}” cardNumberProperty=”cardNumber”
trigger=”{myButton}” triggerEvent=”click”
cardTypeListener=”{cardTypeCombo}”
cardNumberListener=”{cardNumberInput}”
valid=”Alert.show(‘Validation Succeeded!’);”/>
<mx:Panel title=”CreditCardValidator Example” width=”75%” height=”75%”
paddingTop=”10″ paddingLeft=”10″ paddingRight=”10″ paddingBottom=”10″>
<mx:Form id=”creditCardForm”>
<mx:FormItem label=”Card Type”>
<mx:ComboBox id=”cardTypeCombo”>
<mx:dataProvider>
<mx:Object label=”American Express” data=”American Express”/>
<mx:Object label=”Diners Club” data=”Diners Club”/>
<mx:Object label=”Discover” data=”Discover”/>
<mx:Object label=”MasterCard” data=”MasterCard”/>
<mx:Object label=”Visa” data=”Visa”/>
</mx:dataProvider>
</mx:ComboBox>
</mx:FormItem>
<mx:FormItem label=”Credit Card Number”>
<mx:TextInput id=”cardNumberInput”/>
</mx:FormItem>
<mx:FormItem>
<mx:Button   id=”myButton” label=”Check Credit”/>
</mx:FormItem>
</mx:Form>
</mx:Panel>

Using Viewstate with a Custon ItemRenderer

Hi friends, Today I learned a concept of  Using viewstate with a Custom ItemRenderer.A shopping application that displays multiple items on a page might have a custom thumbnail item renderer with two view states.

When the user rolls the mouse over the item, the view state changes: the thumbnail no longer has the availability and rating information, but now has buttons that let the user get more information or add the item to the wish list or cart.

The application item renderer’s two view states have different child components and have different component styles. The summary state, for example, includes an availability label and a star rating image, and has no border.

When the user moves the mouse over an item, the item renderer changes to a state where the picture is slightly enlarged, the price appears in the cell, and the application’s text box shows a message about the item.

Program:

<mx:VBox xmlns:mx=”http://www.adobe.com/2006/mxml”
    horizontalAlign=”center”
    verticalAlign=”top”
    mouseOver=”currentState=’showdesc’”
    mouseOut=”currentState=””>

        <mx:Image id=”img1″
        source=”{data.image}”
        width=”75″
        height=”75″/>
    <mx:Label text=”{data.name}”/>

    <mx:states>
        <mx:State name=”showdesc”>    
            <mx:AddChild>
                <mx:Text text=”{data.price}”/>
            </mx:AddChild>
            <mx:SetProperty target=”{img1}” name=”width” value=”85″/>
            <mx:SetProperty target=”{img1}” name=”height” value=”85″/>
            <mx:SetProperty target=”{parentApplication.t1}” name=”text”
                value=”{data.description}”/>
        </mx:State>
    </mx:states>
</mx:VBox>

Hello world!

Welcome to WordPress.com. This is your first post. Edit or delete it and start blogging!