A few things:

1. Tabs Med was missing a few entries' indexes because of rougue > s in the rml. Content are taking another look.
2. Finally figured out the command line parameters to imagemagick's crop command. To get the left-most 1000 pixels of an image, use

convert -crop -[image width - 1000] image out

and to get the right-most, use

convert -crop [image width - 1000] image out

The WxH+x+y notation is misleading - width and height don't correspond to the desired result of the crop. Instead you're specifying a rectangle which will be intersected with the image. The result will be the intersection. Easy once you know that. Tough when you don't!

3. Rearranged atlas panels and added padding either side ready to re-cut the tiles.
4. Big discussion coming up about sections, default behaviour, show all / show default. Notes so far are below.
5. Glastonbury ticket service need more phones.

The section problem: If you look at the Colum Enc entry on Siberia, you'll see a paragraph at the top with clickable headings below. There is no "Show full entry" link. That is the problem, below is where I think we stand:


Right then - I think this might get complicated. The tech discussion is
below, but the key thing to resolve is: what do we _want_ to happen?

Those sections are marked with s="c", ie default state=closed.

The primary effect of this is that the sections don't open up when fed a
section path of "-". They have to be given an explicit id number on the
section path to respond.

The code discounts the fact that these sections are closed when deciding
whether to show the "Show full entry" link. This is because the sfe link
just feeds in a ".-" section path, which these sections won't respond to
anyway.

If we change this behaviour then we have to have parallel notions of
"Default" and "Full" view of an entry. I think that's possible, but it
will be a source of more confusion. For example, we've already decided
that we won't display all tabs open simultaneously in a tabbed entry -
so a full view won't always be a full view.

I think the problem arises because of the way those entries are
structured. We should talk to Phil and James and see what they think. As
I understand it, the intent is to have a structure like this:

[stuff always displayed] (A)
[heading] (B)
[heading] (C)
[heading] (D)

where the headings B, C and D are clickable to display the associated
text but A is always visible.

The way the entry is structured right now, A is in the root section
and B, C and D are first-level children. We've got this s="c" to
determine the initial state of B,C and D as closed. I think this is the
root of the problem - we've put in something to override what used to be
the "show everything" section path (.-) and now we're looking at putting
in something to override the override. Going to get very messy.

If the sections were instead all peers:

[empty root section]
[stuff always displayed] (A)
[heading] (B)
[heading] (C)
[heading] (D)

Then we could have (A) as a static section (b="s"). That means it always
gets displayed open when its parent is open (ie always, as its parent
would be root). B, C and D would be normal sections - open when fed the
"-" section path, closed but heading visible when a section path is
supplied which doesn't apply to them.

T
- posted by Tim Bruce @ 11:58 AM