The reason why Ext. blank_image_url is used to configure the instance

The default position of the image is <br/>/resources/images/default/s.gif' 

 

Recently, when Jack's window navigation example in ext was read, I suddenly realized the author's intention to do this. <Br/> the author does not explicitly specify the icon (slice) path to be applied to any image or icon that needs to be applied, <br/> CSS is used for configuration. Many application icons start with ext. <br/> the actual icon path is replaced after the CSS is loaded. <Br/> This solution completely solves the problem of skin replacement on the interface. <Br/> here is an example: <br/> In the desktop example, the initial path of the shortcut icon is to the blank images/s.gif <br/> <DL id = "X-shortcuts"> <br/> <DT id = "Grid-win- export cut "> <br/> <a href =" # "mce_href =" # "> <br/> <br/> <div> grid window </div> <br/> </a> <br/> </DT> <br/> </dl> <br/> then, in CSS, modify it to: <br/> # grid-win-plain cut IMG {<br/> width: 48px; <br/> Height: 48px; <br/> background-image: URL (.. /images/grid48x48.png ); <Br/> filter: progid: DXImageTransform. microsoft. alphaimageloader (src = '.. /images/grid48x48.png ', sizingmethod = 'Scale'); <br/>}< br/> when some components that require icon modification are dynamically created, the SRC of the icon generally points to Ext. blank_image_url, <br/> and then point to a specific icon position in CSS. <Br/> You can directly replace the CSS file if you want to skin it later. <Br/> the final practice also proves that if this blingk_image_url is not correctly configured, <br/> decoration icons defined in CSS files may not be displayed on many controls. <Br/>