View Full Version : Ext images

1 May 2007, 11:23 AM
first, thinks to all the ext team, really you're doing an awesome job.
well, i have to make a web based project running in a local network (no internet connexion); my problem is that in my case, ext core seeks for components images ( for example tree's folder and file images) from internet and not from the ext-1.0 local folder !
i included the same css files than the index ext docs

<link rel="stylesheet" type="text/css" href="ext-1.0/resources/css/ext-all.css">
<link rel="stylesheet" type="text/css" href="ext-1.0/resources/css/ytheme-vista.css">

the strange thing is that that the docs and examples work fine and not my code :((
any idea ?
best regards

1 May 2007, 11:36 AM
I think your problem has to do with this:

Look at the definition of BLANK_IMAGE_URL in sorce/core/Ext.js, and also see this thread:


You don't have to touch Ext, just add this to your code:

Ext.BLANK_IMAGE_URL = "http://your.server/path/s.gif";

1 May 2007, 12:53 PM
You also may need to prefix your links with / like href="/extjs-1.0....". This would be the case if you have root of your application in a subdirectory and if you access it as:


1 May 2007, 2:07 PM
thank you so much efege and jsakalos
i have another question about ext documentation... i don't know but (for a newbie developer like me) i didn't find the doc that perfect (like the php manual for example)... i can't guess things that easy from examples and i find the doc poor of explanations...
am i just stupid to understand ext or perhaps i'm not searching at the right place ?
and do you know if some o'reilly or other ext book will be published soon ?
thanks in advance

1 May 2007, 2:31 PM
Keep in mind that Ext hasn't been around anywhere near as long as PHP, so the base of documentation and user community, is nowhere near as big. However, we are constantly adding doc, examples, tutorials, etc. I would suggest you go thru the tutorials on extjs.com.

As far as a book goes, there are currently no plans for this. Given the current resource availability, the community and framework are better served by expanding/improving the existing documentation channels.

1 May 2007, 3:29 PM
The sequence what works for me is:

I look at en example
I try to use what I find in my app
If it doesn't work I read the doc
If it doesn't help I look in source code
And, I use firebug in any of the above steps if I need to make my app working.