Distributing your App - Revision history

Ghenne at 15:34, 25 February 2021

2021-02-25T15:34:28Z

← Older revision		Revision as of 15:34, 25 February 2021
Line 17:		Line 17:
	Your app needs to be deployed to a web server so that it can be loaded and run. There are several choices for web servers you can use.		Your app needs to be deployed to a web server so that it can be loaded and run. There are several choices for web servers you can use.

	=== ~~Volt~~ ===		=== VoltServer ===
	This is the default and will work without any extra setup. ~~Volt~~ can be used for testing and as a permanent location for your app, so long as you have a [[Subscriptions\|subscription]] in place. It also has a number of features which add to AppStudio's abilities. No PHP. If you are using the demo, you can only deploy to ~~Volt~~.		This is the default and will work without any extra setup. VoltServer can be used for testing and as a permanent location for your app, so long as you have a [[Subscriptions\|subscription]] in place. It also has a number of features which add to AppStudio's abilities. No PHP. If you are using the demo, you can only deploy to VoltServer.

	=== Local test server ===		=== Local test server ===

Ghenne at 14:28, 13 November 2020

2020-11-13T14:28:12Z

← Older revision		Revision as of 14:28, 13 November 2020
Line 8:		Line 8:
	# Have a registration code input field in your program. The correct code has to be entered the first time the program is run.		# Have a registration code input field in your program. The correct code has to be entered the first time the program is run.
	# Use a third party web app store. It will handle billing and downloads, and give you a percentage of the revenue. Samples of such stores are OpenAppMkt and the Chrome Web Store.		# Use a third party web app store. It will handle billing and downloads, and give you a percentage of the revenue. Samples of such stores are OpenAppMkt and the Chrome Web Store.
	# Make your app into a native app [[Submitting_to_the_iOS_App_Store\|using ~~PhoneGap~~ and submit it to Apple]]. There is an option on the Run menu for this.		# Make your app into a native app [[Submitting_to_the_iOS_App_Store\|using VoltBuilder and submit it to Apple]]. There is an option on the Run menu for this.

Ghenne: /* Setting up your server for manifest files (IIS) */

2020-11-02T19:14:29Z

Setting up your server for manifest files (IIS)

← Older revision		Revision as of 19:14, 2 November 2020
Line 171:		Line 171:

	On Android, it's a little more complicated. Up till Android 4, the browser was call Android Browser and used a similar process to add the the Home screen. In Android 4, the Mobile Chrome browser was introduced. On some devices, usually those branded as Google, only Mobile Chrome is available. Mobile Chrome is not complete: it is still missing some cosmetic features. See https://code.google.com/p/chromium/issues/list?can=2&q=OS:Android&sort=-stars&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20Area%20Feature%20Status%20Owner%20Summary%20Stars		On Android, it's a little more complicated. Up till Android 4, the browser was call Android Browser and used a similar process to add the the Home screen. In Android 4, the Mobile Chrome browser was introduced. On some devices, usually those branded as Google, only Mobile Chrome is available. Mobile Chrome is not complete: it is still missing some cosmetic features. See https://code.google.com/p/chromium/issues/list?can=2&q=OS:Android&sort=-stars&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20Area%20Feature%20Status%20Owner%20Summary%20Stars

	~~== Setting up your server for manifest files (IIS) ==~~

	If you are going to distribute your app from your own server, you will have to check if it is serving the OfflineApp.appcache file with the correct MIME type. To test what mime type a document is being returned as, use http://web-sniffer.net. Enter the url to your manifest file: for example, http://www.nsbapp.com/myProject/OfflineApp.appcache. The result will be displayed in "Content-Type": it should be 'text/cache-manifest'. If it is not, you'll need to change the setting in IIS. Here is where to look for it:

	~~[[File:TN05.01.png]]~~

	~~You will also need to add index.html to the list of names used by the default context page as follows, if it is not there already.~~

	~~[[File:TN05.02.png]]~~

	~~''with contributions from Tony O'Brian''~~

	~~Here are the contents of the working web.config file which resides in the website route directory on a Hostgator Windows server:~~
	~~<pre>~~
	~~<?xml version="1.0" encoding="UTF-8"?>~~
	~~<configuration>~~
	~~<system.webServer>~~
	~~<staticContent>~~
	~~<remove fileExtension=".appcache" />~~
	~~<mimeMap fileExtension=".appcache" mimeType="text/cache-manifest" />~~
	~~</staticContent>~~
	~~</system.webServer>~~
	~~</configuration>~~
	~~</pre>~~
	~~''Contributed by Graham Pettican''~~

	~~Update: You also need to add~~
	~~<mimeMap fileExtension=".woff2" mimeType="font/woff2" />~~
	~~<mimeMap fileExtension=".woff" mimeType="font/woff" />~~
	~~to mime types~~

	~~''Rodney Eales''~~

