This makes it easier to launch Signet and testnet4 on Windows. Follows the same pattern as testnet.
Before:
After:
(the testnet4 icon is the same as testnet3, not in the above screenshot)
This makes it easier to launch Signet and testnet4 on Windows. Follows the same pattern as testnet.
Before:
After:
(the testnet4 icon is the same as testnet3, not in the above screenshot)
Concept ACK
Tested it on Windows and it works as expected except the color of logo for signet.
0 Directory: C:\Users\Test\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Bitcoin Core
1
2
3Mode LastWriteTime Length Name
4---- ------------- ------ ----
5-a---- 18-10-2022 15:55 890 Bitcoin Core (64-bit).lnk
6-a---- 18-10-2022 15:55 1774 Bitcoin Core (signet, 64-bit).lnk
7-a---- 18-10-2022 15:55 1776 Bitcoin Core (testnet, 64-bit).lnk
8-a---- 18-10-2022 15:55 885 Uninstall Bitcoin Core (64-bit).lnk
we have actual ico files under res for the main and testnet icons, you would need to introduce a bitcoin_signet.ico with the correct yellow hue applied under src/qt/res in order to introduce the correct icon.
Looking ahead, I’d like to move away from having these different launchers to being able to select the chain from within the gui.
Most users won’t know what “signet” means, and it isn’t self-explanatory like “testnet”…
If you want a shortcut, please figure out a way to resolve this.
NACK as-is.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
For detailed information about the code coverage, see the test coverage report.
See the guideline for information on the review process.
Type | Reviewers |
---|---|
ACK | achow101, laanwj, TheCharlatan |
Concept NACK | luke-jr, ghost |
Concept ACK | michaelfolkson, BrandonOdiwuor |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
Reviewers, this pull request conflicts with the following ones:
PACKAGE_*
variables to CLIENT_*
by hebasto)If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
I added the word “test” to the application name.
Since Bitcoin Inquisition uses the default Signet to deploy several proposed soft forks, I think it’s useful to offer easier access (which requires the Inquisition folks to rebase after this is merged).
See #8285 for additional context.
I generated the icon from the mainnet icon by applying the same hue and saturation adjustments:
Though the -modulate command uses percentage instead of degrees, so it was a bit confusing to convert:
0convert src/qt/res/icons/bitcoin.ico -modulate 100,87,119.4 src/qt/res/icons/bitcoin_signet.ico
I added a screenshot in the PR description.
The big icon looks correct, but the mini version in the search result does not. I probably need to change the ImageMagick command somehow. I could also try using the Testnet icon as the basis (and rotate the hue in the other direction).
I think I found the right incantation, using the high res PNG as input:
0convert src/qt/res/icons/bitcoin.png -modulate 100,87,119.4 -define icon:auto-resize="256,48,32,16" src/qt/res/icons/bitcoin_signet.ico
I updated the PR description screenshot.
I noticed that testnet has 4 icon resolutions, which I’ve used for signet too. But mainnet has 9. I could regenerate that one, but it would only save 11kb.
141@@ -141,6 +142,7 @@ Section -un.post UNSEC0001
142 Delete /REBOOTOK "$SMPROGRAMS\$StartMenuGroup\Uninstall $(^Name).lnk"
143 Delete /REBOOTOK "$SMPROGRAMS\$StartMenuGroup\$(^Name).lnk"
144 Delete /REBOOTOK "$SMPROGRAMS\$StartMenuGroup\@PACKAGE_NAME@ (testnet, 64-bit).lnk"
145+ Delete /REBOOTOK "$SMPROGRAMS\$StartMenuGroup\@PACKAGE_NAME@ (signet, 64-bit).lnk"
test
here, pushing fix.
Most users won’t know what “signet” means, and it isn’t self-explanatory like “testnet”…
Most users wont use it and it just helps devs and power users on windows. They know what signet means. Everyone else clicking on it is same as downloading a malware instead of bitcoin core which is not something this repo needs to solve. First match in search is always “bitcoin core (mainnet)” and even that would open other network if bitcoin.conf has other network set.
So this NACK makes no sense for windows users.
I added the word “test” to the application name.
Since Bitcoin Inquisition uses the default Signet to deploy several proposed soft forks, I think it’s useful to offer easier access (which requires the Inquisition folks to rebase after this is merged).
See #8285 for additional context.
I generated the icon from the mainnet icon by applying the same hue and saturation adjustments:
Though the -modulate command uses percentage instead of degrees, so it was a bit confusing to convert:
0convert src/qt/res/icons/bitcoin.ico -modulate 100,87,119.4 src/qt/res/icons/bitcoin_signet.ico
I added a screenshot in the PR description.
The big icon looks correct, but the mini version in the search result does not. I probably need to change the ImageMagick command somehow. I could also try using the Testnet icon as the basis (and rotate the hue in the other direction).
NACK for “test signet”
signet
already helps to know its NOT mainnet
I don’t see any harm in adding the word “test”. A user who searches “bitcoin” will see the “signet” entry in their search results and wonder what it is, perhaps even worry about it. Without the word “test” the only two ways to figure out are to google “what is signet” or to launch the application.
I don’t expect most users to know what “mainnet” is. They obviously know what Bitcoin is, but they may not know that one or more test networks exist.
I don’t expect most users to know what “mainnet” is. They obviously know what Bitcoin is, but they may not know that one or more test networks exist.
If someone doesnt know what is mainnet they wont use bitcoin core as a wallet.
Concept ACK
Perhaps the Bitcoin Design community will have a view on the wording. I’d go with standalone “signet” but I haven’t done any user research on whether this isn’t sufficiently informative.
141@@ -141,6 +142,7 @@ Section -un.post UNSEC0001
142 Delete /REBOOTOK "$SMPROGRAMS\$StartMenuGroup\Uninstall $(^Name).lnk"
143 Delete /REBOOTOK "$SMPROGRAMS\$StartMenuGroup\$(^Name).lnk"
144 Delete /REBOOTOK "$SMPROGRAMS\$StartMenuGroup\@PACKAGE_NAME@ (testnet, 64-bit).lnk"
145+ Delete /REBOOTOK "$SMPROGRAMS\$StartMenuGroup\@PACKAGE_NAME@ (test signet, 64-bit).lnk"
64-bit
here and above?
Name "@PACKAGE_NAME@ (64-bit)"
though, not sure if that’s safe.
175@@ -176,6 +176,7 @@ QT_RES_ICONS = \
176 qt/res/icons/address-book.png \
177 qt/res/icons/bitcoin.ico \
178 qt/res/icons/bitcoin_testnet.ico \
179+ qt/res/icons/bitcoin_signet.ico \
Or we could just drop testnet3 :-P
I find the difference in color useful enough.
I find the difference in color useful enough.
Then, it would be better to have a tiny script in the build process to create the .ico
, no? This would make it reproducible, documented and easily modifiable, without on each modification bloating the git repo by 50kb
The incantation is in the commit message. Adding a script makes sense, but I’m not familiar enough with the (native) build tools to know where to add it. This particular command would also add a dependency to imagemagick (if we don’t use it already), though I’m sure the operation can be done with other tools if needed.
Seems better to do in a followup and generate the testnet icon that way too.
The PR didn’t seem to attract much attention in the past. Also, the issue seems not important enough right now to keep it sitting around idle in the list of open PRs.
Closing due to lack of interest.
cd src/qt/res/icons
convert bitcoin.png -modulate 100,87,119.4 -define icon:auto-resize="256,48,32,16" bitcoin_signet.ico
This commit also removes the 64-bit mention from testnet.
src/Makefile.qt.include
) and added a testnet4 shortcut.
ACK cfd03de965a081facbd72316c76603dd7aa511bd
Did not test, but the code matches the pattern used for the other networks.