Testing and Deploying: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
The easiest way to test your app is in your desktop browser. Use “Start in Desktop Browser” under the File menu. It will run in your default browser, which should support WebKit. At this time, Chrome and Safari support WebKit. | The easiest way to test your app is in your desktop browser. Use “Start in Desktop Browser” under the File menu. It will run in your default browser, which should support WebKit. At this time, Chrome and Safari support WebKit. | ||
You can debug your program using the desktop browser. For more information, see | You can debug your program using the desktop browser. For more information, see “[[Using the Chrome Debugger]]”. | ||
Once your program runs well in the desktop browser, you can deploy it to a server. Devices can then load your program from that server. | Once your program runs well in the desktop browser, you can deploy it to a server. Devices can then load your program from that server. | ||
| Line 8: | Line 8: | ||
'''Deploying''' | '''Deploying''' | ||
App Studio provides a server for testing apps, called the | App Studio provides a server for testing apps, called the nsbapp.com. When you choose Deploy from the menu, your program and any files listed on the manifest are copied to the server. When the upload is complete, the IDE will give you the URL to open the app from. | ||
The first time the app is run on the device, the files on the manifest are copied to the device. Your app can then be run locally, without an internet connection. | The first time the app is run on the device, the files on the manifest are copied to the device. Your app can then be run locally, without an internet connection. | ||
If you change your program and upload it again, there is a pause while the files are moved into place on | If you change your program and upload it again, there is a pause while the files are moved into place on nsbapp.com. | ||
The next time you run the program (or refresh), the device runs its current version from memory while it gets the latest manifest from the server. It compares them: if the manifest has changed, it then downloads the whole application again and saves it to the device. Once this is complete, the new version of the app will run next time you do a refresh. | The next time you run the program (or refresh), the device runs its current version from memory while it gets the latest manifest from the server. It compares them: if the manifest has changed, it then downloads the whole application again and saves it to the device. Once this is complete, the new version of the app will run next time you do a refresh. | ||
For more information, see [[Distributing_your_App|Tech Note 05, “Distributing your App”]]. | For more information, see [[Distributing_your_App|Tech Note 05, “Distributing your App”]]. | ||
Revision as of 10:06, 3 December 2012
The easiest way to test your app is in your desktop browser. Use “Start in Desktop Browser” under the File menu. It will run in your default browser, which should support WebKit. At this time, Chrome and Safari support WebKit.
You can debug your program using the desktop browser. For more information, see “Using the Chrome Debugger”.
Once your program runs well in the desktop browser, you can deploy it to a server. Devices can then load your program from that server.
Deploying
App Studio provides a server for testing apps, called the nsbapp.com. When you choose Deploy from the menu, your program and any files listed on the manifest are copied to the server. When the upload is complete, the IDE will give you the URL to open the app from.
The first time the app is run on the device, the files on the manifest are copied to the device. Your app can then be run locally, without an internet connection.
If you change your program and upload it again, there is a pause while the files are moved into place on nsbapp.com.
The next time you run the program (or refresh), the device runs its current version from memory while it gets the latest manifest from the server. It compares them: if the manifest has changed, it then downloads the whole application again and saves it to the device. Once this is complete, the new version of the app will run next time you do a refresh.
For more information, see Tech Note 05, “Distributing your App”.