User Tools

Site Tools


APPLICATION

Guide Section: GUI of an EASAP | EASAP Tree: Properties Branch


APPLICATION sets the basic properties of the EASAP.

APPLICATION is a singleton object so there is only be one APPLICATION object on an EASAP Tree. The table below contains descriptions of the various parameters for the APPLICATION.

Allowed Clients:

By default, all EASAPs are configured to open only in the Web Browser client. To override this default, you need to set the Allowed Clients: parameter to include EASA Client as part of its value. There are three possible settings for the Allowed Clients: parameter:

  • EASA Client only
  • Web Browser only
  • EASA Client and Web Browser both allowed

When both EASA Client and Web Browser are set to be allowed in the Allowed Clients: parameter, then users will determine which one to use by their Client Preference setting on the Preferences page.


Tip: If you select 'Web Browser' within the Allowed Clients: parameter, it is recommended that you set the ‘Display compatible for’ setting under the Options tab in EASAP Builder to ‘Web Browser’.


Download Only:

EASAPs By setting the Download Only: parameter to YES, you effectively transform your EASAP into a file storage and retrieval tool. These 'file download' EASAPs can be useful for storing such files as:

  • Documents, e.g. design guides or product literature
  • Results from experiments or analysis performed outside of EASA If you do set the Download Only: parameter to YES, all you need to do to complete the EASAP is the following two tasks:
  • Create the appropriate CATEGORY and
  • Using the Files tab, create a folder called ‘download’, and then upload the files to be available for downloading into this folder.

You need not do anything to the remaining three branches, USER INTERFACE, PROCESSES and OUPUT. Once you have completed the two steps described above, you can save your EASAP and then proceed to test, document and publish it. Once published, the EASAP will be presented like any other in the Application library. However, when a user opens it, they will NOT get a user interface of an application, instead they will see either:

  • A file opened in its associated application, if the download folder meets one of the following criteria:
    • contains only one file
    • contains an html file, which will be opened in a browser window and a directory starting with the same name as the html name, for example demo.htm and demo_files
    • contains a file called app.htm or app.html, which will be opened in a browser window
  • A file selection window as shown below, when two or more files has been uploaded into the EASAP.

APPLICATION
Essential Parameters:
Title:Title of EASAP
Author Name:Author's name
Status:EASAP status (default→Development, Pre-Release, Release)
Optional Parameters:
Width:Default EASAP window width in number of pixels
Height:Default EASAP window height in number of pixels
Selection Image:Image file name (.gif/.jpg/.png) used on EASA→Applications selection page. Image size automatically scaled to fit properly in 'Gallery' and 'Table' views.
Author Email:Author's e-mail address
Icon:Image file name (.gif/.jpg/.png) used as icon on upper-left corner of some windows
Password:Password for adding security to editing of EASAP
Max. Parametric Runs:Maximum number of runs a PARAMETRIC RANGE can generate at one time.
Application Information:File name used as linked document in 'Information' column on EASA→Applications page in User mode
Short Description:Short description of EASAP displayed in 'Table' view page at EASA→Applications
Download Only:Set EASAP to be a file Download Only: EASAP (default→NO, YES)
Allowed Clients:Select which Allowed Clients: types are allowed to open the EASAP (default→EASA Client, Web Browser)
Startup DORs:Comma separated list of objects whose values will be set using special URL syntax from 3rd party application (see the Links for Opening EASAPs and Viewing Results)