How are albumHeigth and albumWidth ...

This question is answered. Helpful answers available: 0. Correct answers available: 1.

Reply to this Thread

Search Forum

Back to Thread List

Replies: 18 - Pages: 2 [ Previous | 1 2 ] - Last Post: 21-Aug-2017 08:47 Last Post By: Laza

jGromit

Posts: 7,756
Registered: 31-Jan-2006

Re: How are albumHeigth and albumWidth calculated?
Posted: 05-Aug-2017 21:20

in response to: AndreWolff

AndreWolff wrote:
Well you did test it on the small screen of a mobile Phone.

But I thought that's what everyone was using to look at photo albums these days. I seem to recall someone saying that, right here in these forums. He was convinced that no one was using large desktop monitors for anything any longer, and that designing things to look good on big displays was pointless.

jGromit

Posts: 7,756
Registered: 31-Jan-2006

Re: How are albumHeigth and albumWidth calculated?
Posted: 05-Aug-2017 21:27

in response to: AndreWolff

Screenshot_20170805-152315.png (299.0 KB)

AndreWolff wrote:
...now it looks Ok even on a Phone in portrait mode, see enclosed screenshot.

Looks much the same on Android (ss). But you actually think that looks OK? Really?

AndreWolff

Posts: 1,863
Registered: 14-Dec-2007

Re: How are albumHeigth and albumWidth calculated?
Posted: 06-Aug-2017 08:44

in response to: jGromit

jGromit wrote:
He was convinced that no one was using large desktop monitors for anything any longer, and that designing things to look good on big displays was pointless.

Nonsense, I never said that!

I only said that the mobile platform will become much more important as the PC platform, so jAlbum should concentrate develeopments for that type of devices, see here.

Laza

Posts: 2,339
Registered: 6-Sep-2005

Re: How are albumHeigth and albumWidth calculated?
Posted: 21-Aug-2017 08:47

in response to: AndreWolff

In my opinion anything bigger than 300x300px shouldn't be put in an IFRAME, anymore. Google also shares this opinion as far as I know, and their SERPS engine (search engine rankings position) takes iframes into account too. It was simply a wrong idea, that could make sense in the time when the average monitor size got bigger every year, but not today. I tried "responsive embedding" too, but that didn't took device orientation into account. So no way of getting rid of those usability issues introduced by embedding a user interface into another.

Pages: 2 [ Previous | 1 2 ]

Back to Thread List

Legend
	Forum admins
	Helpful Answer
	Correct Answer