If you are not sure about the use of design.xml inside the flex component packaging, please go though my previous article(Custom components), where I faced some problem regarding categorizing my own set of components.
Design.xml plays a vital role in creating a new new tree child inside the flex components panel. Here is a simple design.xml example.
-
<?xml version="1.0" encoding="UTF-8"?>
-
<design>
-
<namespaces>
-
<namespace prefix="ns" uri="http://www.nvish.com/2008/ngauges"/>
-
</namespaces>
-
-
<categories>
-
<category defaultExpand="false" id="myCuteComponents" label="myCuteComponents"/>
-
</categories>
-
-
<components>
-
<component category="myCuteComponents" id="com.ex.CuteLookComp" name="CuteLook" namespace="ns" />
-
</components>
-
</design>
Namespace node lets you automatically define the namespace without defining any code in the mx:Application attributes. prefix is the namespace name and you must enter the uri that you are defining for the manifest.xml file.
Category tag gives the information about the category name and let you set the ids of the categories.
Components are now kept inside the components node and each component defines a category for itself, an id tha tells which class it reffers to , a name that is displayed and obviously a namespace where it will have its presence.
Hope this will help you, and other problems related to it will be explored in near future.