-
Notifications
You must be signed in to change notification settings - Fork 14
grwl edited this page May 10, 2012
·
3 revisions
GUI will consists of the following tabs:
- a bunch of controls to input address, port, test name, debugging mode, etc.
- 'start' button
- some check boxes and input fields
- 'load ...' buttons: show file selector dialog, pass selected file name to the core
- 'load ...', 'export ...' buttons: show file selector dialog, pass selected file name to the core
- 'generate' button: just call the core
- one more checkbox and lineinput field not shown on the screen prototypes, labeled 'server'
- a list available protocols, a list of selected protocols, buttons 'select all', 'deselect all'
- similarly, lists of ciphers, available and selected ones
- progress bar
- 'stop' button
- table which will contain test results
- the list which will contain log entries
- rich text editor, filled with data supplied by the core
- possibly a few checkboxes/radiobuttons to control report generation
- a button to copy the document to clipboard
When 'start' button is pressed, pressed GUI has to
- pass all options in bulk to the core
- handle possible exceptions
- disable all input element editing (grey out)
- switch to 'test log' tab
When the test finishes, the GUI has to
- call a method of the core to generate report (HTML), and switch to 'report' tab
- reactivate 'start' button and input elements to allow editing
- code must be clean
- GUI design has to look nice on different OSes, i.e. fonts, spacing between elements, alignment must remain correct.
- the same applies to resizing of the application window
- there should be about dialog box and a button to invoke it