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

fix: spacing in artist pages, translation and cards #645

Merged
merged 1 commit into from
Feb 11, 2021

Conversation

ferferga
Copy link
Member

@ferferga ferferga commented Feb 1, 2021

  • Better spacing between albums
  • Remove the overlay from card
  • Translatable tabs

Spotify
image

Vue before
image

Vue after
image

@dkanada
Copy link
Member

dkanada commented Feb 1, 2021

I can count six different left margins in a single photo. Even the previous state had five, although the bottom padding on the title is a welcome change.

@heyhippari
Copy link
Contributor

The lack of alignment between the buttons and the cover is annoying :/

I could see the card only having the Play button, but being larger, then have the two small icons aligned to the bottom of the card.... but then the card is big enough to have the buttons on it directly.

Either way, the card needs to be bigger 😋

@ferferga
Copy link
Member Author

ferferga commented Feb 1, 2021

Page still needs a huge responsive pass, but after your comments I also tried to keep this somewhat responsive:

Desktop

image

Mobile
image

@heyhippari
Copy link
Contributor

Page still needs a huge responsive pass

We should probably merge #616 before this, then, so we can adjust it properly with the few changes I made in there (I adjusted album title size based on size, among other things)

@ThibaultNocchi
Copy link
Member

@ferferga I'd left align everything under the "Albums" label at the same level as it :)

@ferferga
Copy link
Member Author

ferferga commented Feb 11, 2021

Final design:

