@lainz
Did a bit more today. The app is much too fancy for its purpose, but it was an interesting exercise for me.
More/changed resourcestrings, so the .es.po file is now out of whack (I still need to tidy them up so hold off translation for now)
I changed DefaultTranslator to LCLTranslator so the app could deal with languages in a more interactive way. Another reason was the DefaultTranslator chooses 'es' on my system, despite an English-language system. It's probably fooled by my Spanish keyboard.
- Better interactive error-checking on inputs
- Language menu (only English/Español as yet)
- Hint system that runs on first use
- cfg file to store options
- 'About' dialog that uses app VersionInfo
- ..and other stuff
- I expect it could be refactored, but it seems to work in a user-friendly way and the code is maintainable.
Attached: current version 0.1.3.0
@GetMem I'm not sure anything needs to be added to the JSON - it seems enough for its purpose and it will be quick to download.
I have uploaded a test update JSON for you to test 'live'
https://sourceforge.net/projects/lazautoupdate/files/otherpackages/update_cryptini.jsonand
https://sourceforge.net/projects/lazautoupdate/files/otherpackages/update_cryptini_force.json (force update)
(A good protocol is that update JSONs must always have a filename which is distinct from regular OPM-generated JSONs. You could use a custom name-protocol for update JSONs such as 'update_<packagename>.json' - this avoids filename clashes with package JSON files created by OPM and stored in the same folder)