Adobe 38039927 Extended User Guide - Page 297

ADOBE FIREWORKS CS3 293 Extending Guide var classDef = new Object(); classDef.margin = {top:0, right:3, bottom:10, left:3}; classDef.padding = {top:30, right:10, bottom:10, left:10}; classDef.sizeOffset = {width:10, height:0}; classDef.customValues = {staticValue:"static"}; classDef.attributeProperties = ["staticValue", "name"]; classDef.styleProperties = ["color"]; classDef.defaultProperties = ["x","y","width","height"]; classDef.namespace = {ns:"http://www.example.com/2007/mxml"}; Widget.elem.customData["flexClassDefinition"] = classDef; } function applyCurrentValues() { var vals = Widget.elem.customData["currentValues"]; Widget.GetObjectByName("label").textChars = vals[1].value; Widget.GetObjectByName("label").pathAttributes.fillColor = vals[2].value; Widget.GetObjectByName("disabled").visible = !vals[3].value; } switch (Widget.opCode) { case 1: setDefaultValues(); break; case 2: applyCurrentValues(); break; } A document containing this rich symbol that is exported using the MXML and Images export would result in the following MXML document. Star { color:#FFFFFF; } With the definition of flexClassName, the element in Fireworks exports as a Star MXML tag. Notice how the properties defined within attributeProperties became attributes and the property (color) defined within styleProperties became part of the Star style. The only default properties created were those defined in defaultProperties; x, y, width, and height. Because a namespace was defined, the tag was given the correct prefix and it's URI was defined within the Application tag. In Fireworks, the star in this example was 147 x 138 but exported with a width and height of 157 x 138 in MXML because of sizeOffset. Though not apparent in this example, margin and padding would also play a part in how this element is exported.