Merge lp://staging/~jtv/launchpad/bug-418430-stuff-to-review-3.0 into lp://staging/launchpad

= Bug 418430 =

For members of translation groups, the 3.0 personal page shows a list of
translations that await their review. If relevant, it also links to the
full list on a page called +translations-to-review.

When I started creating that page, we did not have the 3.0 macros yet so
I created it in 2.0 style. This branch fixes that. It's an easy change
since there's so little on the page.

Also, I'm adding +translations-to-review to the navigation menu for a
person in Translations. On the +translations-to-review page this shows
up as a list of related pages, since there's nothing else of interest to
show in a sidebar.

One bump in the road was getting the related-pages: I need to get
context/@@+related-pages rather than view/@@+related-pages. I don't
know why that is, but things fail horribly otherwise. I've seen sinzui
add constructors that distinguish between cases where "context" is the
view and cases where it's the underlying model object, but since in this
case there are other pages using the same navigation menu, it seemed
irresponsible to make the same change here without understanding all the
ramifications.

For testing, run the existing Translations pagetests. The only one
affected by the change was the licensing test, which unnecessarily
matches the entire navigation menu.

For Q/A:
 * Visit the home page for someone who is not in any translation groups.
   The navigation menu has no link for translations to review.
 * Visit the home page for someone who is in a translation group. Now
   the link will show up.
 * Follow that link and see the new page. It shows any translations
   awaiting review by this person, and the equivalent of the navigation
   menu at the bottom of the page.
 * Cycle through all the pages in the navigation menu, to make sure that
   I haven't broken any.

Naturally I've done this on the testing branch as well.

No lint.

Jeroen

Hi, Jeroen.

This looks nice!

One note about the UI, when I looked at the page itself, the two
headings -- the person name heading in an h2 and the page title in an
h1 -- were in the same purple color used for translations currently.
As I understand it, these should be light gray and green respectively.
I assume there's some current 2.0 LP style rule making all headings
this color for translations. The same is true of the bugs app, I
know. So I just call your attention to it, if you're not already
aware. Nothing to fix now, but at some point it has to be changed.
Maybe you guys have already talked about this, but just in case not, I
mention it.

I see only one minor fix to recommend:

> + <div class="top-portlet">
> + <h1>Translations to review</h1>
> + <tal:work-to-do condition="view/num_projects_and_packages_to_review">
> + <p>
> + These translations are available to be reviewed by
> + <tal:person replace="structure context/fmt:link">R. Viewer</tal:person>:
> + </p>

The h1 of the page should match the page title. In the case of the
page I sampled, the page title was "Translations for review by
Launchpad German translators" so I would expect the main h1 to be that
as well.

Otherwise, this looks good. Marking this as approved, with the
assumption that this one change will be made.

Cheers,
deryck

> The h1 of the page should match the page title. In the case of the
> page I sampled, the page title was "Translations for review by
> Launchpad German translators" so I would expect the main h1 to be that
> as well.
>
> Otherwise, this looks good. Marking this as approved, with the
> assumption that this one change will be made.

Consider it done, for verily it is.

Jeroen

> One note about the UI, when I looked at the page itself, the two
> headings -- the person name heading in an h2 and the page title in an
> h1 -- were in the same purple color used for translations currently.
> As I understand it, these should be light gray and green respectively.
> I assume there's some current 2.0 LP style rule making all headings
> this color for translations. The same is true of the bugs app, I
> know. So I just call your attention to it, if you're not already
> aware. Nothing to fix now, but at some point it has to be changed.
> Maybe you guys have already talked about this, but just in case not, I
> mention it.
>

So I made a bit of mistake here. I was thinking about the rule that the h2 should be gray, and blanked out for a minute that green is the registry color. So the h2 should be gray, and currently the h1 the app-specific color. I'm just updating the MP to admit my mistake if someone comes along later.

I did talk to beuno about this. And he does have some desire to have a single h1 color across apps. But that is a separate issue.

I filed bug 418666 about needing to have the context.title headings be gray across all app-specific pages.

Cheers,
deryck