Merge lp://staging/~bryce/launchpad/lp-586150-whiteboard-widening into lp://staging/launchpad

Proposed by Bryce Harrington
Status: Merged
Approved by: Curtis Hovey
Approved revision: no longer in the source branch.
Merged at revision: 10962
Proposed branch: lp://staging/~bryce/launchpad/lp-586150-whiteboard-widening
Merge into: lp://staging/launchpad
Diff against target: 119 lines (+34/-38)
4 files modified
lib/canonical/launchpad/icing/style-3-0.css.in (+6/-0)
lib/canonical/launchpad/icing/style.css (+0/-4)
lib/lp/blueprints/templates/specification-index.pt (+27/-33)
lib/lp/soyuz/templates/archive-macros.pt (+1/-1)
To merge this branch: bzr merge lp://staging/~bryce/launchpad/lp-586150-whiteboard-widening
Reviewer Review Type Date Requested Status
Curtis Hovey (community) Approve
Canonical Launchpad Engineering Pending
Review via email: mp+26265@code.staging.launchpad.net

Description of the change

Gives additional horizontal space for the whiteboard section.

The Ubuntu project makes heavy use of the whiteboard for coordinating development tasks. Launchpad's stylesheet wraps lines to make prose read better. However with todo lists this tends to not work out as well. This change provides a bit more horizontal space, which makes the Ubuntu blueprint work item lists read a lot nicer.

To post a comment you must log in.
Revision history for this message
Curtis Hovey (sinzui) wrote :

> === modified file 'lib/canonical/launchpad/icing/style-3-0.css.in'
> --- lib/canonical/launchpad/icing/style-3-0.css.in 2010-05-17 10:56:27 +0000
> +++ lib/canonical/launchpad/icing/style-3-0.css.in 2010-05-28 03:48:33 +0000
> @@ -409,6 +409,10 @@
> /* Keep the abilty to hide list entries. */
> display: none;
> }
> +div.widetext p {
> + max-width: 60em;
> + margin-bottom: 1.0em;
> + }

This is a very narrow definition makes this an exception for the blueprint
white board. It cannot will not be resued. If we really want an exception for
*just* the blueprint whiteboard, this then belongs in the page's
head-epilogue slot.

This rule needs to accommodate the kinds of markup and circumstances that
happen in many places in Launchpad to be included in the global CSS. I think
we need this rule, so the selector must be generalised.

I think .wide will suffice since we have a .narrow. I should be permitted to
use this with a table or a form. lists that should be the same width as the
paragraphs they are with so div and p are too specific

/me looks at other wide cases.
    table#package-requests {
        width: 60em;
        margin: 1em 0;
        }

Score! Well we have found a common rule that blueprints and soyuz can used

I think the rule should be:
.wide {
    max-width: 60em;
    margin: 1em 0;
    }

Update your file and lib/lp/soyuz/templates/archive-macros.pt
    <table id="package-requests" class="wide listing"

And we can remove one more dead rule from style.css.

review: Approve (code ui)
Revision history for this message
Bryce Harrington (bryce) wrote :

I tried this bug it did not work:

.wide {
    max-width: 60em;
    margin: 1em 0;
    }

However if I change it to this, it does work:

.wide p {
    max-width: 60em;
    margin: 1em 0;
    }

I'm not sure where in Launchpad the package-requests table appears, so haven't been able to test how either of these CSS settings affect it. I've poked around the PPA pages where it looks like it should appear but can't seem to locate it, is there some trick to make that portlet show up?

Revision history for this message
Bryce Harrington (bryce) wrote :

Also, isn't 'max-width' a p-specific markup tag? Is that going to apply to tables with the same effect as 'width'?

Revision history for this message
Curtis Hovey (sinzui) wrote :

No, but ultimately your point is valid. max-width is for block elements, inline elements and table elements are ignored (display: inline and display:table respectively). In my defence, it was way past my bed time when I did that review; I should have waiting till morning when the caffeine had taken affect. We need to refine the rule so that we have the same semantics to provide comprable effect.

.wide * {
    max-width: 60em;
    margin: 1em 0;
    }
table.wide {
    max: 60em;
    margin: 1em 0;
    }

Revision history for this message
Bryce Harrington (bryce) wrote :

Okay, that looks more sensible.

However I notice the * has a curious effect on the whiteboard layout... see this screenshot:

  http://launchpadlibrarian.net/49280819/whiteboard-margin-increase.png

Revision history for this message
Curtis Hovey (sinzui) wrote :

Is that the correct screen cap? I do not see an whiteboard on the merge proposal page.

Revision history for this message
Bryce Harrington (bryce) wrote :

I kinda like how it looks with a bit of extra space between the lines... makes the text less harsh and dense. But the above is a bit too much. Cutting down to 0.5em looks more like I think it should.

OTOH if it's going to have weird side effects, maybe leaving the margin untweaked would be safest?

Revision history for this message
Bryce Harrington (bryce) wrote :

Oh and I notice you said 'max: 60em' but shouldn't that be 'width: 60em'? (I still haven't found where this particular table shows up so haven't been able to test it).

Anyway, with the above caveats I've pushed an update.

Revision history for this message
Curtis Hovey (sinzui) wrote :

Yes. you are correct about width 60em

The image does not show the whiteboard. I can image eveyything looks double-spaced since every wide element has 1em before and after it. We already have margin rules for elements, so I think we can drop the .wide * margin rule. This will let the default rules work. If you need to force an 1em between the whiteboard and the line in the page, hack it into the template.

Revision history for this message
Bryce Harrington (bryce) wrote :

> The image does not show the whiteboard.

Hmm, weird. Try again:
  http://launchpadlibrarian.net/49285310/whiteboard-doublespace.png

Here's how it looks with the current state of the branch (with the .wide * margin rules dropped):
  http://launchpadlibrarian.net/49285335/whiteboard-no-margin-tweaks.png

I think this looks fine, the CSS seems sane, and am happy to call it done if you are. Is there a need for anyone else to review this or shall I call it done and plan to land it once PQM has reopened?

Revision history for this message
Curtis Hovey (sinzui) wrote :

Let's call this done then. You can land it next week wne PQM opens.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.