Estimated completion time → 60 minutes.
In this session, we create a new EASAP, set a few properties, and add several data entry objects.
At the end of this session, the first two tabs of our EASAP will appear as below,
The first task is to create a new EASAP within EASA.
In the New Application Wizard, set a few properties in PROPERTIES→APPLICATION for our EASAP,
Both the image and the description will be visible to a group of Users once we Publish the EASAP.
Click OK and the Authoring tool, the EASAP Builder, will open (below).
There will be no coding involved.
Any necessary files required by an EASAP's underlying software are copied from the local Author's machine up to the EASA Server and stored in the development folder for the EASAP. This folder contains the single, centralized definition of the EASAP.
An authorized User will login to the EASA Server and will be redirected to an EASAP Server to interact with the the EASAP GUI once an Author has Published the EASAP.
The Save button is enabled only when there are unsaved changes. Upon saving the EASAP settings, the button will be disabled or grayed out until another change is made.
We are ready to add data entry objects to the user interface of the EASAP.
We add data entry objects to the USER INTERFACE of our EASAP. On this TABBED PANE we allow a User to choose a plate material and specify its dimensions.
Object names are case sensitive. In general, an Author should use lowercase names for objects, while capitalized or ALL CAPS are for built-in objects on the Tree as well as object types (ie. class names).
A User will be asked to enter input values in the units the Author specifies.
In this case we want to make the EASAP explictly aware of which units apply to each input.
To achieve this we use a DATA PROCESSING→SCALAR→COMPUTE.
As W, L and t represent lenghts, each will be automatically converted correctly when used in an expression, see USER INTERFACE→UNIT MANAGER→DEFAULT UNITS→DIMENSIONAL GROUP→Length
An EASAP internally uses values in metric units of kilograms, seconds, degrees Kelvin, meters and radians.
We extract material property data out of a file, material.txt
When a User changes the plate material each material property needs to change accordingly before use as input to the underlying software.
In order to help in the creation of the Extract, Find, and Repeat objects there is an Extract Tool available on the right click menu. The Extract Tool facilitates extracting a LIST of values from a column of data in a text file.
The following window appears,
From here we set up a repeating FIND to pull out the desired data and make them available in the EASAP as LIST's.
We add functionality so the User may select a plate material from the choices in matname.
An INPUTBOX with a Child DATA VALIDATION constrains the possible choices.
At some later time an Author might want to add another entry to material.txt, the EASAP would automatically show the new choice once the modified material.txt was uploaded into the EASAP, and the was EASAP saved and then Published.
We will use a MAP to retrieve the Modulus of Elasticity based on the choice of material from a User.
The SCALAR mat will be compared with each entry in the LIST matname; the index of the first match in matname will determine a corresponding element in Ein and then modulus will take on that value.
Create a similar MAP to retrieve a Poisson ratio for a given material .
We are ready to display the physical property values of the selected material. For aesthetic reasons we want to use INPUTBOX's to display the Modulus of Elasticity and Poisson Ratio once a User makes a choice of material.
We need to add an EVENT PROCESSING so showE and showMu will update when the User chooses a different material and the value of the INPUTBOX mat changes.
Let's check our work. At this point, the USER INTERFACE branch of the Tree should look like this,
After clicking on the Open Web Browser Test button (), the EASAP should look like this,
We should test the material selection functionality, select a different material and observe the property values change
On edges we add data entry objects to allow a User to specify the support conditions for each of the plate’s edges.
We create an error check to make sure a User does not submit a case in which the plate is not properly supported.
The edge_error_check→Show if: expression will be false if one of the four edges has been set equal to 2 ('Fixed'), or, when two edges have been set equal to 1 ('Pinned'); the expression is true otherwise and the Error Message: will be shown upon Submit.
At this point the USER INTERFACE branch of the EASAP Tree should look like this,
After clicking on the Open Web Browser Test button (), the second TABBED PANE should look like this,
If another EASAP exists with the name ‘Rectangular Plate’ a sequence number in parenthesis will be added to the title in order to keep the title unique.
Congratulations. We have completed Session 1. Let's continue with Session 2.