quncommit: ideas about better UI

Bug #416361 reported by Alexander Belchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QBzr
Confirmed
Low
Unassigned

Bug Description

[13:31] <bialix> igc: question about quncommit
[13:32] <igc> hi bialix
[13:32] <bialix> hi igc, I have some time to look at quncoomit
[13:32] <bialix> it looks better now
[13:32] <bialix> igc: I just wonder about terms, like tip
[13:33] <bialix> igc: why you're using idiom "move tip to"?
[13:33] <igc> bialix: would you prefer another name like "head"?
[13:33] <bialix> igc: this is not blocks me from merge, but if you have couple of minutes, I'd better ask
[13:34] <bialix> igc: no, I mean why we talk about moving tip and not about uncommit actually?
[13:34] <bialix> igc: e.g. we can show revision details under first radiobutton
[13:35] <bialix> and put the label for radiobutton: Uncommit last revision:
[13:35] <bialix> igc: actually I have troubles to correctly translate tip, and it does not seem bzr uses "tip" term internally or in the docs
[13:36] <igc> bialix: firstly, I think 'tip' is fine ...
[13:36] <igc> from core-concepts in the User Guide: The last revision is known as the *tip*
[13:36] <bialix> igc: ok, I did not know this
[13:37] <bialix> so I can translate tip as "last revision"?
[13:37] <igc> bialix: yes
[13:37] <bialix> I understand that "tip" is short and nice word in English
[13:37] <bialix> as many others: pull and push
[13:37] <igc> bialix: also, we need to display what revisions will be removed anyhow so there seems limited benefit in displaying that in advance
[13:38] <igc> bialix: I thought pretty hard about that and ...
[13:38] <bialix> it so nice to be Englishman and speak in so wonderful language
[13:38] <igc> I've been through several designs on paper over the last few months thinking about quncommit
[13:38] <bialix> igc: what if I want uncommit 100 last revisions?
[13:39] <bialix> what I'll see in confirmation dialog then?
[13:39] <igc> bialix: we'll display those just like the CLI does
[13:39] <igc> bialix: that would be very unusual, of course
[13:39] <bialix> on CLI any long info go out of my console
[13:40] <bialix> this becomes problem for GUI
[13:40] <igc> bialix: 99% of the time it's just one revision - to fix the commit message, bug metadata, etc :-)
[13:40] <bialix> you just can't have an infinite tall dialog, do you? ;-)
[13:40] <bialix> igc: so if this is 99% cases, why not show ther details right in the quncommit window?
[13:40] <igc> bialix: I guess we could use a scrolling panel or the qlog widget
[13:41] <igc> bialix: I'm ok with doing that
[13:41] <igc> bialix: I just don't think it's mandatory
[13:41] <igc> to land this
[13:41] <bialix> igc: no of course.
[13:41] <bialix> igc: +1 on land the last version
[13:42] <igc> bialix: thanks. Did you want to merge it or I?
[13:42] <bialix> igc: I'm just want to discuss with you how it could be improved, especially re better UI for translations to other languages
[13:42] <bialix> igc: if you can, merge n push it yourself
[13:42] <igc> bialix: no problem. I do think it can be improved
[13:42] <igc> bialix: but that can come later
[13:43] <bialix> yes, of course
[13:43] <bialix> but later I forgot what I'm thinking right now

[13:44] <bialix> igc: can we just dump this discussion about quncommit to new bug report?
[13:44] <bialix> so I don't forget about it later?
[13:44] <igc> bialix: sure...

Changed in qbzr:
status: New → Confirmed
Changed in qbzr:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.