RAMP is shipped with a default set of styles and a jQueryTheme to make the screen appearance resemble a default VLF-ONE screen.
Here is the Customer Maintenance screen without the VLF-ONE styles:
For a new aXes project to adopt the VLF-ONE styles, tick the VLF-ONE RAMP Project check box and the styles will be automatically copied to the project folder. See the tutorial Step 2. Create the Project Container for the RAMP Tutorial .
To manually apply the VLF-ONE styles to an existing project, execute these commands in an IBM i command line:
CPY OBJ('<root>/ts/screens/.defaults/application_definition_vlfone.js') TOOBJ('<root>/ts/screens/<project folder>/application_definition.js') REPLACE(*YES)
CPY OBJ('<root>/ts/screens/.defaults/application_definition_vlfone.css') TOOBJ('<root>/ts/screens/<project folder>/application_definition.css') REPLACE(*YES)
CPY OBJ('<root>/ts/screens/.defaults/axautoguirules_VLFONE.json') TOOBJ('<root>/ts/screens/<project folder>/axautoguirules.json') REPLACE(*YES)
CPY OBJ('<root>/ts/ts2/css/projectThemes/jqtheme_VLFONE/') TODIR('<root>/ts/screens/<project folder>/projectThemes/') SUBTREE(*ALL) REPLACE(*YES)
CHGAUT OBJ('/axes/ts/screens/<project folder name>') USER(*PUBLIC) DTAAUT(*R) OBJAUT(*NONE) SUBTREE(*ALL)
Where:
Here the VLF-ONE styles have been applied to the screen:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RAMP Stage 2A: Rapidly Modernizing Complete Application Segments |
|
|
RAMP Stage 2B: Individually Modernizing Frequently Used Screens |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Install and Configure RAMP-TS / aXes-TS on your IBM i Server |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To Use RAMP You Need to Have aXes Installed and Running on Your IBM i |
|
|
|
|
|
|
|
|
|
|
Configure the Shipped VLF-ONE Demonstration System for Your Servers |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The most important and complex 5250 program in an application can become a modernization trap |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Step 9. Link Destination WRKSYSSTS with Command System Status |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Step 3. Modify CUS_MAINT Script: Listen to the Event and React |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RAMP-WIN001: Creating a Basic Prototype of the Modernized Application |
|
|
|
|
|
|
|
|
|
|
RAMP-WIN001 Step 4: Prototype End-User's Access to Employee Information |
|
|
|
|
|
|
|
|
RAMP-WIN002: Rapidly Modernizing Complete Application Segments |
|
|
|
|
|
|
|
|
RAMP-WIN002 Step 3: Classify the Screens and Track Navigation |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RAMP-WIN004 Step 4. Take Snapshots of Your Destination Screens |
|
|
|
|
|
|
RAMP-WIN005 Step 1. Place Snapshots on Mock Up Command Handlers |
|
|
|
|
|
|
|
|
RAMP-WIN006 Step 1. Snap a Basic Inquiry Screen into the Framework |
|
|
RAMP-WIN006 Step 2. Change the Script to Use the Current Instance List Entry |
|
|
|
|
|
|
|
|
RAMP-WIN007 Step 1. Snap a Basic Data Entry Screen into the Framework |
|
|
RAMP-WIN007 Step 2. Change the Script to Signal the New Employee Number |
|
|
|
|
RAMP-WIN007 Step 4. Change the Script to Update the Instance List |
|
|
|
|
|
|
|
|
RAMP-WIN008 Step 1. Create Two Variants of Display Employee Screen |
|
|
|
|
|
|
|
|
|
|
|
|
RAMP-WIN009 Step 1. Starting the Trace and Redisplaying the Destination Screen |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RAMP-WIN012 Step 1. Snapping in the DF_T3201 Command Handler |
|
|
|
|
|
|
|
|
|
|
RAMP-WIN013 Step 2. Snapping in and Testing the Command Handler |
|
|
|
|
|
|
|
|
RAMP-WIN014 Step 1. Assigning the Same Name to Two Screen Variations |
|
|
RAMP-WIN014 Step 2. Handling Different Screens with the Same Signature |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RAMP-WINAD01 Step 2. Name Fields to Be Copied on the DisplayEmployee Screen |
|
|
RAMP-WINAD01 Step 3. Add a Function to the Script for the DisplayEmployee Screen |
|
|
RAMP-WINAD01 Step 4. Call the Function in the ButtonClick Function |
|
|
|
|
|
|
|
|
RAMP-WINAD02 Step 1. Add a Signal Button to the By Name Filter |
|
|
RAMP-WINAD02 Step 2. Make Your 5250 Screen Listen to the Signal |
|
|
RAMP-WINAD02 Step 3. Test Signaling from Filter to RAMP Screen |
|
|
|
|
|
|
RAMP-WINAD02 Step 6. Signalling from a RAMP script to a VLF component |
|
|
|
|
|
|
RAMP-WINAD03 Step 1. Understand What Makes the Prompter Appear |
|
|
|
|
|
|
|
|
RAMP-WINAD03 Step 5. Generically Associating Date Fields with Date Picker |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RAMP-WINAD05 Step 1. Optional - Creating Your Own Copy of the Shared Scripts File |
|
|
RAMP-WINAD05 Step 2. Accessing SHARED properties and functions |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RAMP-WINAD06 Step 6. Review and Alter Buttons and Function Keys |
|
|
RAMP-WINAD06 Step 7. Review the value you have added to the 5250 application |
|
|
|
|
|
|
|
|
|
|
|
|
RAMP-WINAD07 Step 4. Enable Function Keys/Buttons and Add Required Scripting |
|
|
RAMP-WINAD07 Step 5. Defining the Exit Junctions and vHandle_NAVIGATETO scripting |
|
|
|
|
|
|
|
|
RAMP-WINAD08 Step 1. Name the Fields to Be Used in the Wrapper |
|
|
|
|
|
|
RAMP-WINAD08 Step 4. Test Updating the Screen from the Wrapper |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Replacing Hardcoded Employee Number with Current Instance List Entry |
|
|
|
|
|
|
Filter Code which Automatically Handles Changes to Instance List |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Locating a specific value in a Subfile and making the selection |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Generically Modifying a Screen via the Standard Layout function |
|
|
Specifically Modifying a Screen via a Specific Layout function |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When a Wrapper Wants to Request a RAMP Script to Do Something |
|
|
When a RAMP Script Wants to Request a Visual LANSA Wrapper to Do Something |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A RAMP Design Approach – Using a Single Junction Point (SJP) |
|
|
|
|
|
|
|
|
|
|
|
|
Using HIDE_CURRENT_FORM to manage access to command handler tabs |
|
|
|
|
|
|
|
|
Screen does not react when selection is changed in instance list |
|
|
Error running RAMP in end-user mode (UF_EXEC) but not in design mode (UF_DESGN) |
|
|
|
|
|
|
|
|
|
|
I have made a mistake in classifying a screen. How do I change the classification? |
|
|
How do I differentiate two screens which have the same name? |
|
|
|
|
How can I get the message from the bottom of the current 5250 screen into my RAMP script? |
|
|
|
|
Why should the F12=Cancel and F3=Exit buttons and function keys be disabled on every 5250 screen? |
|
|
Do I have to identify and script every 5250 screen in my application to modernize it? |
|
|
|
|
|
|
|
|
|
|
|