ooops : wrong thread
Message was edited by: m1kal_
Why are you bothering with XML ? Just create a single class with multiple view states. Then you can have a presenter decide which view state the component should take on based on whatever data is in your model ( which could even be XML) .
> Why are you bothering with XML ? Just create a single class with multiple view states.
I am bothering with XML because I need to subclass the component. I am already using view states in the component. As I mentioned in the OP, I am trying to subclass the component. Is it possible to do this? If so, does anyone know the syntax?
do you mean drop-in component with custom encapsulated logic? and in .mxml?
You could follow that article:
(Example: Creating a skinnable Spark component)
this is part of wider documentation on subclassing components subject:
This looks like it might be the solution I'm looking for. The article on Composite Components seems promising. I'm away right now (Memorial Day weekend, of course) but I will try this out when I get back.