We create a new EASAP, upload some files, set some properties, add data entry objects and at the end of this session, our EASAP interface will appear as below.
1. Login to EASA as an Author.
Check with your Administrator that you have a user ID with Author privileges and then log on:
2. Create a new EASAP.
3. In the New Application Wizard set some PROPERTIES for the EASAP.
|This application performs a loading analysis on a cantilevered rectangular plate having a variable thickness and length and a fixed width of 1 ft. The displacement of the plate is predicted for a user defined uniformly distributed load|
Both the image and the description will be visible to a User once the EASAP is published.
When a file is uploaded to an EASAP, it is:
The development folder (ie. <SERVERDATA>\easa\applications\author\Easap1 ) contains the single, centralized definition of the EASAP.
Once an EASAP is published, copies of these files will be read or modified in a way controlled by the User running the EASAP.
In our case we need to upload some image artwork files:
The Save button is enabled only when there are unsaved changes. After a Save, the button will be disabled or grayed out until another change is made.
We now add data entry objects to the user interface of our EASAP.
1. Change the text on tabbed_pane1.
2. Let's check our work with a test.
3. We allow the User to choose the type of material for the cantilevered plate via a CHOICE LIST.
5. We specify default units for our REALBOX so a User may switch to another unit system.
The parameter table for the REALBOX L will appear as follows
6. The User will choose the thickness of the plate via another REALBOX.
8. Let's check our work in the EASAP Builder and test the EASAP.
At this point, the Tree should look like:
9. Let's see the current name and status of our EASAP from the EASA Server.
A new integer is added to an EASAP title, or an existing integer is incremented, in order to keep each EASAP title unique.
We have finished Session 1, let's continue with Session 2.