Wish Secrets.txt

hatzisn

Expert
Licensed User
Longtime User
I just faced something that made me think of the following. Uploading a project I forgot to change some strings that are private to me resulting in uploading and reuploading.
So what I thought to avoid this in the future is a submenu that could be added in the IDEs - maybe tools menu - which would handle exactly this. There you could add a name value pair of strings which will contain what you want and this would be saved in a special folder in the project and embed them in the project's code let's say like "$SSID$" . When compiling, the code creation in B4X IDEs would replace these fields in the code with the given value. Now when we would like to share this code we could very well "export as zip" and the IDEs would create a null value for all values in this name-value pairs making a copy which you could ship with the zip not sharing the values of your secrets. The person that would receive it would be prompted to fill in their corresponding secrets. This could be done also in the meta files...
 

hatzisn

Expert
Licensed User
Longtime User
With the conditions if you share the project with "export to zip" the secrets are also shared with the code if they are hard coded...
 

walt61

Active Member
Licensed User
Longtime User
How about using @Peter Simpson 's suggestion combined with CustomBuildActions (or IDE comment links)? Haven't given it much thought, just an idea. (Could be a bad one :))

Edit: I mean, CBAs or IDE comment links to copy the 'real' secrets file or a dummy one to Files. You'd still have to remember to click the appropriate link before exporting.
 
Last edited:
Top