Description of the files: ext-all.js, ext-debug.js, ext-all-debug.js, ext-dev, ...

[brianpolk]

Sorry if the answer is right under my nose, but I am looking for documentation on the various js files in the root folder. I have come to understand bootstrap.js, and I often use ext-all-debug.js during development. However, I have found that ext-debug.js is not comparible to the src/debug.js in V3 (I miss the console that it created.) What is ext-dev.js? ext-all-dev.js vs ext-all-debug.js, etc? I have found hints a bits on the forum, but would like to see a technical description of the intention and purpose of each of these files. Also, if there is a way to get the debug console functionality in IE (including IE6) that was provided by src/debug.js, I would appreciate that as a secondary question.

I have searched the forums, blogs, and readme / welcome / doc system and cannot find the intent and purpose of these separate files.

Thanks, and keep up the great work!

[tonyx]

bump! I am wondering about the same thing myself.

[edspencer]

We're simplifying all of this in 4.1 as it's clearly somewhat confusing at the moment. Here's what they do in 4.0:

ext-all: minified, no JSDoc, no console warnings
ext-all-debug: non-minified, with JSDoc, no console warnings
ext-all-dev: non-minified, with JSDoc, with console warnings

ext-all and ext-all-debug are functionally equivalent, whereas ext-all-dev throws console warnings when you do things like use deprecated APIs or misconfigure components. I don't believe we have ported the debug console from 3.x across yet

[gianmarco]

I think there's a bug in ext-dev.js:

When i switch from ext-debug.js to ext-dev.js, the path of 'Ext' namespace is lost. This is because extjs path is extracted by searching for included script with the following name:

/ext(-debug)?\.js$/

And obviously this is not the case for ext-dev.js.

A woirkaround is to specify manually ExtJS path, but i think that ext-debug and ext-dev should be seamlessly interchangeable..

@EdSpencer: should i post this in bug forume thread?

[yyjia]

You need to set path for Ext when you use ext-dev.js . I think you should always use ext-dev.js instead of ext-debug.js when you intend to use dynamic class loading feature during your development phase.

[dougbieber]

Not completely true. As a test, I decided to use Ext.sum() and Ext.type() which is deprecated in 4.0.6. There are no messages in the console at all when using ext-all-dev.js..

[gianmarco]

ExtJS 4.1 GA has been released, but seems that it has become worse, now there are much more files than before..

the files are:

ext-all-debug-w-comments.js
ext-all-debug.js
ext-all-dev.js
ext-all.js
ext-debug-w-comments.js
ext-debug.js
ext-dev.js
ext-neptune-debug-w-comments.js
ext-neptune-debug.js
ext-neptune.js
ext.js

during development i use:

ext-dev.js


and during production i use (i include the whole extjs lib):

ext-all.js

Is this still correct in 4.1?
What is the "proper" way in 4.1?

[wmendoza]

I also had the same doubts, and i've come up with the following:

Production: ext-all.js

Development: ext-all-dev.js (It's really useful to use Ext.log function for debugging)

[whirling dervish]

We're simplifying all of this in 4.1 as it's clearly somewhat confusing at the moment. Here's what they do in 4.0:

ext-all: minified, no JSDoc, no console warnings
ext-all-debug: non-minified, with JSDoc, no console warnings
ext-all-dev: non-minified, with JSDoc, with console warnings

ext-all and ext-all-debug are functionally equivalent, whereas ext-all-dev throws console warnings when you do things like use deprecated APIs or misconfigure components. I don't believe we have ported the debug console from 3.x across yet

So now that 4.1 is out, are these descriptions still accurate?

[pmarko]

Bump ...