Skip to content
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

skin preview screenshots in Interface preferences #1525

Merged
merged 4 commits into from
Apr 5, 2018

Conversation

Be-ing
Copy link
Contributor

@Be-ing Be-ing commented Feb 26, 2018

#1377 implemented standard behavior for the skin selection combobox so it only changes the skin when the user presses the Apply button. To provide users a rough impression of what skins look like before they switch to a different skin, show a preview screenshot when a skin is selected with the combobox.

@Be-ing
Copy link
Contributor Author

Be-ing commented Feb 26, 2018

The screenshots should be updated right before every release to ensure they reflect the released skins.

Copy link
Contributor

@esbrandt esbrandt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for working on this long pending feature.

I feel the screenshoots should scale down at least to the same height. When flipping trough the list of available skins, the options below the screenshoots jump around.

The Deere screenshoot has a good size, it could be even a bit bigger IMO (400px Edit: 200px). Hard to make out some details with the smaller screenshoots, probably even harden when using HDPi displays.

Also, should we provide the screenshoots in the vanilla skin state? E.g. in the Deere screen, stacked waveforms are visible, but are not enabled by default.

@@ -29,7 +29,7 @@
<font/>
</property>
<property name="text">
<string>Skin</string>
<string>S&amp;kin</string>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

String changed by accident?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QtDesigner did this automatically. I can rebase and remove the noise from the diff.

<item row="1" column="1">
<widget class="QLabel" name="skinPreviewLabel">
<property name="text">
<string>skin preview screenshot goes here</string>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dummy text can be excluded from the translation template.
<string notr="true">skin preview screenshot goes here</string>

<widget class="QLabel" name="labelFullscreenOption">
<property name="text">
<string>Full-screen mode</string>
<string>Full-screen &amp;mode</string>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

String changed by accident?

@@ -56,6 +56,10 @@ QString SkinLoader::getSkinPath(const QString& skinName) const {
return QString();
}

