Critical update? ... - jAlbum forums

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

Reply to this Thread

Search Forum

Back to Thread List

Replies: 6 - Pages: 1 - Last Post: 28 May 26, 18:30 Last Post By: JeffTucker

JeffTucker

Posts: 8,490
Registered: 31-Jan-2006

Critical update?
Posted: 26 May 26, 23:10

So, just got a "critical update," which took me from 39.5.6 to 39.5.11. David, would you like to share? What are you doing?

davidekholm

Posts: 3,999
Registered: 18-Oct-2002

Re: Critical update?
Posted: 28 May 26, 08:48

in response to: JeffTucker

Sorry for not keeping you guys in the loop. Here are the changes (minor stuff):

Now better handles images mangled by TagThatPhoto (lost GPS coordinates)
Single index page skins like Embed will now never be limited by rows setting
Fixed issue with duplicate folders generated when renaming a folder (since 39.5)
Fixed UI freeze issue caused by folder property panel
Uncompiled skins can now also have icons (path relative to skin directory)

JeffTucker

Posts: 8,490
Registered: 31-Jan-2006

Re: Critical update?
Posted: 28 May 26, 14:59

in response to: davidekholm

davidekholm wrote:
Single index page skins like Embed will now never be limited by rows setting

For years, most of my skins have been handling that with a one-liner in init.groovy:

engine.setRows(0);

Is there now a preferred method?

Uncompiled skins....

Those must be for use with intepreted jAlbum. It's slow, but users can make their own changes easily.

But seriously, there are only four of those. Two of them are totally obsolete, and one is sadly neglected. Adding a new one to the list seems perverse.

RobM

Posts: 4,045
Registered: 4-Aug-2006

Re: Critical update?
Posted: 28 May 26, 18:01

in response to: JeffTucker

JeffTucker wrote:
For years, most of my skins have been handling that with a one-liner in init.groovy:

engine.setRows(0);

Is there now a preferred method?

The API now has for skin properties SINGLE_INDEX_PAGE (since version 33)
But in my opinion that will only lead to user confusion, ‘I set it to this but get this?’ Disabling the control is much more elegant.

davidekholm

Posts: 3,999
Registered: 18-Oct-2002

Re: Critical update?
Posted: 28 May 26, 18:10

in response to: RobM

If both rows and columns are irrelevant, set the SINGLE_INDEX_PAGE skin property.

RobM

Posts: 4,045
Registered: 4-Aug-2006

Re: Critical update?
Posted: 28 May 26, 18:28

in response to: davidekholm

davidekholm wrote:
If both rows and columns are irrelevant, set the SINGLE_INDEX_PAGE skin property.

Sorry, I don’t like having controls left active but ineffective, it just feels wrong. I’d much rather have them disabled outright.

JeffTucker

Posts: 8,490
Registered: 31-Jan-2006

Re: Critical update?
Posted: 28 May 26, 18:30

in response to: davidekholm

For the best UX, I think the best combo is:

enableThumbnailLayout=false
singleIndexPage=true

And then you don't need to do anything further in init.groovy.

So, the user can't get to the settings at all, and it doesn't matter if they've been saved at some archaic rows/cols layout values.

BTW, I love that the API provides the skin properties settings in one format, e.g., SINGLE_INDEX_PAGE, but the skin.properties file requires them as, e.g., singleIndexFile. This is why we love API's.

Pages: 1

Back to Thread List

Legend
	Forum admins
	Helpful Answer
	Correct Answer