This feature is available from OpenBuilder 047 and WinBuilder.
Each script can be updated pressing the "update" button wich will look at the default updates file (updates.ini) if there is a newer version of this script, in case this is true it will download the file.
There are two ways of downloading a new script:
- Using direct download
- Using MD5 checksum
It will use the download link available on updates.ini and will directly overwrite the older script file.
This method is fast and simple, but may also lead to some problems.. on long files the downloaded might get corrupted if the network fails, in this case the older working script is replaced by a corrupted version.
Using MD5 checksum:
It's the recommended way for publishing your works, adding a MD5 check on your updates.ini file will allow the program to download the file onto a temporary folder and compare the MD5 check from the updates.ini against the MD5 signature from the downloaded file. Only if this file passes the test it will overwrite the older version.
How to make an MD5 checksum?
Before making an MD5 checksum you should ensure that your file is ready to be uploaded and that all changes have already been made. It only takes one byte to output a completely different MD5 signature, so you should ensure that you upload an intact version of your file.
Getting the MD5 checksum is easy. Go to the options tab on the script window and press the "Calculate MD5" button. The result on the edit window is the MD5 byte signature of your script - screenshot
How to make an updates.ini?
You need to list your updated script or scripts on an "updates.ini" file to allow them to be downloaded by others.
Here's a brief description and template to make your own update host:
Open notepad, copy and paste this code:
Edit the values to suit your script:
"Test.script" - is the filename of your script (it's not needed to include path)
"001" - is the version of your script, at this moment only numbers without commas are accepted, wich means that 1,1 and 1,2 will all be seen as 1 by the update service. You should use 1 or 2 or 3 or 4 or 5... to keep track of your versions.
http://www.boot-land...pts/Test.script - is the direct link to the updated script, if you wish it can be different from where updates.ini is hosted.
How to include MD5 signature?
Simply add your previously calculated MD5 on the end of the update line, like this example:
ps: don't forget to add a comma to separate the web link from the MD5 signature
You can save all changes and close the updates.ini, now the uploading..
Uploading your files
You should ensure you use an account with ftp acess to make your life easier, if you don't have an account yet, you can look on google for "free ftp" and a couple of good options will appear. FTP is really the way to go if you want to update frequentely your files.
All active script developers get an ftp account hosted on boot-land.net to host all their works.
After you upload your files it's time to share them with others.
Inside the same options tab where MD5 is located, you'll notice a text box titled "Custom updates server", this is a value that customizable for each script file, wich allows for scripts to be updated from different developers - screenshot
You can add the full adress to the your updates.ini (but you don't need to add updates.ini on it) like in the example below:
WinBuilder will automatically look for http://develop.boot-...tes/updates.ini this is reason it's kept outside the link.
If you have a new script and wish to keep up with all bugfixing while others are testing, you should already prepare this in the first script before publishing, this way it will make your updates work much better and make this process much easier for others.
I hope this guide is easy enough to follow, but let me know if there is any question or problem using the instructions from here.
I'll post them later on the wiki.