Custom Query (18300 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (58 - 60 of 18300)

Ticket Resolution Summary Owner Reporter
#11639 patchwelcome IE: dojo gfx text's event handle issue Eugene Lazutkin JayZ(zhouxiang)
Description

When you combine an event to a dojo.gfx.text, for example: surface.createText(text).connect("onclick", function(e){

alert("triggered")

})

In firefox, chrome, safari..., the event(onclick) will be triggered when you click on the boundingbox of the text: please refer to handler_firefox.png

But in IE, the event(onclick) will only be triggered when you click on each word of the text itself exactly, the event will not be triggered even when you click on the blank area between each word of the text, or even the blank area within each word. please refer to the hander_IE.png

#11686 fixed Spider Chart Eugene Lazutkin JayZ(zhouxiang)
Description

The spider chart consists of a sequence of equi-angular spokes, called radii, with each spoke representing one of the variables. The data length of a spoke is proportional to the magnitude of the variable for the data point relative to the maximum magnitude of the variable across all data points. A line is drawn connecting the data values for each spoke. This gives the plot a star-like appearance and the origin of the name of this plot. Spider charts are useful when you want to look at several different factors all related to one item. spider charts have multiple axes along which data can be plotted.

The "spider chart" can be a format commonly used by management consultants to show their clients how an organization compares with those in similar companies. It also can be used as the control of quality improvement to display the performance metrics of any ongoing program. Furthermore, it is also being used in sports to chart players' strengths and weaknesses. For example, you could use a spider chart to compile data about a wide receiver on a professional football team. On one axis, you could plot the percentage of passes caught. Another axis would show his yards per completion; another, his completions per 100 plays; another, blocks made; and a final axis might show his interceptions. So far as we can see, the spider has a broad application area.

Spider charts differ from radar chart in that a spider chart is a chart that has N "y" axes while radar chart has only one "y" axis, all radiating from a central point, where each "y" axis represents a specific category. For example, there are 5 "y" axes: GDP, area, population, inflation and growth here. The radar chart, however, instead of being drawn in a typical linear X/Y space, the radar chart is drawn using a circular plot, with specific X values being shown using an arbitrary number of spokes drawn from a center point. These charts are useful for showing data over a cyclical set of values (for instance, hours of a day, minutes in an hour, etc.). With a radar chart, data is plotted in much the same way as with a typical line or area chart. Actually, the radar chart is somewhat similar with line chart, the major difference between them is: line chart has a "straight" X axis while radar chart has a "circular" X axis, and the orientation of their Y axis is opposite.

demo snapshot from xiang zhou

#11732 fixed dojo.query comments error alex JayZ(zhouxiang)
Description

Following comment error:

//dojo.query() supports a rich set of CSS3 selectors, including:
//
//	* class selectors (e.g., `.foo`)
//	* node type selectors like `span`
//	* ` ` descendant selectors
//	* `>` child element selectors 
//	* `#foo` style ID selectors
//	* `*` universal selector
'''//	* `~`, the immediately preceeded-by sibling selector
//	* `+`, the preceeded-by sibling selector'''
//	* attribute queries:
//	|	* `[foo]` attribute presence selector
//	|	* `[foo='bar']` attribute value exact match
//	|	* `[foo~='bar']` attribute value list item match
//	|	* `[foo^='bar']` attribute start match
//	|	* `[foo$='bar']` attribute end match
//	|	* `[foo*='bar']` attribute substring match
}}

The two lines in bold, the `~` should be "the preceeded-by sibling selector" and the `+` should be "the immediately preceeded-by sibling selector"
Note: See TracQuery for help on using queries.