uncleflo
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 2 bookmarks
howto information development guide reference administration design website software solution service product online business uk tool company linux code server system application web list video marine create data experience description tutorial explanation technology build article blog learn world project boat download windows security lookup free performance javascript technical control network beautiful london support tools course file research purchase library programming image youtube example php construction html quality install community opensource computer profile feature power browser music platform mobile work user process database share manage hardware professional buy industry internet dance advice developer installation 3d access material camera customer travel search test standard review documentation css money engineering webdesign engine develop device photography digital api speed source program management question event phone discussion simple client story water marketing app yacht content setup package interface fast idea account communication cheap compare script study easy live market google resource operation startup monitor training
Tag selected: skinning.
Looking up skinning tag. Showing 2 results. Clear
Flex 4 Component States vs. Skin States « Saturnboy
Saved by uncleflo on January 24th, 2012.
Flex 4 introduced an awesome new skinning architecture. Among other things, the new architecture provides significantly better separation between a component and its skin. Flex 4 also promotes the use of states to the point where they are virtually mandatory in any non-trivial app. And that brings us to the question of the day: How do you communicate state information from the host component down to its skin? As always, we’ll dive into some examples to explore how things work. In our first example, we just want our skin to mirror the states of its host component. So, we begin with a simple component based on SkinnableComponent. And then we add three states: base, happy, sad. Here we discuss the code.
framework information guidelines development invalidate current communication component state spark skinning skin flex Adobe Flex
WS-Blog » Quick tip (Flex 4): Using generic skin classes
Saved by uncleflo on August 17th, 2011.
For skinning Flex 4 components you have a lot of great options. One way is using a custom skin class, which extends a Skin or a SparkSkin class and defines all needed style properties by itself. Imagine a custom button skin, which is more complex than the standard Spark ButtonSkin. It declares additional gradients, rectangles, transitions etc. If you code all needed values for any style properties within this skin class, you may have to create another button skin class for using only one or two different style properties. Doing this, the amount of skin classes can be increased rapidly! A better approach is creating generic skin classes. Such a skin class gets most of its properties from CSS declarations of its host component. So all needed styles can be defined using plain CSS and won’t be hard-coded anymore, even custom style declarations. That’s very simple to do and saves a lot of extra skin classes.
flex button css skinning look web development blog feedback solution integration skin code
No further bookmarks found.