I did one ExtJS application on one PC and I want it to continue developing on another one. I copied the folders, initialized the workspace.json and ran sencha app build. After sencha app watch command I don't get any errors. However there is nothing on the screen and I get 404 messages for the JavaScript files even though they are existing in specified folders.
What am I doing wrong here?
Btw It is Sencha ExtJS 6 version.
For the description of the image, the ext folder is missing.
It is common to give this error when you do not have ext folder on the root application folder.
Related
I want to make a web app that is very similar to the extj5 portal example: http://dev.sencha.com/extjs/5.0.0/examples/portal/index.html
I would like to copy it to a different directory and start coding.
Here are the steps I am taking:
1) Copy portal directory to my working directory.
2) Cd into portal
3) Run the following on the command line.
sencha app upgrade ext-5.0.0 // Ext 5 and this app should be in the same directory
But when I do so, I get:
$ sencha app upgrade ext-5.0.0
Sencha Cmd v5.0.2.270
[WRN] Did not locate framework package
[WRN] Failed to resolve package ext-theme-neptune
[WRN] Failed to resolve package sencha-charts
[ERR] Theme "ext-theme-neptune" not found
[ERR] Required package "ext-theme-neptune" not found
Any advice on the proper way to do this? Ruby is properly installed and I was able to successfully go through the extjs 5 tutorial (generate app, watch app, etc.)
Sencha Cmd uses a lot of metadata, so your best bet is to generate a brand-new app in a blank folder first. Delete everything EXCEPT the /.sencha/ folder.
Then copy/paste the portal example (everything EXCEPT the /.sencha/ folder) into your new app.
You will also need to copy the /examples/ux/ folder, and then update the app.json file -- pointing classpath to the correct ux folder.
Normally this process would be easier, but the Ext JS download is essentially a "workspace", so copying one of the examples into a new place will miss a lot of the workspace's assumed structure (namely, the framework!)
So I am trying to set up another ExtJS (4.2.1) dev workstation I've got Ruby 1.9.3, Sencha Cmd 4.0.4.84 installed and latest Java VM too.
The build won't work on this one though, I'm getting:
[INF] executing compass using system installed ruby runtime
Errno::ENOENT on line ["38"] of C: No such file or directory - C:/devtfs/CustomerPortal/CustomerPortal.UI/Content/Customer_Portal_UI/build/temp/production/Customer_Portal_UI/slicer-temp/.sass-cache/82daaa66b7a4761963814fd25131bf0f81370ec9/Customer_Portal_UI-example.scssc
82daaa66b7a4761963814fd25131bf0f81370ec9 folder does exist, but it's empty.
I've tried
sencha ant clean
sencha app refresh
sencha app build --clean
No go. Ever seen this issue ?
Thanks!
EDIT: Hmm, even after this error, the application seems to be running fine on the Sencha web server, but the index.html file is the last thing that's not created in build/production.
We have an app that was not initially created with Sencha Cmd.
While we will eventually restructure the app to adhere to the structure that works best with Sencha Cmd, for now we just need to know the steps to deploy the app to production in our case.
1) For example, I've heard we need to minify the code by building with Sencha Cmd. Can we do that even if our app was not initially created using Sencha Cmd?
2) I've also heard that we can use Sencha Cmd to ensure that the minified file only contains the classes that are actually used by our application (even reducing the number of ExtJS core classes included). Is that true and if so, can we do that even if our app was not initially created using Sencha Cmd?
3) Anything else to deploy our app to production, especially considering our app was not initially created using Sencha Cmd?
Thanks much in advance!
1) We can deploy & compile our application , even if we have not created the project using sencha CMD. We have to follow the standard application structure given in their tutorial/docs
2)Yes by compiling our js files using sencha compiler/sencha cmd minifies our code to a single file say xyz.js file, so in webapps folder only one file is needed not all other js files containing src code also the import statement in some parent jsp files need to be updated accordingly, instead importing "app.js" . By this process the performance is upgraded as only required/used components are complied.
Note : While compiling our src files,If any component say button,grid etc in any file is used without mentioning its xtype in 'requires[]' field in that particular view file then errors are thrown which are very difficult to track, So make sure all requires[] are updated.
I am able to wrap sencha APP in window Phone 8 if using UIView Control or PhonegapView and accessing app over localhost.
But not able to package app when putting all pages in www folder (Tried with phonegap also).
Other Non Sencha web APP works fine.
I have searched on forum . Many people are facing same issue.
Can any one post a successful solution?
I am using latest Sencha touch 2.3.1
I am getting that first sencha need to be packaged and then it could be put in www folder.
But i am not able to get the correct packaging required which can work.
I had a similar problem; instead of using the package files, I used the command:
sencha app build native
and I used the app.js and app.json files generated that were created in the path
build/native/<YOUR_APP>
I'm currently toying around with Sencha Touch 2.2.1 and am trying to get it to run offline using an HTML5 cache.manifest. Anyone know how to get this to work? I can only find old guides from the last version which no longer seem to work. After some fiddling I have my manifest as follows:
CACHE MANIFEST
index.html
app.js
touch/microloader/development.js
But this seems to throw errors in the development.js script when it attempts to send fetch the app.json file. Are there some Sencha settings I have to adjust for offline mode? Thank you for your help.
After some hunting around it seems this feature is present in Sencha Touch 2.0 but still a bit incomplete. To get it to work, do as follows:
You must have the Sencha command line installed (which you probably
already have since it's required to make a Sencha project in the
first place).
Navigate to your project's parent directory in command line
Use the sencha app build production command to "compile" your project into a single file
Navigate to your production directory in YourApp/build/YourApp/production
Chane the extension of cache.appcache to cache.manifest
Edit the index.html file's html tag so that manifest="cache.manifest"
Ensure your server is configured to serve .manifest files correctly
Now your production code should have a working cache manifest. Note you only need to change the extension so that the app works on iOS, it seems to work in browser (or at least Chrome where I tested this) with the .appcache extension.
Compiling to production appears to be the only way to generate a cache manifest file but you can use this same file in a testing build if you don't want all the code minified for debugging. Of course you'll have to copy your manifest over and ensure it's referenced in your testing build's html tag.
All in all Sencha clearly needs to update their documentation here but I'm glad I found this out. I only tested this with a super basic, static, two page application. Hoping it scales decently.
Instead of changing manually your production package, you should change in app.json lines after 'appCache'. Here is what will be generated by Sencha CMD and will work just fine after running sencha app build production.
You can see a live example here https://github.com/flrent/ConfMate/blob/master/app.json#L79