Binaries to 1.20

transfered all files to 1.20
added code to create recreate FoxBin2Prg
This commit is contained in:
Lutz
2023-08-27 20:01:54 +02:00
parent 97f3cf5698
commit fea3596fbc
183 changed files with 309 additions and 338 deletions

View File

@@ -16,9 +16,9 @@
Start reading our code and you'll get the hang of it. We optimize for readability:
- Beautification is done like:
- Keywords: Mixed case
- Keywords: UPPER case
- Symbols: First occurence
- Indentation Tabs, 1
- Indentation Space, 1
- Indent anything then Comments
- Please do not run BeautifyX with mDots insertion against the code.
- We ALWAYS put spaces after list items and method parameters (`[1, 2, 3]`, not `[1,2,3]`), around operators (`x = 1`, not `x=1`).
@@ -32,10 +32,10 @@ Stuff is a bit scattered, so this is where to look up.
- See this [guide](https://www.dataschool.io/how-to-contribute-on-github/) for setting up and using a fork
- If allready forked, pull the recent state, or get most recent version otherwise.
2. On top of _FoxBin2Prg.prg_ there are two version numbers:
`#DEFINE DN_FB2PRG_VERSION 1.19`
`#DEFINE DC_FB2PRG_VERSION_REAL '1.19.60'`
`#DEFINE DN_FB2PRG_VERSION 1.20`
`#DEFINE DC_FB2PRG_VERSION_REAL '1.20.00'`
3. Please set the **minor** part of _DC_FB2PRG_VERSION_REAL_ to a new number.
**Do not** alter the **1.19** part. This is written to the text files.
**Do not** alter the **1.20** part. This is written to the text files.
Alteration might force that the files must be newly commited, what is not everybodies taste.
4. Add a meaningfull description of the change in the changes list on top of _FoxBin2Prg.prg_.
The most recent entries for changes in the middle of this section around _* </HISTORIAL DE CAMBIOS Y NOTAS IMPORTANTES>_,
@@ -48,8 +48,7 @@ Stuff is a bit scattered, so this is where to look up.
8. If a change to the parameters is made, change _C_FOXBIN2PRG_SYNTAX_INFO_EXAMPLE_LOC_ properties.
9. For changed functionality, add descriptive text on the appropriate _.md_ file in _docs_ folder.
10. Please alter the footer of \*.md files touched to recent date.
11. **The follwing steps are not neccesary, if you use *VPXDeployment* to create a new version that is applicable for Thor use.**
12. Create a template _foxbin2prg.cfg.txt_ for general settings or _foxbin2prg.dbf.cfg.txt_ for the settings per table.
11. Create a template _foxbin2prg.cfg.txt_ for general settings or _foxbin2prg.dbf.cfg.txt_ for the settings per table.
- Do this even if no change to the setting to change the version number inside this files.
- Or change version number in those files manually
- **Note**. If you are not on an English comp, set the value _Language: EN_ in your local _foxbin2prg.cfg_ to create English files.
@@ -59,13 +58,19 @@ Stuff is a bit scattered, so this is where to look up.
DO FoxBin2Prg.prg WITH "-c","foxbin2prg.cfg.txt"
DO FoxBin2Prg.prg WITH "-t","foxbin2prg.dbc.txt"
```
13. Alter the version number for the EXE to the version used above.
14. Compile to EXE **in VFP9 SP2**
16. commit
17. push to your fork
18. create a pull request
12. Alter the version number for the EXE to the version used above.
13. Compile to EXE **in VFP9 SP2**
14. Create the text representation of the binary sources running like
```
CD "path_to_FoxBin2Prg"
*This uses a special configuration
DO Create_FoxBin2Prg.prg
```
15. commit
16. push to your fork
17. create a pull request
Thanks
----
Last changed: _2023/08/26_
Last changed: _2023/08/27_