Merge lp:~thisfred/u1db/cosas-conflict-resolution into lp:u1db
Status: | Merged |
---|---|
Approved by: | Eric Casteleijn |
Approved revision: | 375 |
Merged at revision: | 373 |
Proposed branch: | lp:~thisfred/u1db/cosas-conflict-resolution |
Merge into: | lp:u1db |
Prerequisite: | lp:~thisfred/u1db/its-full-of-conflicts |
Diff against target: |
451 lines (+253/-62) 3 files modified
cosas/conflicts.ui (+139/-0) cosas/cosas.ui (+6/-1) cosas/ui.py (+108/-61) |
To merge this branch: | bzr merge lp:~thisfred/u1db/cosas-conflict-resolution |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Roberto Alsina (community) | Approve | ||
Review via email: mp+119193@code.launchpad.net |
Commit message
- added UI for conflict resolution
Description of the change
- added UI for conflict resolution
NOTE: right now the only way to resolve a conflicted task is to select it and hit enter. I'd like to have clicking the item do the same thing, but I couldn't figure that out, please advise.
How to test:
PYTHONPATH=. python cosas/ui.py
[ create some tasks if you don't already have any, close the program ]
mv ~/.local/
PYTHONPATH=. python cosas/ui.py
[ open sync dialog, sync with ~/.local/
mv ~/.local/
mv ~/.local/
PYTHONPATH=. python cosas/ui.py
[ edit the same tasks but to have different text and/or done status, open sync dialog, sync with ~/.local/
you should now see conflicts (text is reddish, exclamation point on the right hand side)
Clicking the item should emit the currentItemChanged signal and/or the itemClicked signal.
I agree that is a better interaction, so holding until we can try to figure that out on monday.