-
Notifications
You must be signed in to change notification settings - Fork 227
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
Add link to website if a new version is available #1980
Add link to website if a new version is available #1980
Conversation
20d576c
to
c4c4bf6
Compare
c4c4bf6
to
bfeed76
Compare
I'd prefer wording like "A Jamulus upgrade is available: click for details". Definitely without the exclamation mark (implies being commanded to something). |
Yes. Can change that. However the question is how the "click for details" page should look like. But that's something I need to worry about on the webpage. |
bfeed76
to
d112825
Compare
Ok. Changed it. Need to wait until autobuild is finished. |
Windows autobuild failed. Hopefully an update of the ASIO sdk will fix it: ann0see@2583800 Ok. Download the artifacts here: https://github.com/ann0see/jamulus/releases/tag/r_link-download-page |
Ok. See the updated screenshot above. |
@gilgongo I think that‘s something for you? |
d112825
to
6d0b21b
Compare
src/serverdlg.cpp
Outdated
lblUpdateCheck->setText ( "<font color=\"red\"><b>" + QString ( APP_NAME ) + " " + tr ( "software upgrade available" ) + "</b></font>" ); | ||
lblUpdateCheck->setOpenExternalLinks ( true ); // enables opening a web browser if one clicks on a html link | ||
lblUpdateCheck->setText ( | ||
"<font color=\"#c94a55\"><b>" + tr ( "A %1 upgrade is available: " ).arg ( APP_NAME ) + |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the font colour changing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "red" didn’t fit to the mixer background contrast wise. But we can also agree on another colour.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally we'd have a stylesheet (managed at application level) with a class... But if it's got to be an explicit hex code to look right, fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. But that's out of scope here probably. I think you should open an issue (and maybe even tag it as "good first issue" since I think it's easy to implement)
795626f
to
9a16ea2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Do we want to add a build version (with JACK, OS,...) as GET argument to the URL? This would enable us to automatically redirect the user to the correct download on jamulus.io e.g.: https://jamulus.io/upgrade?progversion=3.8.1&build=windows_jack while build= could also be a md5 hash of CONFIG QSysInfo::productType() |
9a16ea2
to
2ccecd2
Compare
Used the wrong argument for the version on the update url. Should be fixed now. |
d92919a
to
6a95ba4
Compare
For testing, build locally with Jamulus.pro |
6a95ba4
to
89a201a
Compare
Before we merge this 72e4ac1 needs to be reverted. However, now we have it as test commit |
* Update clientdlg.cpp * Update serverdlg.cpp * Update global.h * Spacing
So grab the artifact from the builds, run it as client and server, and let us know. |
Yup. Works as expected. |
Should be squash & merged. |
I'm still not 100% sure about the color/contrast of the message. I'll revert it to red but maybe a @jamulussoftware/designers might give a proposal (preferably in another PR) |
I just took a look here, and the current contrast ratio is 4.01:1. Ideally, to be pass WCAG AA guidelines for normal text (~18px) you'd want a ratio of >4.5:1. I'd advise against a full tinted red, as I think it'd make the ratio worse. A darker red (or something in this range) like #AB202C can work. |
Yes. Looks much better now! Thanks |
Oh, I didn't consider the color for the different skins. I don't think the dark red I suggested works with the fancy skin. Are you open to using different colors for normal and fancy? Or would you prefer a color that encompasses both skins? |
I was going to ask.... Here it's not skinned. It was partly why I was thinking the styling should be passed as an argument (though I'd pulled all the HTML out), to make it easier to apply skinning. |
It’s not that bad IMHO, but I think it’s out of scope of this PR to make the colours changable (since this would also involve the mute myself bar). |
The server recording highlight is on the mixer panel, so I guess that's elsewhere, but that's skin-dependent, IIRC. Stick with whatever colour is used in the Mute Myself indicator so at least we know it's meant to be the same in future. |
Ok. Reverted it back to "red". See updated screenshots. |
Thanks! I think this should have been squashed 😉 |
Mmmm.... 😁 |
Short description of changes
Adds a clickable link in the "new jamulus version available" message:
I think it would be good to have this one in the next release.
Context: Fixes an issue?
Sometimes users might find it confusing to only get notified that a new version is available but no actionable "solution" is provided. Therefore this will add a link to a page which is still to be created (currently just a redirect to jamulus.io).
Also see: #370 (comment)
Does this change need documentation? What needs to be documented and how?
Status of this Pull Request
Working implementation.
What is missing until this pull request can be merged?
Two approvals.
Checklist