IMHO, we should follow these two STEPs:
- I think it would be good time to create a convention rule when a new HMG version it's being installed.
All of us we want to know where the HMG is installed, what folder it has been installed.
At HMG instllations we would execute a procedure of creating and/or rewrite the HMGPATH variable of our enviroment, then this will be accessible at any place by just by invocating the simple variable %HMGPATH%.
I know there are some user that prefer to use old HMG version... (It's a mistery to know why, I really still do not understand that)
But even for these users, this variable could be adjusted/rewritten to find the HMG path where ever be the HMG version.
This enviroment variable HMGPATH would helps a lot for working with the last installed HMG version.
And this is the best of best solution where now is a hole of undefined and important info in our work bench.
But this HMGPATH variable needs to be created in our enviroment. As the same is done in other programming tools.
- Reaching a consensus for HMGPATH variable creation for HMG, all HMG demands will be attended like as:
- SAMPLES compiling
- Compiling app by using a Build.bat in the path
- Pre-Processor routines in the compiling which also needs a Harbour path of our HMG folder
The best way to do it is be placed at: %windir%\System32 folder (by making at once with ADMIN rights of course).
This works for all Windows versions and this other Build.bat file must contains as follows:Note in this propose, that we gonna pass to use %HMGPATH% variable what's previously created by HMG installations program or being set enviroment (create/modified) manually by user as related at this instructions for example.
Code: Select all
@ECHO OFF CALL %HMGPATH%\Build.bat %1 %2 %3 %4
Conventions is so good when we need a common needing. This %HMGPATH% variable it should happen before. Now it's at HMG users and administrators to approve.
To use Notepad++ is also a good idea but not workable for everybody which prefer another source editors... and for improving this idea of PLUGINS in NPP must be posted (IMO) in another topic as tutorial for Notepad++.