Are you sure you disabled it at project level?
Before I went to netbeans I was using Indigo, this is the builder's page of my ExtJS project:
And this is the "about" of my indigo:
Are you using spket plugin?
I start using it but the benefits were to marginal so I decided to get rid of it.
Sorry for the delayed answer...
Thank so much por the help!
To other people that could have the same problem (I did that):
1.- option menu "help" in Indigo -> "install new software"
2.- add "http://www.spekt.com/update" and install all plugins
4.- download the "*.jsb2" file from sencha web (I found it in the forums...)
5.- put the jsb2 file in the extjs root (side by side of the ext-all.js file, for example)
8.- Restart the IDE if necessary...
9.- the end
a view days ago I tried to create a Web-Project with ExtJS in Eclipse (Juno) for a student research project. There had never been any problems creating other Web-Projects in Eclipse until I tried to use ExtJS 4 (ext-4.1.1-gpl.zip) within my project.
When I imported the (zipped or unzipped) ExtJS-folder into my project I had the same problem which is described at the beginning of this discussion by arnoldc. Eclipse simply stuck in “Building workspace” and eventually dies out with java heap space error.
Tried virtually every solution I could find on the web:
But nothing changed.
- Moved sdk.jsb3 from “extjs-4.1.1/build” to “extjs-4.1.1” and remapped wrong path specifications “../platform/” to “src” (and “src/src” to “src”)
- Installed “Spket-PlugIn” for ExtJS and replaced “com.spket.js_1.6.23.jar” with the latest version
- Configured an ExtJS-4 Profile via Spket-PlugIn for the customized sdk.jsb3-file and used “Spket JavaSkript Editor” as default for *.js
- Modified eclipse.ini up to -Xms256m -Xmx4096m
My Question: Is there something more to do that I missed or did I do something wrong?
Would be grateful for any idea (beside switching to another IDE).
I'm currently using Juno with ExtJS without problem.
Then, instead of putting whole ExtJS distribution just include whatever you need, for example this is the structure of my WebContent:
Note that my html entry pages includes ext-all or ext-all-debug.
The first time I imported ext-all-debug.js (or ext-all.js) into the project it took a little while until “Building Workspace” was finished. But every further time “Building Workspace” works fine.
Thank´s a lot for the tip of using ext-all.js or ext-all-debug.js instead of ext-debug.js in html entry pages, too. Just ask myself why ext-debug is recommended for the pages under http://www.sencha.com/learn/getting-...rted-section-2 and what is it good for? (Maybe I will find out later)
Finally I successfully created a first “Hello Ext”. :)
(Also it works with the original eclipse.ini file. So, for a start, there is no need to crank up memory.)