Ghenne: /* Setting up on a GoDaddy server */

2020-11-02T19:14:14Z

Setting up on a GoDaddy server

← Older revision		Revision as of 19:14, 2 November 2020
Line 204:		Line 204:

	''Rodney Eales''		''Rodney Eales''

	~~== Setting up on a GoDaddy server ==~~

	~~Here is how to edit the MIME types on Apache:~~
	~~http://support.godaddy.com/help/article/375/can-i-configure-mime-types-on-my-linux-hosting-account~~

	~~Here are the instructions for Windows hosting:~~
	~~http://support.godaddy.com/help/article/6286/modifying-or-adding-custom-mime-types-to-windows-hosting-accounts~~

	If your hosting is on a shared GoDaddy server runnimg Windows and IIS, it would seem that in order to set up your custom web.config file an upgrade to a virtual dedicated server is needed. Another, likely also less expensive approach, would be to switch to Linux hosting running Apache. Then you could create a .htaccess file to contain the following line:
	~~<pre>~~
	~~AddType text/cache-manifest .appcache .manifest~~
	~~</pre>~~
	~~Place this in the root of your site (in which case it affects the entire site) or in a directory where you will keep your apps (and in which case only that one directory will be affected)~~

	~~''with contributions from Johann Vogel''~~

Ghenne: /* Setting up your server for manifest files (Apache) */

2020-11-02T19:13:36Z

Setting up your server for manifest files (Apache)

