pascal/lazarus-ccr
1
0
Fork 0
Code Issues Releases Activity

Updates Inno setup files

Browse Source 
git-svn-id: https://svn.code.sf.net/p/lazarus-ccr/svn@5500 8e941d3f-bd1b-0410-a28a-d453659cc2b4
This commit is contained in:
gbamber
2016-12-15 08:44:34 +00:00
parent ef94278c96
commit 9d70cf2465
2 changed files with 32 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
applications/json_packager/deploywin/readme.txt
View File

@ -3,8 +3,6 @@ README FOR External OPM JSON package Editor
* This application is for component writers who wish to publish updates for the Online Package Manager.
* The update is packaged in a ZIP file, and uploaded along with a configuration file in json format.
* The json file can be manually edited, but this GUI application can make and edit the JSON file so that it is always correct for OPM.
* On startup it will create an \updates folder which can be used as your deployment folder for the updated app.

35
applications/json_packager/deploywin/readmepreinstall.txt
View File

@ -1,6 +1,35 @@
Choosing an installation folder
--> Please read! - Choosing an installation folder
===============================
* By default, this app will install into your Program Files folder.
* By default, this app will install into your Program Files folder,
but the next dialog will invite you to change that.
* The best place to install it is in your development folder,
where you have your component code
i.e. /component_root/latest_stable/
* Suggested structure (optional):
* /component_root/latest_stable - component release source files
* /component_root/latest_stable/sourcezip.zip
- Original zipped release files for OPM (to be uploaded)
* /component_root/latest_stable/jsoneditor.exe
* /component_root/latest_stable/updates/update_component.json
- Generated update json (to be uploaded)
* /component_root/latest_stable/updates/updatezipfile.zip
- Updated zipped source files (to be uploaded)
* Each unique component should have its own copy of jsoneditor.exe
* It is designed to be deployed in multiple locations
* Each copy has a unique cfg file
* On first run, jsoneditor.exe will make 2 subfolders:
* /updates
* /locale (for the language files)
* It also makes a config file in the Users/<youname>/Appdata area
* A better place to install it is in your development folder - where you have your component code