Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Macro GUI - should I move to HTML?
#1
I'm nearly finished with coding Macro del Diablo, and need to start working on making it look more like a finished app instead of a continuous series of pop-up dialogs and message boxes.

The macro now starts with a decent looking smart dialog with a fair number of controls (text inputs, date picker, combo and drop downs etc) for making all necessary settings to run the rest of the process; after that it runs for 5 or 6 minutes with occasional status boxes and OK/Cancel dialogs. I want to create a single window that will have the init smart dialog controls and then switch to displaying a series of progress points and possibly animations ("Now converting HDV files to WMV", "Archiving files to network" etc) to make all the waiting a little more interesting and informative while waiting...

Questions:

1. I'm leaning towards using HTML pages for the GUI because of familiarity (tho perhaps multi page dialog would work better?). Before I start substantially tweaking the code, I wanted to ask for your valued recommendations and any obvious pitfalls to avoid etc.

2. If I port over to HTML for the GUI, is there any way to display my initial smart dialog within a browser window (or vice versa -- I think I just answered my question...), or should I redo the input controls as an HTML form? Or perhaps suggest any other methods of saving some or all of that work?

3. This program will need to be compiled to exe, but will only be used on one or two edit stations -- is this a consideration in deciding which method to use (the workstations will certainly have IE, not sure if XP or Vista OS however...)?

Your help/opinions are always appreciated!

Steve

PS. I have another question, but I'll start a new thread on that topic...


[edit for clarity]


Messages In This Thread

Forum Jump:


Users browsing this thread: 1 Guest(s)