Don't always create a Shortcut

[Siecje]

Do you have to always create a Shortcut?

I have created a command to run in the Command Prompt and it takes arguments. I don't need a shortcut.

[takluyver]

I've considered dropping the requirement before, but for now I think it's a reasonable compromise. The typical use case I see for Pynsist is a GUI application which will be launched from the start menu, so that's what I'm focussed on.

That said, I think it should be easy to cancel the shortcut in a custom template, if you want to experiment with that. There are already blocks in the template called install_shortcuts and uninstall_shortcuts, so I think all you'd need to do is override those to be empty.

I've been meaning to write a doc page explaining the design choices behind Pynsist, and what to do if you want to do something a bit different.

[takluyver]

I've been meaning to write a doc page explaining the design choices behind Pynsist, and what to do if you want to do something a bit different.

And I finally got round to it:
http://pynsist.readthedocs.io/en/latest/design.html

[Siecje]

Might also want to mention

1. Why Pynsist doesn't automatically detect which packages to include?
2. Why there isn't a .exe file in the install directory?
3. Why Pynsist doesn't try to hide that the application was written in Python or the application source code?

[takluyver]

Thanks, I'll have a think about those

[takluyver]

I finally got around to listing and explaining things that I don't intend to do: 88f56f9

[Siecje]

You mention Single-file executables but there isn't even a .exe file in the install directory.

[takluyver]

If you define commands there are exes in a subdirectory. I still think that for launching a GUI application an entry in the start menu is more important than an exe, but it's not as straightforward as it was when I started Pynsist.