* Fwd: qgit 2.1 questions about range selection
[not found] ` <e5bfff550712310352j3245511chbbd301d35e09204b@mail.gmail.com>
@ 2007-12-31 11:53 ` Marco Costalba
0 siblings, 0 replies; 3+ messages in thread
From: Marco Costalba @ 2007-12-31 11:53 UTC (permalink / raw)
To: Git Mailing List
---------- Forwarded message ----------
From: Marco Costalba <mcostalba@gmail.com>
Date: Dec 31, 2007 12:52 PM
Subject: Re: qgit 2.1 questions about range selection
To: Steffen Prohaska <prohaska@zib.de>
On Dec 31, 2007 11:42 AM, Steffen Prohaska <prohaska@zib.de> wrote:
> Hello Marco,
Hi Steffen,
I hope you don't mind if I forward this also to the git list.
Your questions are interesting, and I think could be useful also for
other people.
>
> Here is a first impressions and some questions about the range
> selection, which I find pretty hard to understand.
>
> - The "Range select" dialog.
> * It is displayed upon startup or when I open a new
> repository. But I haven't found a way to access "Range
> select" from the menus. I'd expected to find it as
> "View > Range select".
Currently the only way is to open (with File->open or "open folder"
the tool button or with File->last opened repos list ) again the
_same_ repository. I understand is not the best way. Your suggestion
"View->range select" it seems a better idea.
> * The dialog's "Top:" and "Bottom:" drop downs apparently contain
> tags or "HEAD". Why can't I select a specific branch? I'd
> expected this here, too.
You can write anything you want in top and bottom fields, they are not
read-only, so you can write a branch name or anything understandable
by 'git log'. You can also clear one filed, as example the bottom
field to have all the revisions until the initial one.
> * The dialog's "Top:" and "Bottom:" fields are reset to a
> default each time the dialog opens. Why aren't the last settings
> preserved?
Mmmmm, why not? this goes in the same playfield of "View->Range select", thanks.
> * I find the toggles "Working dir" hard to understand. Why
> not always showing the working dir? Why not displaying
> differences to the index (as gitk does with the "green"
> commit)?
Well differences in the index _are_ displayed with an "orange" commit
(from a long time ago also, much more then gitk BTW). The reason is
not selected by default is that on big repos, as Linux, checking for
working dir changed files takes very long and is not useful for people
that just wants to pull Linux and take a look atthe updates. Anyhow
you can always toggle this directly right clicking anywhere in the
main revision list. A pop up menu appears and "Check for modified
files" is the first entry.
> * Similar for the toggles "All branches", "Whole history".
> Maybe "All branches" could be included in the "Top:" drop down
> and "Whole history" could be included in the "Bottom:" drop down.
>
There should be some tooltips that help here. But again Top and Bottom
are only range delimiters, what happens is that if you write A in the
top field and B in the bottom field git log is called with : git log
A..B
> - The parameters of the current range selection are not obvious.
> After closing the "Range select" dialog the history is
> displayed. But where can I see the parameters of the
> selection? I'd have expected to see an indication which
> branches, tags, whole history, ... I selected. Indications
> of this are scattered over the GUI. For example, a filter can
> be toggled on in the tool menu bar and is greyed out if
> activated. Or "FILTER ON" may be displayed in the window
> title.
>
Well there is already a "Filter ON" but is for a more advanced feature
then range select. Simply, from main list, press key 't' to show tree
view, then select some files/directories (multi selection is allowed),
then press the magic wand toolbar button: that's the FILTER ON (and
you see on the window caption BTW)
> - "Toggle filter by tree" seems to switch to "--all". I see
> more commits than I expect. I'd have expected that this
> toggle adds a boolean "and" to the selection; that is the
> current view would be restricted to commits touching the
> selected path.
>
Mmmmm, if this is the case it's a bug. Thanks I will investigate.
> Maybe the range selection could be unified in the following way.
> The selection is represented as multiple lines; each line
> representing part of the selection parameters. All lines together
> act as a boolean expression selecting the commits. Each line
> contains drop down boxes and text fields (or other GUI elements).
> The selection filter is displayed below the tool bar and the
> tab containing the "Rev list"; or it should be included in the
> "Rev list". For example, the following lines would select the
> commits on branch pu, not on master, touching file help.c
>
> - Selection: [label]
> - Branch [drop down], origin/pu [drop down],
> - Not on branch [drop down], origin/master [drop down],
> - File [drop down], help.c [text field],
>
> Each line contains "-", "+" buttons to remove this line or add a
> line below. The very first line has a button "+" to add a line
> at the very bottom. I attached a snapshot of the Mac OS X
> Smartfolder GUI to illustrate this.
>
>
That's nice!
Currently you can use the "Additional options" field at the bottom of
range select to write a free text that will be pasted directly to the
git log command line arguments.
>
>
> Btw, is the git mailing list the right forum to discuss such
> suggestions?
>
> If so, feel free to reply with CC to git@vger.kernel.org.
>
Already done ;-)
Thanks
Marco
^ permalink raw reply [flat|nested] 3+ messages in thread