QPixmap SkinLoader::getSkinPreview(const QString& skinName) const {
return QPixmap(getSkinPath(skinName) + "/preview.png");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about a more descriptive file name, e.g. preferences_skin_preview.png or preferences_skin_screenshoot.png?

@Be-ing
Copy link
Contributor Author

Be-ing commented Feb 26, 2018

I feel the screenshoots should scale down at least to the same height. When flipping trough the list of available skins, the options below the screenshoots jump around.

Yes, I will redo the screenshots...

Also, should we provide the screenshoots in the vanilla skin state?

Yes, good point. I will redo the screenshots with a fresh settings directory.

E.g. in the Deere screen, stacked waveforms are visible, but are not enabled by default.

Parallel waveforms are the default in Deere.

The Deere screenshoot has a good size, it could be even a bit bigger IMO (400px Edit: 200px). Hard to make out some details with the smaller screenshoots, probably even harden when using HDPi displays.

IMO details are unimportant for this. I do not want to make the screenshots so big that they clutter the preferences window. I'll try a height of 300 px.

@daschuer
Copy link
Member

daschuer commented Mar 3, 2018

Shouldn't this go to master?

@Be-ing
Copy link
Contributor Author

Be-ing commented Mar 3, 2018

It doesn't matter too much for me, but I thought you were bothered by the current behavior. IMO targeting this to master would be overly pedantic about feature freeze. The code changes are really trivial and clearly won't break anything else. OTOH reverting to the 2.0 behavior of loading skins as soon as they are selecting (before pressing Apply) would be more difficult than merging this.

@daschuer
Copy link
Member

daschuer commented Mar 3, 2018

OK, than let's keep this for 2.1

@nopeppermint
Copy link
Contributor

nice, maybe you could add also a preview of the color schemes in Shade

@Be-ing Be-ing added this to the 2.1.0 milestone Mar 8, 2018
@daschuer
Copy link
Member

I feel the screenshoots should scale down at least to the same height. When flipping trough the list of available skins, the options below the screenshoots jump around.

Yes, that is annoying. IMHO the screenshots should be all at the same width as well.
A smaller size like the current Shade screenshot would be nice. It would work to me, to how only the top right part, to find a compromise between screen shot size and down scaling.

We need also a default screenshot for skins without a screenshot.

@daschuer
Copy link
Member

Is this still a 2.1 candidate?

@Be-ing
Copy link
Contributor Author

Be-ing commented Mar 19, 2018

Yes. I'll update the screenshots when all pending skin PRs are merged.

@daschuer
Copy link
Member

So this PR should only include the default screenshot, right?
Can you rebase this PR to not include the outdated screenshots into the git history?

@Be-ing
Copy link
Contributor Author

Be-ing commented Mar 19, 2018

Yes, this PR should only show the skins in the default configurations. I'll rebase it when the time comes.

@daschuer
Copy link
Member

I mean, we can merge this now, if you remove the real screenshots and add a placeholder for any skin without a screenshot.

@daschuer
Copy link
Member

@Be-ing is this still a 2.1 candidate?
Can you add the current screen shots by rebasing this, to keep this PR small sized?
Can you do the screenshots with 100 % scaling to not show scaling issues if any?

@Be-ing
Copy link
Contributor Author

Be-ing commented Apr 1, 2018

What resolution should I do the screenshots at? I am thinking of taking fullscreen screenshots on my old laptop at 1366 x 768 and scaling them down to 300px or 400px height.

@daschuer
Copy link
Member

daschuer commented Apr 1, 2018

They should be taken with design size.
As of Shade 1024*600
Resize to 300 is already quite high. How about 250

@Be-ing
Copy link
Contributor Author

Be-ing commented Apr 1, 2018

We can't use Shade's minimum size for the screenshots because not all skins support that. We could use the lowest common denominator size of all skins.

@daschuer
Copy link
Member

daschuer commented Apr 1, 2018

Yes that's right. I mean to use the optimum screen size for each skin. I would say it is full HD for LateNight for example. For Tango, we can decide if we want to show the netbook mode or the 4 deck full scale mode.

@ronso0
Copy link
Member

ronso0 commented Apr 1, 2018

For Tango, we can decide if we want to show the netbook mode or the 4 deck full scale mode.

I propose 1280px or 1366px with default configuration: 50px waveforms, 2 decks, 2 FX units, ...

@daschuer
Copy link
Member

daschuer commented Apr 3, 2018

src/preferences/dialog/dlgprefinterfacedlg.ui
uic: Error in line 241, column 42 : Unexpected attribute notr
File 'src/preferences/dialog/dlgprefinterfacedlg.ui' is not valid

@daschuer
Copy link
Member

daschuer commented Apr 5, 2018

Ping! An other day delay.
We need a rc now. Will you have time to finish this today?

@daschuer
Copy link
Member

daschuer commented Apr 5, 2018

Placeholder:

placeholder

@daschuer
Copy link
Member

daschuer commented Apr 5, 2018

Be-ing#19

image

@Be-ing
Copy link
Contributor Author

Be-ing commented Apr 5, 2018

Don't merge quite yet, still a few little quirks to fix in the code.

@daschuer
Copy link
Member

daschuer commented Apr 5, 2018

Please use the optimum size for the screenshots, not a unique size.
This shows how the skin is intended to use.
Which is the mayor use case for this preview feature.
This lines also quite well up, if we have one day a tiny skin, or a full HD only skin.

@Be-ing
Copy link
Contributor Author

Be-ing commented Apr 5, 2018

The screenshots show the default skin configurations.

@Be-ing
Copy link
Contributor Author

Be-ing commented Apr 5, 2018

The "(64 sampler)" skins are not showing the screenshot for their parent skin. Do you have any hints how to make that work?

@Be-ing
Copy link
Contributor Author

Be-ing commented Apr 5, 2018

Nevermind, I'll take screenshots showing 64 samplers for those.

@Be-ing
Copy link
Contributor Author

Be-ing commented Apr 5, 2018

Okay, done.

@Be-ing Be-ing merged commit d16e2c2 into mixxxdj:2.1 Apr 5, 2018
@ronso0
Copy link
Member

ronso0 commented Apr 6, 2018

Nice!
Deere samplers could really use the cover art. Also I notice Tango preview needs 8 samplers, too.

@Be-ing
Copy link
Contributor Author

Be-ing commented Apr 6, 2018

I notice Tango preview needs 8 samplers, too.

We could change the screenshot. I took it full screen at 1366 x 768 then resized to 250px height and preserving the aspect ratio.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants