I have a licensed version of extjs 6.2.0. I tried to run examples by opening index.html in folder ext-6.2.0\examples . The similar page gets opened like shown in the link http://examples.sencha.com/extjs/6.2.0/examples/, but when I try to go further by clicking on options shown on page say Kitchen Sink (Classic), instead of showing page like http://examples.sencha.com/extjs/6.2.0/examples/kitchensink/#all, directory structure (...\ext-6.2.0\examples\kitchensink) gets opened in browser.
You need some kind of web server to make this work. Luckily enough, Sencha Cmd has a built in one. So, assuming you have Sencha Cmd installed, here are the steps to get this working:
from your terminal navigate to the ext-6.2.0 folder (cd ext-6.2.0);
from there, run the sencha web start command;
open the address where the server has started (by default should be http://localhost:1841/)
Related
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.
I'm new to Sencha and so for Sencha Test. On my Windows 10 machine I installed the latest Sencha Studio and imported a sample project for ours. Following tutorials I created a test suite with the sample "it should pass 1 = 1" test. But I cannot run this test, neither via IDE nor CLI.
On the scenario I selected my local Chrome browser and the sample test. When I click on RUN, the browser selection on the right gets updated with gray bullets or void but nothing else happens. Changing the scenario's test type to "Webdriver" or "In-browser" does not change anything in regard for the outcome.
I also tried to execute the test via CLI but no success either. I always end up with this message: "Sencha Test v2.0.2Error: Sencha Cmd install directory not found : C:\Users[MY_PROFILE]\bin\Sencha\Cmd." That's right, my Sencha Cmd installation is located in C:\dev\Sencha\Cmd and works properly. Where's the configuration to change that stc can find Sencha Cmd?
Any hints how to get the tests run? Is an archive server mandatory to run the tests? Is there anything that I might have missed? Using Google was no help so far.
Maybe that's helpful: The Event Recorder does also not work properly. When I click on recording, my Chrome does not get opened, I have to open it by myself and navigate to the URL provided by Sencha Studio. Weird.
Thanks in advance.
After several hours of thinking and searching I think the most critical error was to NOT install Sencha Cmd and Sencha Test into the installer's recommended folder. I still have issues when starting tests but I'll post an answer if there's anything interesting about this topic.
Also, it seems that Sencha Test always expects that a built project exists. So just checking out the sources without building them is not sufficient to run tests, even if you're testing e.g. the staging.
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.
Hi I want to learn Sencha. I have basic knowledge of MVC. I have downloaded sencha Touch and Sencha cmd. I have extracted sencha Touch folder to my local. And I have installed Sencha cmd. But Sencha cmd is not working. When I click on cmd it automatically disappeared. What can I do now. I have installed Sencha SDK Tool.
Any one please help me out.
There is a series of videos on how to prepare your computer for development here: http://extjs.eu/videos
After installing Sencha cmd in windows you need to set Environment variables.
Open start menu
Click on computer > Right click Properties.
In properties > click on Advance setting.
In Advance setting click on environment variable.
Here you select path and click on edit and add the path of the sench cmd.
Go back to cmd and run sencha.
Here you will get all the sencha details. if you get means sencha is installed properly.
At first you have to download the cmd(Which you have done). Then do the followings:
It is a zip file. Extract it.
Then you will get a .run file(If using ubuntu) or .exe file(In Windows).
Double click this file and install it. (For Ubuntu, first you have to change permission of this file to 777 using chmod 777 .run/file/path and then double click).
Now you can run sencha in terminal and check whether it has successfully been installed or not.
Goto command promt and type sencha . if your sencha cmd is installed properly ,you will see data on your promt. if it says that sencha command not found,try reinstalling sencha cmd
there is no need to open sencha cmd and sdk if you have correctly installed sencha cmd then go to command promt and type sencha if it's show version and other help command then it's properly installed.
then go to your sdk path and create app by sencha generate app app_name folder_name or path where you want to create your application.
A real case: Sencha v6.5.3.6 on Windows 10 professional x64. From CMD, you run
C:\Users\computer_user_name\bin\Sencha\Cmd\sencha
I must point out full path of sencha.exe for running.
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