Mobile (As in Spotify, in mobile design the tracklist isn't shown. One can see the tracklist by clicking on an specific album)

image

Desktop

image

@codecov-io
Copy link

codecov-io commented Feb 11, 2021

Codecov Report

Merging #645 (0491004) into master (9b0e179) will not change coverage.
The diff coverage is 0.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #645   +/-   ##
=======================================
  Coverage   11.99%   11.99%           
=======================================
  Files         134      134           
  Lines        3534     3534           
  Branches      527      527           
=======================================
  Hits          424      424           
  Misses       3087     3087           
  Partials       23       23           
Impacted Files Coverage Δ
components/Item/Card/Card.vue 0.00% <0.00%> (ø)
pages/artist/_itemId/index.vue 0.00% <ø> (ø)
components/Buttons/UserButton.vue 0.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9b0e179...0491004. Read the comment docs.

@ferferga ferferga force-pushed the artists-improvements branch 2 times, most recently from 49b498f to 0491004 Compare February 11, 2021 13:52
@camc314
Copy link
Contributor

camc314 commented Feb 11, 2021

Wouldn't it be better (like spotify) to have a grid of album covers, at the moment they look a bit too big imo.

@neopc10
Copy link

neopc10 commented Feb 11, 2021

Would also like to have a means of sorting these albums by year, or better yet, have an ascending sort by year as a default!

@ferferga
Copy link
Member Author

@camc314 This is what I mean in Spotify. You mean like this but with smaller covers right?

Screenshot_20210211_145610_com.spotify.music.jpg

@neopc10 I don't think this is the place to do so. You can already do that in library view. You will usually want to check albums in a recent > oldest fashion

@camc314
Copy link
Contributor

camc314 commented Feb 11, 2021

Actually, It looks like Spotify doesn't do that.

What I was thinking of was using the item Grid on mobile devices, that way we could fit 2/3 widthwise.

@ferferga
Copy link
Member Author

@camc314 Can you post an screenshot of what you mean please?

For reference, this is the latest version of Spotify in Android, I don't know if in iOS it's different as I don't use any iOS device, but I'm aware there are some subtle differences in the way the layout is organised.

@camc314
Copy link
Contributor

camc314 commented Feb 11, 2021

Spotify doesn't actually do what I thought for artist pages. I though it had an area like this

image

It's just a thought, I don't mind what we decide to do

.gitignore Outdated Show resolved Hide resolved
@@ -120,10 +120,10 @@ export default Vue.extend({
return false;
}
},
overlay: {
noOverlay: {
Copy link
Contributor

@camc314 camc314 Feb 11, 2021

Choose a reason for hiding this comment

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

I would prefer we leave it as overlay and set the default to false, although I can do that in a separate PR

Copy link
Member Author

Choose a reason for hiding this comment

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

We're switching most of the props (see #592 (comment))

Copy link
Contributor

@camc314 camc314 Feb 11, 2021

Choose a reason for hiding this comment

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

I don't quite understand, The comment, on 592 is what I'm saying? Let me know if that's wrong.

Copy link
Member Author

Choose a reason for hiding this comment

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

MrTimscampi says that, if a property is not specified, it's false by default. Before, we were defaulting overlay to true and, for disabling it, we needed to pass it like :overlay="false", which is counter-intuitive.

Other props in card also follow the approach this prop will follow now: they are like noX and setting them means they're false, no need to do the :overlay="false" thing anymore, just no-overlay when using the component.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah I didn't notice that all the others were noX, imho, like vuetify does, we should prefer the other method (instead of noOverlay have overlay). Since we do this elsewhere we can leave for now. Thoughts @ThibaultNocchi

Copy link
Member

@ThibaultNocchi ThibaultNocchi Feb 11, 2021

Choose a reason for hiding this comment

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

I think Cam is just saying to keep the property as overlay even though it is at false by default (which I agree should be)

Edit: yeah what you said Cam ^^

Copy link
Contributor

Choose a reason for hiding this comment

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

So we will leave as is for now, and refactor later. @ThibaultNocchi one last approval before merge?

@ferferga
Copy link
Member Author

@camc314 Oh I see what you mean now. That one isn't bad either. We already have the same layout in the library browsing pages and this makes me push towards the "row" design so there's a bit of differentiation. I don't mind either though, both are great ways to present the content tbh.

Thoughts @ThibaultNocchi ?

Copy link
Contributor

@camc314 camc314 left a comment

Choose a reason for hiding this comment

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

Few comments, rest looks fine to me.

@neopc10
Copy link

neopc10 commented Feb 11, 2021

@neopc10 I don't think this is the place to do so. You can already do that in library view. You will usually want to check albums in a recent > oldest fashion

That's cool with a small library but isn't exactly practical with a large one.

This forces a ton of scrolling to see any relevant results for artists you have more than one album for. For example, I have something like 50 Elvis albums. The most recent is a 2019 compilation of his 1967 concerts, which has 8 discs. I'm looking for a 1950 album. That means I'm scrolling for quite some time before I finally get there.

With most other streamers, the albums are presented in a horizontal scroller with the tracks obviously not expanded, so there's far less work involved.

Since the excessive vertical scrolling is forced here, having the ability to sort would at least allow you to choose from wihch end you want to start scrolling.

@ThibaultNocchi
Copy link
Member

@ferferga Yeah I like Cam's idea, having a grid of covers with only their name and year could be great. We don't have to duplicate the track listing as the album is only a click away, and we can still add a whole album to the queue in a click.

I also agree with neopc's idea about being able to sort them on the artist page, but I'd leave that as an idea for later and just get this first view of the artist page.

@camc314
Copy link
Contributor

camc314 commented Feb 11, 2021

Shall we leave it as is for now, and merge, and then refactor over the next few weeks to use the grid?

@Perseusdehond
Copy link
Contributor

I like both the grid view and a list view. Maybe an option in settings in the future? But I like it either way

@sonarcloud
Copy link

sonarcloud bot commented Feb 11, 2021

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@ThibaultNocchi
Copy link
Member

LGTM, but we'll really need to do the responsive pass on this page :p

@camc314 camc314 merged commit eb3e66a into master Feb 11, 2021
@camc314 camc314 deleted the artists-improvements branch February 11, 2021 14:50
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.

None yet

8 participants