Automatic license file placement, like user presets

[David Healey]

@dannytaurus I include this in my installer, you could also do it through a HISE script.

[dannytaurus]

@David-Healey How would you do it with script?

[David Healey]

@dannytaurus I'd include the license in a .js file, then use File.writeString() to put it into a file in the app data folder.

[dannytaurus]

@David-Healey Gotcha. Problem with that method is keeping two separate copies/formats of the license text in sync, assuming you also want to display it on your website/elsewhere too.

I'm not even sure how I want to show/store the plugin license yet.

I looked at a bunch of other (well-known) plugins on my system and can't find any licenses/EULA files for most of them.

They either have it in a panel in the plugin, or it's just on their website.

[David Healey]

@dannytaurus I show it in the first page of the installer and it's on the website. Adding it into the app data folder too seems like a good idea so I might do that.

[dannytaurus]

@David-Healey said in Automatic license file placement, like user presets:

the first page of the installer and it's on the website

Yeah, that's all I was going to do too. But then I thought some persisted version on the user's disk might be good too.

I think probably the best way is to show it in the plugin, even if it's a footer link in a settings/credits panel.

That's the only way to be sure that the license always travels with the plugin.

[ustk]

Why not just verify if it's on the disk or not and pull it from the server?
Assuming plugins are connect to the internet for your license system in the first place...

EDIT: or even simpler, pull it at the same time you pull the plugin's license...

[dannytaurus]

@ustk I don't do plugin licensing, so my plugin has no server calls at all currently.

Not a bad idea though, pulling it from its web URL.

[David Healey]

@dannytaurus said in Automatic license file placement, like user presets:

Not a bad idea though, pulling it from its web URL.

Might as well just have a button that opens the web page in that case.

[dannytaurus]

@David-Healey No, because this is about persisting the file to the user's disk.

Although as I said earlier, I think the final best answer is to display the license directly in the plugin somewhere.

Then nobody could ever accuse the developer of not making the license easily available.

Website goes down - no problem
User moves the plugin to another machine - no problem
User wipes/moves/modifies their AppData folder - no problem

If the license is in the plugin itself, it can't be accidentally moved, deleted or overwritten, and it can't become unavailable because of server outage.

Probably going this route now...