Something that should be thought about is how the source code and the repository is organised.
Note - It may be useful to combine all AHK files in the repository into one. For this we can use this
For a start we may want a folder: "src". In this folder we will keep:
The main script, the script to compile, should probably be Main.AHK.
All inclusion statements should be contained in a separate Headers.AHK.
A folder lib_core (storing all .AHK files for the core features compiler.)
A folder lib_emb (storing folders of .AHK files built to extend MapBasic)
Here's a picture of how I envision it:
It is likely to end up different to this and many files which should be separate will likely be combined together for splitting later on. I also still don't know whether the header file will work as I think it will. It's all currently untested but this will be much better than its current state.
Something that should be thought about is how the source code and the repository is organised.
Note - It may be useful to combine all AHK files in the repository into one. For this we can use this
For a start we may want a folder: "src". In this folder we will keep:
The main script, the script to compile, should probably be Main.AHK.
All inclusion statements should be contained in a separate Headers.AHK.
A folder lib_core (storing all .AHK files for the core features compiler.)
A folder lib_emb (storing folders of .AHK files built to extend MapBasic)
Here's a picture of how I envision it:
It is likely to end up different to this and many files which should be separate will likely be combined together for splitting later on. I also still don't know whether the header file will work as I think it will. It's all currently untested but this will be much better than its current state.