This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 82840 - Show History: filtering is clumsy, no info about branches in revision list
Summary: Show History: filtering is clumsy, no info about branches in revision list
Status: NEW
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: CVS (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@versioncontrol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-16 22:01 UTC by Pavel Buzek
Modified: 2012-12-24 19:15 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Buzek 2006-08-16 22:01:05 UTC
It is pretty hard to find the latest version on a specific branch in Show
History window. In fact the only way to guess about branches (AFAICT) is by
longer version numbers which is not very nice. Maybe the list of all revisions
should be organized as a tree showing the branches more clearly. Then I would
also hopefullu be able to collaps revisions on a branch which I do not care
about. Or I could have a choice between a tree and list, like in email client I
can view list or threads of email.

The search on top of the page can be used to filter branches but it takes a
while to find and get used to. It would be more usable (for me) if branches were
part of the revision list.

As for the filters: see how thunderbird or netscape does it. You type a String
and the list is filtered by this string -- both in subject, sender, etc. - i.e.
full text search, everything that contains the entered text. One input line for
the filter is enough. You save a lota UI space. If I want to find all revisions
looking for 'pbuzek' it will 99% cases find the ones that I committed. If I
happen to have a branch called pbuzek or a comment containing 'pbuzek' I won't
mind seeing it in the result. Same if I am searching for branch name, issue
number in comment, etc. The point is to make it fast and easy to limit the list
of revisions to a reasonable amount, not to enter a complex query and get
precise results.
Comment 1 Maros Sandor 2006-09-08 14:08:48 UTC
You can switch to the Diff view which is tree-like with visible branch points,
does it not work for you? (we are still missing branch and tag names there,
though, see Issue #66138)

The quick filter is a good idea, Jano? We can put it just above the results view.
Comment 2 jrojcek 2006-10-10 10:30:34 UTC
I like the quickfilter idea. The question is how to combine it with with the search fields so that it's not like 
- you first specify the search criteria and then use filtering. This might be confusing.

During designing the seach history we also considered an option to have just one search field which would 
work like a google search. You can type a string and you can also type special instructions like "from: 
<something>". This is not really a filtering, but somewhat similar.