This is an example developed in Flex 4 Gumbo or Flash Builder 4 of a text input that displays a prompt inside of the component when no text has been entered and the component is not focused.
View Demo Here (right click to view source code)
If you’re considering building a RIA, you have a few choices of technology, including Flex, Ajax, and Microsoft Silverlight. If you look at these options objectively, the development effort required for each and the resulting user experience is roughly the same. One of the benefits of Flex is its reach — the Adobe Flash Player, upon which Flex applications run, is already installed on about a billion computers wordwide!
Of course, Ajax also uses technologies that are installed on almost every computer in the world — JavaScript, XHTML, and CSS. One of the downfalls of Ajax, however, is that cross-browser compatibility can be difficult to achieve. What might work in one browser for example, Firefox might not work in another such as Internet Explorer, so the debugging process has the potential to become difficult and long-winded.
Microsoft Silverlight, on the other hand, is similar to Flex in that it runs on a browser plugin. Silverlight, however, has yet to reach the installed userbase of the Flash player.
If you’re just starting out with building RIAs, you should definitely try all of them to see which one you like best and find easiest to work with — each of Flex, Silverlight and Ajax has its advantages and disadvantages. In my opinion, Flex is definitely the best RIA development technology available. Additionally, if you’re a fan of the Adobe Creative Suite, it’s good to know that many of these tools (Flash, Photoshop, Illustrator, Fireworks and so on) have Flex component integration built into them.
Here are 5 handy free tools to speed up your website. Check it out here.
The Image Gallery developed in Flex showing the Image loading progress status using Progress Bar. Check it out here. You can view its source code by right clicking on the application.
Visit this link : http://dev.meshenergy.com/test/passwordmeter.html
Deep Linking is a term that describes the support for URL based navigation in applications that are not a collection of HTML pages.In Flex 3, Deep Linking is implemented using fragments, the portions of URLs after the “#”. For example, in this link http://mysite/page.html#view=1 the fragment is view=1.
Adding support for Deep Linking to your Flex 3.0 Application is relatively simple. The basic steps are:
1. turn off the HistoryManager (the HistoryManager also uses the BrowserManager and will interfere with your fragment processing).
2. initialize the BrowserManager with a default fragment and title
3. determine when you want to update the fragment and call BrowserManager.setFragment.
4. listen for events from the BrowserManager
5. when you receive an event, interpret the fragment and change your application accordingly
Deep linking only works with certain browsers. The following browsers support deep linking:
* Microsoft Internet Explorer version 6 or later
* FireFox for Windows and Macintosh
* Safari for Macintosh
Some great links for deep linking with examples:
Handling Flex 3’s deep linking in a Cairngorm architecture
Deep Linking with TabNavigator
Deep Linking with ToggleButtonBar
There is no tooltip for datagridColumn.But instead its dataTipField. The following is the syntax:
<mx:DataGridColumn headerText=”name” dataField=”name” dataTipField=”name” showDataTips=”true”/>
 | Kalavati Singh on Flex – ProgressBar chang… |
 | Gopi Krishna on Flex Application – Image… |
 | basker on Flex Application – Image… |
 | Pradip Jadhav on Flex Application – Image… |
 | John Isaacks on Flex Application – Image… |
