FWD » Core Development » User Interface

Please add to this list whenever you find something that is a permanent restriction.

1. The font rendering will be close but will not be a pixel-for-pixel duplicate of the Windows font rendering. To resolve this we would have to implement our own font rendering engine that duplicated the Windows font rendering engine. This is not planned at this time and it is believed it is not needed so long as our rendering is close enough that users cannot tell the difference during use.

2. The default icon is a GCD logo instead of the OpenEdge logo. We don't want to duplicate their logo because it would confuse the user into thinking this is OpenEdge code. That would violate trademark law and copying the logo would violate copyright law.

3. There is no OpenEdge splash screen. We could make our own but there doesn't seem to be a functional reason to do so.

4. The cursors being used don't exactly match the sets used in Windows. This could be resolved, but again there is little reason to do so.

5. Menus (fixed and popup), combo-box drop-downs and any other windows that can display outside of the strict boundary of the 4GL application windows, will only display within the browser. The page in the browser will be a kind of virtual desktop which can be scrolled so that any such content can be seen.

6. Clipboard limitations (expand the details here when the final development is done).

7. Some browsers capture certain accelerator keys for browser functions. Those key combinations cannot be used for application purposes.

1. PrtScr/SysRq print screen key
2. Alt + F4 opens close window warning dialog
3. Ctrl + Shift + PAGE UP move tab in focus left but generates Progress 4GL code - 3067 correctly
4. Ctrl + Shift + PAGE DOWN move tab in focus right but generates Progress 4GL code - 3068 correctly
5. Alt opens the browser's menu but generates Progress 4GL code - 1024 correctly
6. Alt + F opens File menu
7. Alt + S opens History menu
8. Alt + V opens View menu
9. Alt + B opens Bookmarks menu
10. Alt + T opens Tools menu
11. Alt + H opens Help menu

1. PrtScr/SysRq print screen key
2. Alt + F4 close the window without warning dialog
3. Ctrl + W close the current page without warning dialog
4. Ctrl + T opens a new tab
5. Ctrl + N opens a new window
6. Ctrl + Shift + N opens a new window in incognito mode

1. PrtScr/SysRq print screen
2. Alt + F4 close the window without warning dialog
3. Alt + Home go to a home page
4. Alt opens the browser's menu but generates Progress 4GL code - 1024 correctly
5. Alt + F opens File menu
6. Alt + E opens Edit menu
7. Alt + V opens View menu
8. Alt + A opens Favorites menu
9. Alt + T opens Tools menu
10. Alt + H opens Help menu
11. F1 opens Microsoft Help & Support page but generates Progress 4GL code - 301 correctly
12. Alt + D focuses and selects the url in the address bar.
13. Ctrl+ O opens New Document Address Dialog
14. Alt + Z opens Add To Favorites menu but if repeat Alt+Z generates Progress 4GL code - 1114 correctly
15. Alt + C opens View favorites but generates Progress 4GL code - 1091 correctly

These results have been checked manually with test.html, keystrokes.js, keyboard_testcases.js from testcases/uast/keyboard/web and the current version p2j.keymap.js and p2j.keyboard.js from 1811t by pressing the functional shortcuts in the input field.

Firefox doesn't generate key events for some simultaneously pressed keys if the left and right control are hold. For example,
CTRL + CTRL + Z, CTRL + CTRL + X, CTRL + CTRL + C, CTRL + CTRL + V, CTRL + CTRL + Enter, CTRL + CTRL + Delete, CTRL + CTRL + Insert, CTRL + CTRL + Home, CTRL + CTRL + Page Up, CTRL + CTRL + Num Lock

keydown  keyCode=17        which=17        charCode=0        
         shiftKey=false ctrlKey=false altKey=false metaKey=false
         key=Control char=undefined location=1 repeat=false
keydown  keyCode=17        which=17        charCode=0        
         shiftKey=false ctrlKey=true  altKey=false metaKey=false
         key=Control char=undefined location=2 repeat=false
keyup    keyCode=17        which=17        charCode=0        
         shiftKey=false ctrlKey=true  altKey=false metaKey=false
         key=Control char=undefined location=1 repeat=false
keyup    keyCode=17        which=17        charCode=0        
         shiftKey=false ctrlKey=true  altKey=false metaKey=false
         key=Control char=undefined location=2 repeat=false   

keydown  keyCode=17        which=17        charCode=0        
         shiftKey=false ctrlKey=false altKey=false metaKey=false
         key=Control char=undefined location=1 repeat=false
keydown  keyCode=17        which=17        charCode=0        
         shiftKey=false ctrlKey=true  altKey=false metaKey=false
         key=Control char=undefined location=2 repeat=false
keydown  keyCode=34  (")   which=34  (")   charCode=0        
         shiftKey=false ctrlKey=true  altKey=false metaKey=false
         key=PageDown char=undefined location=0 repeat=false

The current implementation of the GUI web client redirects to the login page if a user executes the reload/refresh command. It has been done intentionally and the reload/refresh default action can be restored as soon as the application state API is ready.
To reload the application page it needs to focus the address bar and press F5 or equivalent key strokes. The warning dialog appears before the page has been reloaded. If a user confirms to leave the current page, then the web page is reloaded, the new web socket connection is opened and then the web page is redirected to the login page and the web socket server peer gets the QUIT command. On receiving QUIT it terminates the own worker process to give a user to create new session with P2j server via the web access.