Merge lp:~allenap/launchpad/sub-search-ui-bug-656823-2-devel into lp:launchpad
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Approved by: | Gavin Panella on 2010-11-04 | ||||
| Approved revision: | no longer in the source branch. | ||||
| Merged at revision: | 11884 | ||||
| Proposed branch: | lp:~allenap/launchpad/sub-search-ui-bug-656823-2-devel | ||||
| Merge into: | lp:launchpad | ||||
| Diff against target: |
335 lines (+213/-22) 5 files modified
lib/lp/registry/browser/configure.zcml (+6/-0) lib/lp/registry/browser/person.py (+86/-17) lib/lp/registry/stories/person/xx-person-subscriptions.txt (+60/-1) lib/lp/registry/templates/person-structural-subscriptions.pt (+48/-0) lib/lp/registry/templates/person-subscriptions.pt (+13/-4) |
||||
| To merge this branch: | bzr merge lp:~allenap/launchpad/sub-search-ui-bug-656823-2-devel | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Paul Hummer (community) | ui | 2010-11-04 | Approve on 2010-11-04 |
| Graham Binns (community) | code | 2010-11-04 | Approve on 2010-11-04 |
|
Review via email:
|
|||
Commit Message
New view, +structural-
Description of the Change
This adds a new view for IPerson, registered as
+structural-
user has subscribed. This matches a similar page called +subscriptions
(which is live, but not linked to from anywhere) which shows direct
subscriptions (bugs only so far).
I didn't put this information on the +subscriptions page because that
has a batch navigator over the direct subscriptions. I've found having
a static data set on the same page as batched information to be
confusing in the past.
Instead each page links to the other using an info link at the
top. This looks okay, but there's probably a better way of doing it.
The structural subscriptions are shown in a list, not in tabular form,
because they will be extended later to include subordinate
information, namely bug subscription filters. There can be multiple
filters for each structural subscription. Nested lists seem to be an
obvious way to represent this.
Screenshots:
http://
http://

This looks good to me. I generally don't like pages that are just listings, but we already have a story for them. You might want to consider a javascripty inline solution for showing these listings on the main page.