I just found a rather alarming thing in the extjs/adapter/ext/ext-base.js file:
Anybody know what that is all about?
I just asked google.
You can read a lot about it here: http://www.google.com/search?q=extjs.com%2Fs.gif
Especially this thread: http://220.127.116.11/forum/showthread.php?t=7413
Basically the reason is that they need the image to have an absolute path. And there’s no way of knowing where the user will place the files included in the package. According to the above thread the image is included in the distribution of ExtJS and you’re encouraged to set the location of the image yourself.
MODx snippet-glossary 101:
Ditto = Content Lister -- Wayfinder == Menu Builder -- Jot = Comment Control
Yeah, I have been beating my head trying to get a paging grid with search implemented, and finally took the time to go search for this. Got the search paging grid working too, finally. extjs is really tough to get into, but I can see the power of it. Of course, it would help if I could get my backend sql queries right the first time
You’re supposed to set it to override that default in the beginning of your AJAX script:
Ext.BLANK_IMAGE_URL = 'http://localhost/bmp2/assets/js/extjs/resources/images/default/s.gif';
It can be set relative, but in this case I decided to go for the overkill. Lovely little data grid with search and sortable columns.
Since we’re going to try a whack at getting MODx to Ext2 for the 097 release, I’ve not changed this yet. And I highly recommend never changing actual Ext files - it makes upgrading a nightmare.
Edit: Actually, I’m dumb. I already did that: line 56 of manager/templates/default/js/sections/layout/header.js
Anyway, yes. This will be working locally without reference to extjs.com in the releases.
shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect
Well, hopefully the difference isn’t so great that I’ve wasted all this time and aspirin learning how to get around in 1.1.1