Merge lp:~thumper/launchpad/use-last-rev-id into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Tim Penhey on 2010-02-26 |
| Approved revision: | not available |
| Merged at revision: | not available |
| Proposed branch: | lp:~thumper/launchpad/use-last-rev-id |
| Merge into: | lp:launchpad |
| Diff against target: |
411 lines (+138/-43) 8 files modified
lib/canonical/launchpad/javascript/code/branchmergeproposal.js (+81/-8) lib/lp/code/browser/branchmergeproposal.py (+1/-0) lib/lp/code/doc/branch-merge-proposals.txt (+4/-5) lib/lp/code/interfaces/branchmergeproposal.py (+5/-5) lib/lp/code/model/branchmergeproposal.py (+5/-2) lib/lp/code/stories/webservice/xx-branchmergeproposal.txt (+7/-7) lib/lp/code/templates/branchmergeproposal-pagelet-summary.pt (+27/-13) lib/lp/code/windmill/tests/test_branchmergeproposal_commitmessage.py (+8/-3) |
| To merge this branch: | bzr merge lp:~thumper/launchpad/use-last-rev-id |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michael Nelson (community) | ui | 2010-02-25 | Approve on 2010-02-25 |
| Paul Hummer (community) | code js ui* | 2010-02-24 | Approve on 2010-02-24 |
|
Review via email:
|
|||
Commit Message
Send through the last scanned id when approving a merge proposal and update the table asynchronously.
| Tim Penhey (thumper) wrote : | # |
| Tim Penhey (thumper) wrote : | # |
Changed the windmill test to use the approved value and check for the approved revision id.
| Paul Hummer (rockstar) wrote : | # |
Think adding a few comments to the insertion code would be helpful. When I look at the patch, I know what the javascript is doing because I see the tal changes as well. Seeing the javascript by itself might be a little confusing (it is a bit hairy, but clever).
| Tim Penhey (thumper) wrote : | # |
http://
| Michael Nelson (michael.nelson) wrote : | # |
> Need to find a good way to test this.
Heh, a script to setup the environment that you demo'd would be great. I just created an MP for ~name12/
UI-wise, it works really well, updating the display with the extra row when necessary. I laughed in your video near the end where you go to update the version number, but then hesitate and stop the video... made me click it ;). So I assume that'll get done later... do you think it's worth doing it before landing this branch? The non-js fallback works fine, but it does seem strange that it doesn't bring up an overlay and update inline. Up to you.
Now, nothing to do with a UI review, but I wrote a DynamicDomUpdater a while back for this *type* of thing - basically it allows you to plug-in the functionality so that a node (for example, a table node) knows how to update itself. YMMV, but you can find it at:
lib/canonical/
tested at:
lib/canonical/
Cheers,
Michael.
| Tim Penhey (thumper) wrote : | # |
Setting the merged revision id has always behaved like that. I hesitated because it wasn't want I was wanting to demonstrate :) I'll take a look at the dynamic dom updater at some stage.

Need to find a good way to test this.