Mrinal Wadhwa is a Software Architect form Bangalore, India. He is interested in User Interfaces, Databases, Data Analysis, Data Visualization, Networking, Distributed Systems, Cloud Computing, Software Design, Architecture, Scalability etc. and is working with a small team trying to bootstrap a software as a service product startup.
Along with the Custom Components in Flex 4 presentation I shared yesterday, I also gave a 15 minute lightening talk at Adobe DevSummit on Keyboard Productivity in Flash Builder, this was just a quick show and tell where I walked people through various ways of what Jeff Atwood calls Going Commando … read more
I gave a presentation on Custom Components in Flex 4 at Adobe Devsummit last week in Chennai and today in Hyderabad, here’s the slidedeck where we create an Imperial StormTrooper component
Here are two quick layouts we wrote during the meeting as I showed everyone how easy it is to write a custom layout …
Random Layout
Step Layout
These layouts are currently somewhat crude but the idea was to convey how easy it is to write your own layouts … here the code for RandomLayout … just one simple function … read more
Layouts in Flex 4 are decoupled from containers and its quite simple to define your own layout. Yesterday I wrote ConcentricLayout.
ConcentricLayout arranges layout elements in such a way that their centers are aligned and their size sequentially decreases. The width of each layout element is less than the previous element by a value specified using the horizontalGap property and the height of each layout element is less than the previous element by a value specified using the verticalGap property. If the element has an explicit width or an explicit height it still aligns its center but is not resized. You can tell the layout to force a resize of all elements and ignore their explicitly specified size using the forceResize flag
Last week I got some Illustrator files from the designer on our team, which I had to convert into Flex 4 skins. When we had planned this, we thought this would be easy … the designer makes the skins in Illustrator, we export FXG directly from Illustrator or we import them into Catalyst, do some tweaking and then export to get FXG that we can use in SparkSkins .. unfortunately it wasn’t that simple, I’m documenting some of the gotchas and workarounds I learned for anyone else who may run into the same situation.
Most of the problems we had were related to gradients, here are some snapshots …
The first strip is original graphic created in Illustrator
The second strip FXG Exported from Illustrator
The third strip is original Illustrator file imported into Catalyst and then FXG exported from Catalyst