72647 Custom windows GUI in VC++ 6

This will be a VC++6.0 project. The delivered product will be a VC++ .dsw containing all source code in a .zip file which can be unzipped and compiled. We are on a tight deadline. The following points are to show our commitment to the project, and the level of commitment we will require from the developer/development team. The finished product must be delivered on the 21st of April, 2004. We would like to have 2 checkpoints where we see the current state of the code on the 7th and the 14th of April, 2004. 1/3 of the accepted bid will be placed in a ScriptLance escrow account. 1/6 of the accepted bid will be paid upon acceptance at the checkpoints on the 7th and 14th of April, 2004 by the bidders preferred method. The remaining 1/3 and the 1/3 in escrow will be paid/released up completion of the project. We require that the developer check his email and respond to all inquires within 24 hours. We require that the developer inform us to their progress at least every 48 hours. If the developer is unavailable for a period of 72 hours, we may at our discretion award the project to another developer. We would like the developer to provide a phone number for contact. Bids from programmers with strong feedback are encouraged. All copyrights and license for the provided code will be owned by us. Use of third party, GPL, and lGPL code must be discussed and/or described as part of your bid. This GUI will replace the windows CE explorer application. The GUI will be driven by a configuration file. The GUI will cover the entire desktop. The Gui will run in a RDP Environment. There must be very little back and forth chatter network chatter from the application in order to reduce bandwith requirements. The Gui will work with a touchscreen. Touchscreens function nearly identically to a mouse, but there are no "hover"/"mouseover" events. There is no use providing eyecandy for these events as they will never occur. There will be no way to exit the GUI. The desktop will be 1024x768 but the application should maximize itself to the client desktop size. The opening screen will be a license agreement for the software. It will have two button, accept and decline. The next screen will be the main gui (accept) or a message if the user does not accept the license agreement (decline). The text of both the license agreement and the declined response message will be located in flat files. The names of the files will be specified in the configuration file. The GUI will be able to incorporate several different Internet Explorer browser windows, java, or executable applications. The GUI will be able to force these applications to be a certain size. The size will be specified in the configuration file for each application. The GUI will allow those applications which have full screen modes to switch into full screen. The first application launched will require a random filename. This same filename must be passed on the command line to all other java and executable applications. This internet explorer application will have right-click mouse functionality disabled. A text box will be provided for URL navigation. Standard buttons for forward, backward, stop, home, navigation will be provided. The home URL will configurable and not changable by the user or external websites. The location of the buttons for navigation will be configurable. The browser will be "locked down" to prevent access to the file system. No files can be saved, and the allowable protocols (e.g. http://, https://) will be configurable. The background image for the GUI will be read from a file. The image will be specified in a config file. There will be up to 12 buttons placed in the GUI. The buttons will have two images (default/pressed) which will be read from a file and specified in the config. The buttons will be on top of all other GUI elements. The position of the buttons will be specified in the config. Pushing the buttons will cause a program, browser, or java app to launch. The launched program will overlay part of the GUI and attain focus. The launched program will appear in a window of the GUI, and always be on top of the GUI. e.g. the GUI should be transparent at the location where the application is shown. The buttons will be a member of a group. ButtonGroups Group1,group2,group3 ButtonGroup1 Button1,Button2,Button3 ButtonGroup2 Button4,Button5 etc. When a button is pressed, the applications launched by the other buttons which are a member of that group will be terminated, if they are running - that is, that if Button1 launches an application, pushing button2 or button3 will cause the application launched by button1 to terminate, if it is running. Pushing button 1 later will cause the application launched by button 2 or 3 to terminate. At no time may more then one application in a button group be allowed to run. The transparent area will be specified in the config file, and will contain a browser control when it does not contain another program. The program and program command line will be specified in a config file. The program must work and display correctly thru Remote Desktop Protocol. The GUI must be very polished, clean. No flickering. The code must be well documented, and clean. The code must have no memory or resource leaks and have a clean bill of health thru Purify. Config files Configuration files will contain name value pairs. The name will be seperated from the value with whitespace. Everything to the left of the first contiguous block of whitespace is the "name". Everything to the right of the first contiguous block of whitespace is the value. The config file to use will have a default, and be able to be changed from the command line when the program is launched. The name will be case insensitive. The value will be case sensitive. The selected developer will be presented with a background image to facilitate application development. We look forward to working with a strong developer or development team on this application and encourage your bids.