Mediate a Flex 4 Skin
Has anyone thought about creating a mediator for a skin? along with another mediator for a component? or is that just ridiculous ^_^
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Joel Hooks on 25 Jun, 2010 08:24 PM
I don't know if it is ridiculous, but I firmly believe the skin should be managed by its host and not external forces.
2 Posted by Samuel Asher Ri... on 28 Jul, 2010 09:18 PM
Encapsulation of code (what code manages itself and what doesn't) is a sliding scale.
a) In general I think that a mediator should manage all of its 'UI' (in this case Flex Component and that Flex Components Skin).
b) However you may want to reuse a skin across components.
In the latter case the skins as3 code could be placed;
1. In the script tag of the mxml file of the skin itself (adobe's solution)
2. In the Flex component (not recommended)
3. In the mediator for the Flex component (RL's general solution, and likely ideal for 'a' above)
4. In a superclass of the mediator for the Flex Component (likely ideal for 'b' above).
Hope that helps. I'm still learning too!
[email blocked]
Stray closed this discussion on 10 Feb, 2011 05:31 PM.