use ExtJS for views (prob to include and load it)

[eluser]bayrem[/eluser]
no I empty the cash and all goes ok.

the alert load :d

so you think that I must replace the extjs files ?

those files are broken !!!

any suggestions ?

[eluser]Michael Wales[/eluser]
If you cleared the cache, and reloaded the page, and saw the alert() you are loading the file fine - it's an issue with the library itself.

[eluser]bayrem[/eluser]
so you think that if I replace the all extjs folder all goes fine ?

thx

[eluser]bayrem[/eluser]
thank you very much for you're help and reactivity

the prob was because of the extjs libraries calls was not in the good order, for those how will have the same prob. Here is the answer, the right order :

Code:

< link rel="stylesheet" type="text/css" href="<?= base_url(); ?>ext/resources/css/ext-all.css">
&lt; script type="text/javascript" src="&lt;?= base_url(); ?&gt;ext/adapter/ext/ext-base.js"&gt;< / script>
&lt; script type="text/javascript" src="&lt;?= base_url(); ?&gt;ext/ext-all.js"&gt;< / script>
&lt; script type="text/javascript" src="&lt;?= base_url(); ?&gt;ext/examples/examples.js"&gt;< / script>
&lt; script language="javascript" src="&lt;?= base_url(); ?&gt;ext/examples/window/layout.js"&gt;< /script>

Thanks twice for you're help.

Maybe will need you later in a advanced stage

LOL

[eluser]esra[/eluser]
There is a document on the EXT JS site that describes the loading order of various files. For some silly reason, this document is referenced on the page where custom ext_all files can be generated and some of the older 1.1 documentation pages. One of the fundamental concepts of AJAX-like technology is the use of a base set of CSS ids with corresponding Javascript functions. Thus, javascript code for both the EXT base and the all classes are dependent on the CSS ids defined in the base css file. Similarly, the base javascript file includes utility support for Observable and other utilities which are used (are in the class hierarchy) of many EXT JS widgets and other code. Thus ext_all is dependent on the base utilities.

A similar problem can happen with examples.js when you use the example code as the basis for your own code. I use examples.js as the basis for a common.js file which is stored above the extjs directory. Examples.js includes some basic code required to handle the window state files which are stored under examples/states/. That is, the states files are dependent on code in examples.js. Since I usually strip out the examples directory from my final distributions, I moved the examples/states/ javascript files and the common.js file (example.js) to a directory above extjs to ensure they are always available to my templates. You only need to do this if you remove the examples directory from your extjs directory for reduce library size and also need to manage window states (which appears to be so because you are using layout.js).

The various inheiritance diagrams included in the EXTJS API documentation help a lot when isolating problems like this because they show dependencies. A utility function such as Observable in EXTJS is akin to a helper in CodeIgniter.

[eluser]bayrem[/eluser]
many thanks for the details.

:d