Announce: Material Skin

[mherger]

Did you bump the version number in install.xml and update the repository file?

[cpd73]

Did you bump the version number in install.xml and update the repository file?

Oops! Forgot to commit those changes! Bad idea to make a release late a night... Should be fixed now.

[mherger]

Announce: Material Skin

> Oops! Forgot to commit those changes! Bad idea to make a release late a
> night... Should be fixed now.

Better late than never - happens to me all the time :-)

Great release, thanks a lot!

--

Michael

[mherger]

Announce: Material Skin

Two artwork related comments:

- you're using 300x300_o for the grid. If you used 300x300_f instead,
you'd share the server side image render cache with iPeng, which might
speed up page loading and save some disk space

- the artwork in the playlist panel is not being resized on the server.
It's always downloaded full size. I have some in the 2000x2000px range -
which can make rendering that list pretty slow. The same applies for
"slideshow" items: though only shown in the grid 300x300, pictures are
downloaded full size.
--

Michael

[cpd73]

Two artwork related comments:

- you're using 300x300_o for the grid. If you used 300x300_f instead,
you'd share the server side image render cache with iPeng, which might
speed up page loading and save some disk space

OK, I tried the various variants and saw no real difference - well some added white bars, buts that's not what I wanted. None seemed to crop to a square (checked via loading URL into a browser), so I added some CSS to do this.

I'll update the code to use 50x50_f for the lists (and play queue), and 300x300_f for the grid.

- the artwork in the playlist panel is not being resized on the server.
It's always downloaded full size. I have some in the 2000x2000px range -
which can make rendering that list pretty slow. The same applies for
"slideshow" items: though only shown in the grid 300x300, pictures are
downloaded full size.

But slideshow should show full size pictures, so that you can zoom in.
[EDIT] Replied too soon. I see what you mean, the grid contains the full size images! Will fix.

[cpd73]

Two artwork related comments:

- you're using 300x300_o for the grid. If you used 300x300_f instead,
you'd share the server side image render cache with iPeng, which might
speed up page loading and save some disk space

http://localhost:9000/imageproxy/mai/artist/870/image_100x100_c

http://localhost:9000/imageproxy/mai/artist/870/image_100x100_f

http://localhost:9000/imageproxy/mai/artist/870/image_100x100_o

All return exactly the same image - same dimensions, and same md5sums.

[mherger]

Announce: Material Skin

> I'll update the code to use 50x50_f for the lists (and play queue), and
> 300x300_f for the grid.

Pre-cached versions are:
50x50_o
100x100_o
300x300_f (if using iPeng)

The sizes are rendered at scan time, therefore don't need much
processing when the page is loaded. Other sizes would only be processed
when called.

I think some of the options (o vs. f) only are still there for
compatibility reasons... even if the result is the same, it's preferable
to use the same parameters in order to take advantage of the caching.

> But slideshow should show full size pictures, so that you can zoom in.

Hmm... didn't see this here (desktop). It was using the same layout as
the grid.

--

Michael

[cpd73]

> I'll update the code to use 50x50_f for the lists (and play queue), and
> 300x300_f for the grid.

Pre-cached versions are:
50x50_o
100x100_o
300x300_f (if using iPeng)

The sizes are rendered at scan time, therefore don't need much
processing when the page is loaded. Other sizes would only be processed
when called.

I think some of the options (o vs. f) only are still there for
compatibility reasons... even if the result is the same, it's preferable
to use the same parameters in order to take advantage of the caching.

Ah, OK. Will use the same parameters as well then.

> But slideshow should show full size pictures, so that you can zoom in.

Hmm... didn't see this here (desktop). It was using the same layout as
the grid.

No, I meant when you click on an image it start the full screen viewer.

[Shozzer]

Looking good so far, thanks very much. Some great improvements this release! Will continue to play and report back. I am in an IT conference all day and Material should prove a great distraction if things get a little tedious here!

[d6jg]

Looking great now

Tiny tiny issue on both Desktop and Mobile

This is a track coming from Spotify with no Year tag - I don't think there is actually a zero in the stream / tag anywhere

[d6jg]

The grid view on desktop is excellet but one improvement suggestion in relation to long album titles

Would it be possible to add a tooltip that gives the whole album title ?

Here I have a number of versions of DSOTM - they are actually all slightly different but the only way of telling which is which is to either open the album itself or switch away from grid view. A tootltip would assist here.

[cpd73]

The grid view on desktop is excellet but one improvement suggestion in relation to long album titles

Would it be possible to add a tooltip that gives the whole album title ?

Yup, but which would be better; tooltip, or us multiple lines for title?

[d6jg]

Yup, but which would be better; tooltip, or us multiple lines for title?

Not sure.
Instictively I thought multiple lines would be better but the font you are using is quite large so might create a weird gappy layout which is why I said tooltips.
Canvas some other opinion on the subject

[Wigster]

Hi,

Another thing I have noticed is that I can't skip forward/backward within the track: then I drap the progress indicator blob on the desktop, it goes back to its initial position. On mobile, it ends up switching views from now playing to browse. Material 0.1.1 with MS Edge on Desktop (it works perfectly fine otherwise on it) and Safari on Mobile.

[slartibartfast]

Hi,

Another thing I have noticed is that I can't skip forward/backward within the track: then I drap the progress indicator blob on the desktop, it goes back to its initial position. On mobile, it ends up switching views from now playing to browse. Material 0.1.1 with MS Edge on Desktop (it works perfectly fine otherwise on it) and Safari on Mobile.

On the mobile if you just tap the track progress bar at the desired position rather than dragging the blob then it works.

Sent from my SM-G900F using Tapatalk