|
From: Brian C. B. <Bri...@sh...> - 2003-07-19 01:44:28
|
Reposting: Hi all (extended form of Taj ;-), I was thinking about how the GUI of a program can really impact its success/failure. Looking at the GUI for rq.net, it seems to be lacking quite a bit. So I was thinking that perhaps a wizard like GUI might be nice. 1st Page: A general welcome to the RapidQ.NET program with a little about it and how to use it and of course, Taj's logo (don't you like me refering to you in the third person?). Can be disabled for future launches (with something like a 'Don't show this page again' checkbox). Any 'setup' can be done here. 2nd Page: Page to select the file to compile. "Next (Options)" button might lead to 3rd page, while "Finish (Compile)" might lead to 4th page. 3rd Page (optional): Options page where you can specify the language to compile to, and other options. 4th Page: Compile page where the file is compiled (with progress bar) if need be, select the path to the compiler. 5th Page: Finish - you get compile results and can either go back to step 2 (if your program had errors) or exit. So this could be as long as a 5 step program (Welcome, Select File, Set Options, Watch Compile, and View Output) or as short as a 3 steps (select file, watch compile, and view output). What do you think? Sincerely, Brian C. Becker @ www.BrianCBecker.com Shall we accept good from God, and not trouble? |