It’s a common requirement for e-mail or password inputs – the second input should not be copy pasted from the first one, to make sure it’s what the user wanted to put in. When using spark my Flex 3 method didn’t work, so just in case someone needs to do the same thing, here’s the code for spark components:

It will also work with a TextArea.

When looking at some old project folders I’ve found one of the first skins I’ve created while starting with the Flex 4 skinning model, and I thought it might be an interesting case to look at, source code is included at the end of the post. It’s based on a really nice design done by Adrian Pelletier. What we’ll try to do is create a button which looks more or less like one of his button designs:

What makes it a good design is not only the way it looks but also the way the Photoshop file is created – it’s mostly based on shapes and layer effects which are easy to translate to Flex skin code.

Styling a Flex 4 Button

The Flex 4 skinning model is different from the one used in Flex 3, to keep the introduction short, let’s just say it’s now much easier to create programmatic skins, and you can do it with newly introduced MXML tags. If you ever used Degrafa to skin your components it’s should be fairly familiar, if not please check the example code. The basic usage is straight forward – you need to create a mxml file and you can start putting the new tags to design the skin.

Let’s start with the shadow behind the button, as you can see on the picture above it has 3 parts – a gradient fill, a stroke and an inner shadow, and all of them thrown on a shape of a rounded rectangle. Let’s translate this to graphic tags. First of we need that rounded rectangle, so we define a Rectangle with the corner radius using the new tags:

That’s how easy it is to create shapes using the new syntax. Next we need to define a fill, which according to the Photoshop design is a linear gradient starting from color 0x0f2835 and ending with color 0×153445. We also need an inner drop shadow on it, so let’s add it. We also need a stroke above all this, so we need to add another rectangle which will not have the drop shadow on it, and will define that gradient stroke, just like the design. A few minutes later we have:

It’s not the shortest listing, but remember that I’m only copying the settings from the design. The final flash result looks like this:

It’s almost a easy to create the rest of the design, take a look a the working button with some Flex magic thrown in to get nice transitions between states (viewsource enabled), and after the jump, I’ll quickly point to different parts of the design which are used in the ButtonSkin.mxml

Result

What makes a skin – looking at ButtonSkin.mxml

First of you should define a component for which the skin is designed.

Next you need to define all the states which are defined by the host component (you can check this info on livedocs) which is done in this code:

After that’s done you also need to put the parts of the skin that the host components assumes your skin will have (this is called skinning contract and I’ll write a post about it when I have some time). In the case of Button we need to display a single string (the button label as stated in livedocs) we’re going to use a Label for that and give it an id of labelDisplay according to the contract.

Than we can start putting in the graphics, using the same tags we used while creating the shadow. The only additions is that the values of the gradients change depending on the state, thanks to the new state syntax in Flex 4 it’s much more readable – there’s a different color when the button is in an over state (color.over) and a different one when the button is in the down state (color.down)

To add the smooth color fades between states we also define a bunch of transitions which work on our gradient entries.

Feel free to download the source code and play with it, hopefully it will be a good starting point.

Download source code.

There’s a new project on Adobe Open Source called FlexPMD (if You’re wondering what PMD stands for the answer is simple – nothing). It’s a tool that scans Actionsript and MXML code and points out bad practices, unused variables, etc. Really helpfull if you’re trying to keep the code clean and get a habit of  coding really nicely.

To try it out you really just need to go to the download page, get one of the versions (I’ve tested the command line one on windows and it works very good), generete a ruleset file using the web tool (link on the same page), and that analize the output XML file (you can use the simple web tool which is also provided on the download page).

I’ve put both the jar files and the ruleset (called pmd.xml) in “F:/Flex SDK/Tools/FlexPMD/” so the command to run it for me looks like this:

java -Xmx256m -jar “F:/Flex SDK/Tools/FlexPMD/flex-pmd-command-line-1.0.RC3.jar” -s “F:/THE/DIRECTORY/WHICH/TO/ANALIZE/” -o . -r “F:/Flex SDK/Tools/FlexPMD/pmd.xml”

It might be good to point out that you don’t need to analize the whole project but can also run the tool on any directory in it, which generates files which are easier to read, especially if you’re just starting to clean a big application.