Existing 4GL Forms and Source Code

Transcription

1 Migrating from TUI to GUI 1

2 Existing 4GL Forms and Source Code Compiling programs fgldbsch created a required schema file (.sch) fglform compiles existing.per files fglcomp compiles existing.4gl files fgllink links parts together in a.42r (program) or.42x (library) In Genero Studio: Configure, Import, Build and Execute Executing programs FGLGUI environment variable manages TUI or GUI mode FGLPROFILE file manages runtime configuration Genero Desktop Client (GDC) renders app on client IIUG Migration Tutorial 2

3 TUI vs. GUI FGLGUI=0 GU IIUG Migration Tutorial 3

4 TUI vs. GUI FGLGUI=1 IIUG Migration Tutorial 4

5 Rendered UI in GUI mode window form menu messages /errors IIUG Migration Tutorial 5

6 TUI vs. GUI: Traditional Mode FGLGUI=1 gui.mode = traditional IIUG Migration Tutorial 6

7 How do we go from here to there? IIUG Migration Tutorial 7

8 From TUI to GUI Windows and Forms 1. Screen Layout 2. Screen Arrays Tables 3. Containers and Widgets 4. DISPLAY AT OPEN WINDOW with FORM 5. SCREEN window 6. Presenting Actions: ToolBars, TopMenus, Menus, Buttons 7. TTY attributes Presentation styles IIUG Migration Tutorial 8

9 SCREEN LAYOUT Difference in form design LAYOUT replaces SCREEN providing access to new containers and widgets IIUG Migration Tutorial 9

10 Untouched.per file opened in Genero Studio.

11 Modified.per file Using LAYOUT and containers and new widgets.

12 Modified per file Modified.per file Using LAYOUT and containers and new widgets.

13 Rendered form that is defined with table and group containers and widgets like dateedit.

14 .per files can be directly imported into Studio s Form Designer to help visually design form.

15 LAYOUT Containers Layout containers include GRID, SCROLLGRID, TABLE, FOLDER, and GROUPBOX IIUG Migration Tutorial 15

16 The form structure shows how the containers are nested.

17 LAYOUT Widgets Many widgets to choose from and easy to create in Form Designer. IIUG Migration Tutorial 17

18 Same screen capture of form structure this time showing listing of widgets The form structure also shows the layout of the widgets within each container.

19 Attributes For example, the textedit widget can have the following attributes defined: textedit Attributes COLOR COLOR WHERE COMMENT DEFAULT DOWNSHIFT FONTPITCH HIDDEN INCLUDE KEY NOT NULL NOENTRY PROGRAM REQUIRED SCROLLBARS SIZEPOLICY STYLE STRETCH TAG TABINDEX UPSHIFT WANTTABS WANTNORETURNS IIUG Migration Tutorial 19

20 Attributes All Genero objects have attributes. Form Designer makes it easy to see an object s attributes and values. IIUG Migration Tutorial 20

21 Screen Arrays Tables Changing the container to a table, provides a better layout mechanism than the screen array default. No.4gl 4lsource needs to bechanged. Table container attributes can be used to control table container features. IIUG Migration Tutorial 21

22 Table containers can house screen arrays. Here the data has been sorted by Company by the user and columns shown can be checked on and off.

23 DISPLAY AT OPEN WINDOW with FORM Windows are dynamic objects that adapt to thesize of theform. No more X, Y positioning. Positioning is relative lti toobjects t on form. Positioning can be preserved locally with the GDC local settings. Window settings can be managed with styles. IIUG Migration Tutorial 23

24 SCREEN Window Main root default window is SCREEN. Ensures forms have a place to display. However, recommend changing to OPEN WINDOW WITH FORM The default SCREEN window can be used or closed. If app starts with OPEN WINDOW with FORM, CLOSE WINDOW SCREEN If code has a lot of DISPLAY FORM statements, you can use SCREEN window or modify to OPEN WINDOW with FORM (recommended) IIUG Migration Tutorial 24

25 COMMAND > ACTION Menus and dialogs now can be made up of ON ACTION statements. Named ACTION can be presented on window and form in a variety of ways. IIUG Migration Tutorial 25

26 COMMAND > ACTION Menus and dialogs now can be made up of ON ACTION statements. Named ACTION can be presented on window and form in a variety of ways. IIUG Migration Tutorial 26

27 Presenting Actions Commands to Actions Presenting Actions: Default right Menu/Action Panel ToolBars TopMenus Widgets lk like Button" IIUG Migration Tutorial 27

28 Here, actions are presented in both a topmenu and toolbar.

29 When the ON ACTION is present in the dialog, the corresponding presentations on screen are enabled.

30 This form uses an ACTION DEFAULTS section to set up the presentation attributes of the actions.

31 Presentation attributes of actions can also be specified globally in a.4ad file.

32 In this.4ad file, the accept and cancel actions are tied to the 4gl Escape and Control-C accelerators to preserve user system familiarity.

33 TTY Attributes Presentation Styles Fields with styles applied. These tables have different styles applied. Presentation styles can now control the changing look and feel of objects such as Window type, fonts, colors, and conditional settings like focus and odd/even table rows. IIUG Migration Tutorial 33

34 The style attribute for objects specifies the style to use. This.per file is setting a style on both the Table container and the Label widgets.

35 Presentation Styles Defined in.4st The styles we saw applied are defined in a.4st file. Styles can apply to: All objects Specific objects Conditionally IIUG Migration Tutorial 35

36 Summary Screen Layout Screen Arrays Tables Containers and Widgets DISPLAY AT OPEN WINDOW with FORM SCREEN window Presenting Actions: ToolBars, TopMenus, Menus, Buttons TTY attributes Presentation styles IIUG Migration Tutorial 36

37 Questions?