Convert GUI to CHR

I am not aware of any such tool. A lot of ABL code will just work across GUI (prowin32.exe/prowin.exe) and CHUI (_progres.exe). But of course the devil is in the details. Some ABL language features are explicitly GUI-only and are documented as such; anything to do with fonts, to name one example. There are many others. Also, some functionality will work in both display types but may not have the desired UI layout in CHUI without some modification.

Even if such a tool did exist, it's not clear to me what it would do in the case of functionality that has no CHUI equivalent, other than documenting which code should be refactored or removed.

Do you need to support GUI and CHUI concurrently or will it be a "big bang" change from one to the other?
 
Or... maybe... you have a program that you are running on Windows with prowin32.exe or prowin.exe and you have no GUI features and no need for any such features? If that is the case then you simple replace prowin.exe with _progres.exe.

There are an awful lot of Windows applications that pointlessly insist on running scheduled tasks and other headless code with prowin rather than _progres.
 
Rob Fitzpatrick said:
I am not aware of any such tool. A lot of ABL code will just work across GUI (prowin32.exe/prowin.exe) and CHUI (_progres.exe). But of course the devil is in the details. Some ABL language features are explicitly GUI-only and are documented as such; anything to do with fonts, to name one example. There are many others. Also, some functionality will work in both display types but may not have the desired UI layout in CHUI without some modification.

Even if such a tool did exist, it's not clear to me what it would do in the case of functionality that has no CHUI equivalent, other than documenting which code should be refactored or removed.

Do you need to support GUI and CHUI concurrently or will it be a "big bang" change from one to the other?
Click to expand...
Thank you for the answer.
I have CHR programs that are deleted. I only have the program with the GUI version.
I need to do the GUI to CHR conversion.
The original program (which was deleted) was a CHR program which was converted to GUI
I think it is necessary to do the conversion manually (Remove from the program any piece of code relating to GUI)
 
TomBascom said:
Or... maybe... you have a program that you are running on Windows with prowin32.exe or prowin.exe and you have no GUI features and no need for any such features? If that is the case then you simple replace prowin.exe with _progres.exe.

There are an awful lot of Windows applications that pointlessly insist on running scheduled tasks and other headless code with prowin rather than _progres.
Click to expand...
Thank you for the answer.
I replaced prowin.exe with _progres.exe, but the program does not compile in CHR, because it is a GUI program
 
How many of these programs need conversion? What are the compile errors

The conversion process may not be very difficult depending on how many programs there are and what the errors being encountered are.

Or it might be hopeless. You aren’t providing much detail on which to base an answer.
 
You must log in or register to reply here.
Back
Top