← Older revision		Revision as of 19:13, 2 November 2020
Line 171:		Line 171:

	On Android, it's a little more complicated. Up till Android 4, the browser was call Android Browser and used a similar process to add the the Home screen. In Android 4, the Mobile Chrome browser was introduced. On some devices, usually those branded as Google, only Mobile Chrome is available. Mobile Chrome is not complete: it is still missing some cosmetic features. See https://code.google.com/p/chromium/issues/list?can=2&q=OS:Android&sort=-stars&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20Area%20Feature%20Status%20Owner%20Summary%20Stars		On Android, it's a little more complicated. Up till Android 4, the browser was call Android Browser and used a similar process to add the the Home screen. In Android 4, the Mobile Chrome browser was introduced. On some devices, usually those branded as Google, only Mobile Chrome is available. Mobile Chrome is not complete: it is still missing some cosmetic features. See https://code.google.com/p/chromium/issues/list?can=2&q=OS:Android&sort=-stars&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20Area%20Feature%20Status%20Owner%20Summary%20Stars

	~~== Setting up your server for manifest files (Apache) ==~~

	If you are going to distribute your app from your own server, you will have to check if it is serving the OfflineApp.appcache (or .manifest) file with the correct MIME type. To test whether your server has the correct settings, use Check Deployment in the Run menu.

	~~=== Modify mime.types ===~~

	~~The first method to correct the MIME type is to modify the mime.types file. Here is where you will find it:~~
	~~<pre>~~
	~~<IfModule mime_module>~~
	#
	~~# TypesConfig points to the file containing the list of mappings from~~
	~~# filename extension to MIME-type.~~
	#
	~~TypesConfig /private/etc/apache2/mime.types~~
	~~</pre>~~

	~~If your server is running Apache (most likely), you need to edit this file:~~
	~~<pre>~~
	~~/user/local/apache2/conf/mime.types~~
	~~</pre>~~
	~~Add this line to the end:~~
	~~<pre>~~
	~~text/cache-manifest appcache manifest~~
	~~</pre>~~
	~~You will need to restart Apache so the settings take effect. Could be something like~~
	~~<pre>~~
	~~restart_apache~~
	~~</pre>~~
	~~from the shell.~~

	What's happening here is that the server needs to return the cache file back to you with the proper content type set. If you don't do this, the file will probably come back as 'text'. If set properly, it will come back with a type of 'cache-manifest'.

	~~=== Use the .htaccess file ===~~

	If your webserver is hosted by an ISP you will may not be able to edit the "mime.types" file (server administrators are understandably reluctant to allow just anyone to modify their server's configuration!) If this is the case, you can usually provide a configuration file that will apply only to your personal server area. This file is named ".htaccess", and is sometimes used to control password access to portions of your website.

	In the root of your website directory, if it doesn't already exist create the .htaccess file and include the line "AddType text/cache-manifest .manifest" (omit the quotes). The .htaccess file will now specify the new manifest MIME type.

	~~Here's the minimum .htaccess file:~~
	~~<pre>~~
	~~AddType text/cache-manifest .appcache~~
	~~AddType text/cache-manifest .manifest~~
	~~</pre>~~
	~~The .htaccess file is used by Apache servers, and by some others as well. The Apache server may, as an option, ignore .htaccess files, so this technique may not work.~~

	~~For more information, see http://httpd.apache.org/docs/current/howto/htaccess.html and http://en.wikipedia.org/wiki/Htaccess .~~

	~~(with contributions from Paul Elliott)~~

	== Setting up your server for manifest files (IIS) ==		== Setting up your server for manifest files (IIS) ==

Ghenne: /* Including Images with your project made simple */

2020-11-02T19:12:41Z

Including Images with your project made simple

← Older revision		Revision as of 19:12, 2 November 2020
Line 138:		Line 138:

	# Put the images in your project folder. It's easiest to put them in a folder called images. Do not add them to the "nsb" folder, since that folder gets wiped out during compilation.		# Put the images in your project folder. It's easiest to put them in a folder called images. Do not add them to the "nsb" folder, since that folder gets wiped out during compilation.
	# In the ~~manifest~~ property, put 'images'. Then all the images in that folder will be deployed with your app.		# In the ''extraFiles'' property, put 'images'. Then all the images in that folder will be deployed with your app.
	# In your app, refer to the images by the simple pathname:		# In your app, refer to the images by the simple pathname:
	<pre>		<pre>

Ghenne: /* The Manifest File */

2020-11-02T19:12:03Z

The Manifest File

← Older revision		Revision as of 19:12, 2 November 2020
Line 144:		Line 144:
	</pre>		</pre>

	=== ~~The Manifest File~~ ===		=== extraFiles ===

	~~The Manifest file~~ is ~~a file~~ in ~~your project directory which~~ contains a list of all the files in your app~~. This file is created automatically by AppStudio~~. You can maintain its contents in the IDE: it is in the top level of the Project Explorer, in the property ~~Manifest. If you want your app to run in offline mode, you need to add the names of any images, folders or other files you app requires~~. These files must be located in the project's directory.		extraFiles is in Project Properties. It contains a list of all the files in your app. You can maintain its contents in the IDE: it is in the top level of the Project Explorer, in the property ''extraFiles''. These files must be located in the project's directory.

	~~Make sure your web server serves up .appcache files with the MIME type text/cache-manifest, or else this won't work. For more information on doing this, see "Setting up your server for manifest files"~~		Here is a sample ''extraFiles'':

	Here is a sample ~~manifest property~~:
	<pre>		<pre>
	mario.jpg		mario.jpg
	</pre>		</pre>
	~~The manifest property~~ should have a list of file names, one name per line. Folder names can also be included: they will automatically be expanded recursively. Subfolders are allowed.		''extraFiles'' should have a list of file names, one name per line. Folder names can also be included: they will automatically be expanded recursively. Subfolders are allowed.
	You can put most types of files that HTML can use into it. The app file, icons, background and splash screen are automatically included ~~in the application cache~~. You do not need to add them to ~~the manifest file~~. Remember add your image files!		You can put most types of files that HTML can use into it. The app file, icons, background and splash screen are automatically included. You do not need to add them to ''extraFiles''. Remember add your image files!

	To add an SQLite database, simply add its name to ~~the manifest~~. An SQLImport() function will be automatically be invoked when you start your app to load the database the first time. If you want to use some of the options of [[SqlImport]], use the same format as that function:		To add an SQLite database, simply add its name to ''extraFiles''. An SQLImport() function will be automatically be invoked when you start your app to load the database the first time. If you want to use some of the options of [[SqlImport]], use the same format as that function:
	<pre>		<pre>
	customers.db,DB,loadComplete,NSB.overwriteAlways		customers.db,DB,loadComplete,NSB.overwriteAlways
	</pre>		</pre>
	~~The manifest file can also be used to deliver updates to the files your app uses.~~

	When your app starts, it checks with the server (if available) and compares the manifest files to the one it last downloaded. If it has changed, an update is triggered. All the files in the new manifest are download and the application is restarted.

	~~You can force an update to your app at any time by executing the following statement:~~
	~~<pre>~~
	~~window.applicationCache.update()~~
	~~</pre>~~
	~~This is useful if a file you are reading from a remote site may have changed. In this case, the manifest file will not have been updated.~~

	=== Installing your App on a device ===		=== Installing your App on a device ===

Ghenne: /* Setting up your files */

2020-11-02T19:08:36Z

Setting up your files

← Older revision		Revision as of 19:08, 2 November 2020
Line 132:		Line 132:
	\|-		\|-
	\|databases		\|databases
	\|SQLite databases can be included with your app. Simply put the name of the database in ~~your manifest~~. AppStudio will take care of encoding the data and the schema and deploying it. When the app is loaded on the device, the database will be automatically reconstituted and will be usable right away.		\|SQLite databases can be included with your app. Simply put the name of the database in ''extraFiles'' in Project Properties. AppStudio will take care of encoding the data and the schema and deploying it. When the app is loaded on the device, the database will be automatically reconstituted and will be usable right away.
	\|}		\|}

