open-watcom / open-watcom-v2

Open Watcom V2.0 - Source code repository, Wiki, Latest Binary build, Archived builds including all installers for download.
Other
958 stars 157 forks source link

Enhancement suggestions on windows #1168

Open winspool opened 9 months ago

winspool commented 9 months ago

In an attempt to try bug #1167 on Win11 (64bit), i installed: https://github.com/open-watcom/open-watcom-v2/releases/download/Current-build/open-watcom-2_0-c-win-x64.exe and found some things, which i think, can be made more modern:

jmalak commented 9 months ago

I have a note to IDE. IDE cannot work with source files as standalone, you need always specify project first and one target as minimum then you can add any source file. IDE is strictly based on project and target items hierarchy. Source file is lowest hierarchy item. If such functionality is required then some dummy/default project and target must be created first to be able add source file and edit it. !!! IDE is not text editor and doesn't include editor, it call external editor if item is source file !!! An IDE is just a framework for building an executable (top of the hierarchy) and works with object dependencies and has defined rules for what should be done with each type of object, etc. The IDE does nothing but call various tools according to the rules.

To installer changes. Take into account that installer is character/GUI mixed application that must works on all supported OS-es with single source code. Therefore it use part of gui project (single API for character and graphical windows system) and there are limitation dictated by this API. May be it will require enhancement/fixing of UI/GUI project API before you will be able realized such changes in installer.

Any useful contribution is welcome.

joncampbell123 commented 9 months ago

I have a note to IDE. IDE cannot work with source files as standalone, you need always specify project first and one target as minimum then you can add any source file. IDE is strictly based on project and target items hierarchy. Source file is lowest hierarchy item. If such functionality is required then some dummy/default project and target must be created first to be able add source file and edit it. !!! IDE is not text editor and doesn't include editor, it call external editor if item is source file !!! An IDE is just a framework for building an executable (top of the hierarchy) and works with object dependencies and has defined rules for what should be done with each type of object, etc. The IDE does nothing but call various tools according to the rules.

To installer changes. Take into account that installer is character/GUI mixed application that must works on all supported OS-es with single source code. Therefore it use part of gui project (single API for character and graphical windows system) and there are limitation dictated by this API. May be it will require enhancement/fixing of UI/GUI project API before you will be able realized such changes in installer.

Any useful contribution is welcome.

What minimum size character display is the installer designed for? 80x25? Perhaps the GUI could just size it's background window based on 80W by 25H where W and H are the dimensions of a reference character, perhaps the letter "M", and work within that. Give it a title bar for the user to drag around and it would work like any other installer.

jmalak commented 9 months ago

If I remember correctly then Installer is reading screen geometry on host it is part of GUI project initialization. By example on DOS you can switch your mode to more then 80x24 and installer will use it. The same on linux there is read geometry of terminal and installer use full size. It rearange size of dialogs with regards to screen size. In installer is nothing related to setup screen geometry (as mode switching). Only on Windows and OS/2 where GUI is available installer is running in GUI mode on other hosts only character mode installers are available. It is completely dependent on current host setting.

joncampbell123 commented 8 months ago

Then perhaps what the Windows and Linux installers could do is simply not create the background window at all. Just have the dialog box to install with, just like every other installer out there these days. People would prefer to be able to do something while an installer is running, like browse the web.