Windows installer #49
Comments
|
Wow! This looks great!! Thank you very much. I will have to check it over when I get some time. I see the merge requests and will have a look over Christmas period hopefully. Don’t be stressed if it takes me a while to get back to you. Time is limited currently.
Thanks again
Ted
Sent from Yahoo Mail for iPhone
On Monday, December 17, 2018, 6:58 pm, Marc Würth <[email protected]> wrote:
Hi Ted,
The about page on the product website of QuickHash states:
No installation needed making it portable and easy to run or delete after use.
...
No installation. No wizards. No registration. Just double click and use, instantly (or Linux users can also use Debian packages to install if they wish)
I agree, it is very nice to not need to execute an installer/installation wizard to be able to use a small tool such as QuickHash.
Nonetheless, in a business environment it can be mandatory to pre-install tools or at least make the permanent installation of a tool throughout several machines more convenient. This is where an installater/installation wizard comes in.
Because I felt it would be even cooler for QuickHash to provide such an installer (for Windows at least), because I have some experience in creating installation scripts with NSIS (Nullsoft Scriptable Install System) and because just for fun, I created an NSIS based installer script for QuickHash.
Actually, I provided two variants. They are pretty much the same but they install QuickHash into different folders (by default):
1.the program files, e.g. ``C:\C:\Program Files (x86)\QuickHash"
- the local app data folder, e.g. "C:\Users\Ravage\AppData\Local\QuickHash"
Problem with the first is, that QuickHash tries to write the UI state into an XML file within the same folder, which doesn't work because of missing write privileges on that folder.
Thus, currently only the second installer works without problems.
Let me know, if you want to include the installer script into QuickHash.
It was fun fiddling around, anyway.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
No problem. If you want me to send you the precompiled installers from both version or need help compiling them, just say so. You can also reach me by mail or Skype. |
This is default behavior on Windows and Mac if the filename wasn't set. On Linux it's saved as a hidden file in the user's directory. I don't know if the filename can be set for each OS in a dynamic way inside unit2.pas. My suggestion would be something like |
@darealshinji sounds reasonable. |
This comment has been minimized.
This comment has been minimized.
Could you create a issue for that?
Can we move this discussion to a separate issue? |
|
Hi Ted,
The about page on the product website of QuickHash states:
I agree, it is very nice to not need to execute an installer/installation wizard to be able to use a small tool such as QuickHash.
Nonetheless, in a business environment it can be mandatory to pre-install tools or at least make the permanent installation of a tool throughout several machines more convenient. This is where an installater/installation wizard comes in.
Because I felt it would be even cooler for QuickHash to provide such an installer (for Windows at least), because I have some experience in creating installation scripts with NSIS (Nullsoft Scriptable Install System) and because just for fun, I created an NSIS based installer script for QuickHash.
Actually, I provided two variants. They are pretty much the same but they install QuickHash into different folders (by default):
Problem with the first is, that QuickHash tries to write the UI state into an XML file within the same folder, which doesn't work because of missing write privileges on that folder.
Thus, currently only the second installer works without problems.
Let me know, if you want to include the installer script into QuickHash.
It was fun fiddling around, anyway.
The text was updated successfully, but these errors were encountered: