| commit | 6537dcb8a8f696254a8b335e596146a24e210b5b | |
| author | Marek Zawirski <marek.zawirski@gmail.com> | |
| Sun, 17 Aug 2008 20:44:12 +0000 (17 22:44 +0200) | ||
| committer | Robin Rosenberg <robin.rosenberg@dewire.com> | |
| Thu, 21 Aug 2008 21:45:16 +0000 (21 23:45 +0200) | ||
| tree | 296385ed49d098b08718592dad0c856e55f4b528 | treesnapshot (tar.gz zip) |
| parent | 9575533b4c258a69415f8db264a82d7af9e352a6 | commitdiff |
Push GUI
Push operation in GUI is implemented as wizard consisting of 3 pages:
-repository selection
-ref specifications selection
-confirmation page with dry run results (optional - can be skipped)
Wizard finish-action starts Job with PushOperation. Dialog with results
is shown when job ends. It can be configured to be displayed only if
results change since confirmation.
With confirmation page, it is possible to perform 2-stage push, allowing
user to preview updates and mark them to be performed only if
advertised refs don't change.
Eventually, results Dialog can be replaced with Result/Transport view
some day, as this idea arose recently.
Signed-off-by: Marek Zawirski <marek.zawirski@gmail.com>
[Ed. amended follow up patches]
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
Push operation in GUI is implemented as wizard consisting of 3 pages:
-repository selection
-ref specifications selection
-confirmation page with dry run results (optional - can be skipped)
Wizard finish-action starts Job with PushOperation. Dialog with results
is shown when job ends. It can be configured to be displayed only if
results change since confirmation.
With confirmation page, it is possible to perform 2-stage push, allowing
user to preview updates and mark them to be performed only if
advertised refs don't change.
Eventually, results Dialog can be replaced with Result/Transport view
some day, as this idea arose recently.
Signed-off-by: Marek Zawirski <marek.zawirski@gmail.com>
[Ed. amended follow up patches]
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>