Reason for configuring Ext. blank_image_url

When analyzing the extjs source code, I do not know why to configure the blingk_image_url attribute in ext. In the future, I have not deliberately studied the details, so I have a tendency to stop ......

However, when I recently looked at Jack's window navigation examples in ext, I suddenly realized the author's intention to do this.

The author does not explicitly specify the icon (slice) path to be applied in some places where images or icons need to be applied, but is configured through CSS, many application icons start with ext. replace the blingk_image_url with the actual icon path after the CSS is loaded. This action completely solves the problem of skin replacement on the interface.

Let's look at an example:

In the desktop example, the initial path of the shortcut icon is to the blank images/s.gif

<DL id = "X-shortcuts">
<DT id = "Grid-win-shortcut">
<A href = "#">
<Div> grid window </div> </a>
</DT>
</Dl>

Then, modify it in CSS:

# Grid-win-Shortcut IMG {
Width: 48px;
Height: 48px;
Background-image: URL (../images/grid48x48.png );
Filter: progid: DXImageTransform. Microsoft. alphaimageloader (src = '../images/grid48x48.png', sizingmethod = 'Scale ');
}

 

When some components that require icon modification are dynamically created, the SRC of the icon generally points to Ext. blk_image_url, and then points to a specific icon position in CSS.

Then, you can replace the CSS file directly.

The final practice also proves that if this is not correctly configuredThe blank _ image_url may not display the decoration icons defined in the CSS file on many controls.