-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows installer #360
Comments
I'll start tracking the work here. You can assign this to me if you would like.
I've found a way to set the background image, however it requires a bmp image rather than a png. I believe we can covert the background image using the dub package imageformats. The background image can only be set by using the Ultra-Modern User Interface for NSIS. This extension makes the UI look nicer anyways so I'm okay with this. |
Hi, can we disallow HTML file as licence file since there is no rightful way to convert it to text? |
With regards to PNG, could you instead add a new key to the plugin.json, and the user would add a .bmp file no? |
Sure. Should we have a license.txt for Windows and a license.html/license.md for MacOS? Or just a license.txt for all?
That would definitely be the simpler route. And I suppose it wouldn't be too much to ask the user to convert the png to bmp. |
Doesn't look that modern to me. Screenshot on the linked page reminds me of 2010.
PowerShell should allow us to convert images, too |
The less dependencies the better, so if we can avoid depending on Ultra-Modern and the cost is not having a background image, then I'm all for not having a background image! |
Also, it shouldn't be to hard to use a custom solution for background images. Nevertheless, does anyone use background images for their installers nowadays? |
Yeah its a bit misleading! Changing the background makes it look a little better though. I think Modern UI (which is built into NSIS) looks better than UltraModern UI (can be installed with NSIS all as one install). Modern UI only has the ability to change the header image though. If we are going to have a separate bmp it may be better to just make a header bmp that has the company logo and use that instead. @p0nce The installer I sent you previously was built with Modern UI. |
I liked that installer! Let's go header and separate bmp then? Looks like a win as you said. |
Great! So do we want to have a separate text and html file for the license? Or only a single text file to be used on the mac installer as well? I'm fine with either way. |
I'd say those formatted (RTF, HTML, etc.) license text neither look modern nor good nor justify the bloat they might introduce. |
Yup, I'd say we should force a Markdown licence, that will look acceptable in text form and is converted to HTML for the Mac installer already. I don't think anyone use Dplug with a HTML licence and allowing it to be fully custom doesn't really work (it's too much powerful for the use case). |
What should we do about
I'm not sure if it makes much sense since to move the fields to |
Another option would be maybe to make the |
Mmmm it seems for the Mac installer I've choosen to duplicate the field So I'd vote for 3 if only to make that mistake consistent. :| and 2 later on but this is not your problem anymore :) |
Unfortunately I had to disable the |
Shouldn't it be possible to let the user select what sub-components (VST, VST3, x64, x86) to install, plus have a size count for each of those? At least, that's what other installers do. |
I don't think "space required" is super interesting. A dplug plug-in will almost always display a small size, which isn't particularly a good thing as far as consumer go. You may remove that feature without damage. I don't think it really affect the decision to install or not. |
|
No description provided.
The text was updated successfully, but these errors were encountered: