Difference: AppxHTMLClient (7 vs. 8)

Revision 82014-12-12 - JeanNeron

Line: 1 to 1
 

APPX HTML Client

This page gives an overview of and installation instructions for the Appx HTML client.

Line: 20 to 20
 Once the HTML client is working, you can connect to any Appx 5.4+ server, just as you can with the Appx Desktop Client. Due to the engine changes that were made in 5.4 to support the HTML client, you cannot connect to an earlier Appx engine.

LocalConnector

Changed:
<
<		Because of the tighter security in web browsers, it is not possible for HTML 5/javascript to seamlessly upload, download or open files on the users desktop the way it can be done with the Appx Desktop Client. To address this, the HTML client includes a small 'helper' program that supports this. By default, the HTML client will check to see if this helper program is installed when the user logs in. If it is not installed, it will offer to install it, and if the user cancels they will be nagged the next time they log in.
>
>		Because of the tighter security in web browsers, it is not possible for HTML 5/javascript to seamlessly upload, download or open files on the users desktop the way it can be done with the Appx Desktop Client. To address this, the HTML client includes a small 'helper' program that supports this. This is called the 'LocalConnector'. By default, the HTML client will check to see if the local connector program is running when the user logs in. If it is not running, it will offer to install it, and if the user cancels they will be nagged the next time they log in.
  If your application does not require the ability to upload/download/open files on the desktop, you can turn this off (see Installation below).
Changed:
<
<		There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the LocalConnector is installed & runnning. Red means the connector is not installed. The 'Remote' connector refers to the connection to the Appx Server Connector. This must be green with a "+" for any connection to work.
>
>		There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the l ocal connector is installed & runnning. Red means the connector is not installed. The 'Remote' connector refers to the connection to the Appx Server Connector. This must be green with a "+" for any connection to work.
 

Differences between ADC and HTML Clients

The HTML client has a different presentation for most non-Appx elements such as Date Choosers, File Upload/download dialog boxes, Tables, etc. The goal of the HTML client was to replicate the presentation of your screens as accurately as possible as far as the Appx elements are concerned (i.e., the widgets and fields you use in the Image Editor). Since we use different 3rd party tools and runtimes for other elements, they will look different compared to the Appx Desktop Client.

Line: 34 to 34
  The web server does not have to be on the same server as Appx.
Added:
>
>		If you plan to use an SSL connection, your web server must be configured to accept both SSL and non-SSL connecions.
 We have tested the HTML client on current versions of IE, Chrome and Safari.

Installation

Line: 49 to 51
  Note that this will appear to 'hang', but it is actually running and waiting for connections. Just minimize the DOS box and leave it running.
Changed:
<
<		At some point we will automate this step, but for now you must manually start the connector upon first installation and after every reboot.
>
>		We will automate this step, but for now you must manually start the connector upon first installation and after every reboot.
  Finally, you need to set the name of the host running the Appx Server Connector in the 'client.html' web page:
Line: 64 to 66
 You must open port 3014 on your web server for this connection to work. If you do not want to open any new ports on your web server, see the next section 'Tunneling/Forwarding'.

LocalConnector

Changed:
<
<		As mentioned above, you can suppress the requirement for the LocalConnector by changing the following line in /var/www/html/appx/client.html:
>
>		As mentioned above, you can suppress the requirement for the LocalConnector by changing the following line in "client.html":
  <meta name="appx-local-required" content="true" >

Change the "true" to "false" to supress the requirement.

Added:
>
>

LocalConnector Installation

If you do not turn off the LocalConnector requirement as above, then when the 'client.html' page is loaded it will check to see if the local connector is running on the users desktop. If not, they will get a dialog box offering to download the local connector. The actual installation of the local connector varies by the O/S on the user's desktop:

  • Windows: Once the download is complete, run the installer. The local connector will be installed, started and Windows will be configured to automatically start on a reboot. No further action is required.
  • Mac O/S: Once the download is complete, open the disk image and double click the installer. The local connector will be installed and started. The local connector will have to manually started after each login by opening a terminal window and entering the command "cd AppxLocalConnector;open node-webkit.app". Alternatively, the user can add 'node-webkit.app' in their AppxLocalConnector folder to their Login Items in System Preferences.
  • Linux: Once the download is complete, open a terminal window and enter:
    • cd Downloads (or wherever the file was saved to)
    • sh localConnector_linux32.sh or sh localConnector_linux64.sh, depending on whether you have 32 or 64 bit Linux. The connector will be installed.
    • Start the connector running by:
      • cd $HOME/AppxLocalConnector
      • sh ./start-nw.sh
    • The user has to manually start the local connector every time they log in, or they can add the script to their programs that start automatically when the log in. The steps vary by Linux distribution, consult your documentation.
 

Tunneling/Forwarding

If you do not want to open port 3014 and would rather use port 80, you can use forwarding instead. For example, to configure Apache 2.4 you would do the following:

View topic | History: r18 < r17 < r16 < r15 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback