well actually i have a good looking skin for a text input but unfortunately there are few bugs in Flex SDK when a textinput has a skin cladd but i got a work around for it now using the text input over the skin (code) so its working for now.
anyways thanks for you response

Lisa

Sorry but you can’t do that. What do you need on the Spark TextInput that isn’t there?

-James

Thanks,
Lisa

-James

It’s not quite using the skin properly.

The limitation of Halo skins were that they weren’t DisplayObjectContainers, so you could only put graphics in them, no DisplayObjects, but this was easily solved by creating a couple of custom base skin classes that extended Sprite. The other problem was being able to affect the object that displayed the text as in mx, the TextField was inside the mx:Button itself, where as in spark this has be removed and you have to add an object to your skin to display the text. This was also possible to get round as the TextField inside an mx:Button is the first child added, so it was possible to access this from your skin via getChildAt() and set it’s visible property to false, then adding your own object to display the label inside your custom skin and populating its text using the label property on the mx:Button.

This is not was happening here though. The SimpleText object you have inside you skin is being totally ignored by the mx:Button and no String is ever added to it (as the Button has no idea it should do anything with it). Instead the String that is visible is the protected TextField inside the mx:Button.

You can see this by adding your skin to a spark:Button, You’ll see that your label on your spark:Button has a transition on its color, unlike the mx:Button where the color changes immediately. Here’s an example, and for the purpose of making the color transition clearer I have made the start colors red.

The default skin for an mx:Button in Flex 4 is the same skin that is used for the spark:Button (i.e. spark.skins.default.ButtonSkin), but the object that is in the skin to display the String is ignored and the TextField inside the mx:Button is used, as in the above example.