This is a simple project that uses Code::Blocks, C++, mingw (32 bit), wxWidgets (32 bit) libraries to produce a UI application that does pretty much nothing. It is a skeleton project. BOOST may be used if required.
We know this project can be done easily in using MS based solutions. But this project strictly requires the above technologies.
As part of undertaking the project you would need to suggest what “Resource Editor” you suggest to use for modifying the RC files used for this project. We prefer a free Resource Editor however am open to recommendations.
Program needs to work for all versions of Windows.
The focus of the project is purely to provide the project file, RC files to have a basic starting point for the project to be completed by others. The tasks illustrated are merely request to get the project started.
1. Basic UI look
Refer to the attachment “[url removed, login to view]” which shows a standard Windows broken into two regions. The “HTML Region 1” is just an HTML control for the banner and the “HTML Region 2” is just an HTML viewport based on what is selected in the banner.
The Basic UI look must have:
a. Icon and title as “myUI – ABC”
b. The banner as illustrated.
c. When you click on the Icon in the banner, it will raise a message box that says: “Banner Icon clicked”
d. When you click on the text area containing “myUI – ABC hello world!”, it will raise a massage box that says: “Banner Text clicked”
e. The toolbar button has the active button highlighted in “purple” for the actively selected button which changes the viewport based on the selection.
f. Viewports covered in the next section.
2. HOME DASH PAGE
Refer to the attachment “[url removed, login to view]”. This should be displayed when the “HOME DASH” button is selected and when the program starts up.
The Home Dash UI must display:
a. Any web page read from a file containing the HTML. This can be anything.
b. Contain a link which says email address and a randomly chosen domain name was used for the purpose of this project. When clicked it should open a web browser and navigate to google home page.
3. SETTINGS PAGE
Refer to the attachment “[url removed, login to view]”. This should be displayed when the “SETTINGS” button is selected.
The Settings UI must display:
a. The webpage as illustrated. HTML for this viewport should be stored in a file and displayed into the viewport as illustrated.
b. The “Your Generally Settings” will be highlighted in Orange and the controls of droplist and radio buttons must be displayed where the initial settings is read from a “[url removed, login to view]” file.
c. The “APPLY” button does not SHOW until the user modifies the selection to be something different to what is selected (i.e. screen has been modified). For example: change the language selection to Chinese. Or the radio button clicked to say “No”.
d. When screen has been modified the APPLY button shows. If clicked it will save the changes to “[url removed, login to view]” file and reused again in step b) as the initialisation for the screen.
e. If the “Your Advanced Settings” is selected, then it must turn Orange to highlight that it is the actively selected and now show the “Advanced Settings” page.
f. The “Advanced Settings” page just contains an edit box containing a label “Your Name” in which the user can enter their name. And contain a check box containing label “Male”
g. Again like step b) the initial values are read from the “[url removed, login to view]” file.
h. Again like step c) when modified the “APPLY” button will show and if clicked will save the changes to the “[url removed, login to view]” file.