Ghenne: /* Setting up your files */

2020-11-02T19:07:43Z

Setting up your files

← Older revision		Revision as of 19:07, 2 November 2020
Line 127:		Line 127:
	\| nsb/		\| nsb/
	\| Required. This directory contains all the files that AppStudio itself needs at runtime. Do not make any changes to the contents of this directory.		\| Required. This directory contains all the files that AppStudio itself needs at runtime. Do not make any changes to the contents of this directory.
	\|-
	~~\| OfflineApp.appcache~~
	\| This contains a list of files to be included. It is created automatically at deploy time with filenames the IDE knows about, plus any files listed in the project's manifest property. Older apps may use the suffix .manifest, but .appcache is recommended (and, in the case of DropBox, required.) See "The Manifest File".
	\|-		\|-
	\| images and js files		\| images and js files

Ghenne: /* AppStudio Server */

2017-04-18T14:53:44Z

AppStudio Server

← Older revision		Revision as of 14:53, 18 April 2017
Line 17:		Line 17:
	Your app needs to be deployed to a web server so that it can be loaded and run. There are several choices for web servers you can use.		Your app needs to be deployed to a web server so that it can be loaded and run. There are several choices for web servers you can use.

	=== ~~AppStudio Server~~ ===		=== Volt ===
	This is the default and will work without any extra setup. ~~It is intended~~ for testing ~~only: do not rely on the~~ app ~~being available there forever~~. No PHP. If you are using the demo, you can only deploy to ~~the test server~~.		This is the default and will work without any extra setup. Volt can be used for testing and as a permanent location for your app, so long as you have a [[Subscriptions\|subscription]] in place. It also has a number of features which add to AppStudio's abilities. No PHP. If you are using the demo, you can only deploy to Volt.

	=== Local test server ===		=== Local test server ===