When you create your custom actions file as long as you use the form
id="[com.blinex.charts.AreaChart]" for your classes then you’ll get code hints on strongly typed variables. The id must be the fully qualified class name and must be enclosed inside square brackets. This provide code hints both for variables declared using the fully qualified name and when the class is imported.
To get the code-hinting on the colon, the list of classes, you need to add a new folder to you custom actions that lists types. Here’s an example from our B-Line Charting Components 3.0, which will be released any day now.
<folder name="Types" id="Types" index="true" tiptext="Types that can be used for strong typing" helpid="0"> <string name="AreaChart" tiptext="AreaChart type" text="AreaChart" helpurl="Help/BLineCharting30/content_72c6061a.htm" /> <string name="BoxChart" tiptext="BoxChart type" text="BoxChart" helpurl="Help/BLineCharting30/content_23f3e2f8.htm" /> <string name="BubbleChart" tiptext="BubbleChart type" text="BubbleChart" helpurl="Help/BLineCharting30/content_8497b033.htm" /> . . . </folder>
There is a big catch though, the suffix style code hints don’t support id’s that have a period in them. If you’re going to set up suffixes you have to use an id such as
id="comblinexchartsAreaChart" which of course breaks the typed hints.
So, component developers have to choose–do they want to support typed hints or suffixed hints?