310 likes | 333 Views
Explore different strategies for migrating from character mode to GUI, including auto-GUI, dual processes, and designing new GUI applications. Understand the advantages and disadvantages of each approach and learn how to implement them effectively.
E N D
Conference - 2002 Migrating to GUI
How do you get there from here? Migrating to GUI
Before you begin... you must decide if character mode is an ongoing requirement or if it can be abandoned after migrating to GUI. Migrating to GUI
Four Strategies • Character mode Auto-GUI • Single Application - Duplicate Processes • Dual Applications • Single Application - Dual mode processes (coming in 4.2) Migrating to GUI
Character Mode Auto-GUI • Advantages: • Easiest • Most applications run “without change” • Applications can be easily “tweaked” for best possible auto-GUI effect • Fastest - Up and running immediately • Looks better than character mode • Can be starting point for full GUI • Disadvantages: • GUI is limited to “basic” presentation Migrating to GUI
Character Mode Auto-GUI • Buttons on menu and input images • Title Bar with 3 buttons • Pull-down menus • System (Direct Process 1) • Application (Direct Process 2) • Process (Current Process) • Check boxes for Logic fields • Horizontal scrolling within field • Scrolling text fields Migrating to GUI
Character Mode Auto-GUI • Scan indicators (Binoculars) • PCF scan • DLU scan • SCAN statement (ILF) • List box for token fields • List box for alpha table fields • Scrolling screens • Boxes around column headings • Separator lines between fields and records • Scroll bar APPX Release 4.1
Title Bar • Buttons • Process Pull-down
Column heading boxes & blue text • Horizontal lines between records • Vertical lines between fields • Box around selected record • Scroll bar • Scan indicator
Check box for Logic fields • Separator under column heading • List box for Token fields • SCAN indicators
Single Application - Dual Processes • No new applications or databases • Two sets of menus • Different startup process (menu) depending on user ID or Client type • Two sets of input processes • Use design transfer to make a copy of each menu and input process • GUI-ize one copy of each menu and input process Migrating to GUI
Dual Applications - Different Versions • Two versions of each application • For example: • TAR CH (character mode applications) • TAR GC (GUI mode applications) • Shared data files • Two databases • One “uses” the other’s data files • Different startup database depending on user ID or Client type Migrating to GUI
Design New GUI Applications • Create a copy of the applications • Give them a different version code • Reengineer each menu process • Reengineer each input image • Reports and Inquiries do not require any changes Migrating to GUI
Design New GUI Applications • Reengineer each menu process • Image • Define named resources for wallpaper, logos, icons, etc. • Replace top row with title bar • Replace “option” text with buttons • Add boxes around groups of buttons • Define tab order for buttons • Replace “other” text with GUI labels • Add wallpaper or background color • Add logo graphic Migrating to GUI
Design New GUI Applications • Reengineer each menu process • Navigation aids for each menu item (Optional child process) • Define named resources for icons • Add Pull-down menus • Add Toolbar buttons • Add Right-click menu items Migrating to GUI
Design New GUI Applications • Reengineer each input process • Same as menu processes • Specify GUI attributes for data fields • Type of control and size • Text font, style, color, scaling • Border Style and color • Other • Add boxes around groups of fields • Define tab order for fields Migrating to GUI