Some Browse Changes feedback.

The Browse Changes improvements in Selena are pretty good. Very natural
to have this functionality as part of the Changes Tool Window. However,
some further changes would make it even better:

1. The menu item for this very top-level functionality now seems buried
in the main menu. I think it should be somewhere at the same level as
the Create Patch and Shelve Changes functionality.
It would also be great if there was a way to invoke Browse Changes from
the Changes tool window.

2. In Demetra I used to place the Changes tool window on the left. File
trees look better with more vertical space than horizontal, in my
opinion. In Selena this is no longer an option, because the browse
changes layout needs lots of horizontal space. It would be great if the
layout could adjust to side placement of the Changes tool window. The
Changed Files panel would then be placed below the Changes table and
comment field.

3. Browse Changes needs a scope selector.
Currently it uses the selected item as scope (I think). Every time I
invoke it, I wonder where my changes have gone. After a few seconds I
realize I am looking at the changes for a single file, instead of the
entire project.
In Demetra it defaulted to the entire project, if I remember correctly.
This was more usable, but it actually needs a way to change the scope
from the Specify Search Criteria dialog. Similar to "Analyze > Inspect
Code..." and "Find in Path..."

4. The Specify Search Criteria dialog also needs to remember the
settings from the previous invocation. I often want to specify very
similar settings for a new search. Changing the values of the previous
invocation would be faster.

5. Loading the changes in the background, so I can work while waiting
for the results would be very desirable. But I assume this is already
planned.

If any of these requests needs JIRA's let me know.

Bas

5 comments
Comment actions Permalink

Without getting into much detail, I beg to disagree. The Browse Changes panel is still very, very far from actually being useful. It still lacks decent filtering, grouping, automatic updating, caching of information… sounds familiar? Yep, that's TMate.

When I heard TMate was withdrawn from the market (and the last version doesn't work with Selena anyway), I really believed JetBrains was bringing TMate functionality into the core product, changing internals, maybe, but keeping must of the user interface. It seems I was wrong, pity.

0
Comment actions Permalink

As I understand it, integrating Tmate still needs to be done.
Anyway, my post was about Browse Changes, a functionality hidden in IDEA
for several versions, not about TMate. Personally I am not very familiar
with TMate because it leaked so much memory that I could not use it and
do useful work at the same time. Perhaps you could describe some of its
functionality in this thread so I know what I am missing? Or maybe you
can point to some JIRA requests?

Bas

Marcus Brito wrote:

Without getting into much detail, I beg to disagree. The Browse
Changes panel is still very, very far from actually being useful. It
still lacks decent filtering, grouping, automatic updating, caching
of information… sounds familiar? Yep, that's TMate.

When I heard TMate was withdrawn from the market (and the last
version doesn't work with Selena anyway), I really believed JetBrains
was bringing TMate functionality into the core product, changing
internals, maybe, but keeping must of the user interface. It seems I
was wrong, pity.

0
Comment actions Permalink

Hello Marcus,

Without getting into much detail, I beg to disagree. The Browse
Changes panel is still very, very far from actually being useful. It
still lacks decent filtering, grouping, automatic updating, caching of
information… sounds familiar? Yep, that's TMate.

When I heard TMate was withdrawn from the market (and the last version
doesn't work with Selena anyway), I really believed JetBrains was
bringing TMate functionality into the core product, changing
internals, maybe, but keeping must of the user interface. It seems I
was wrong, pity.


Please don't jump to advance conclusions. There's still lots of time remaining
before the Selena release, and we do plan to implement filtering, grouping,
automatic updating and caching of information in the Browse Changes panel.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Please don't jump to advance conclusions. There's
still lots of time remaining
before the Selena release, and we do plan to
implement filtering, grouping,
automatic updating and caching of information in the
Browse Changes panel.


Oh, I know. Sorry if it sounded otherwise. I was just venting about the apparently gratuitous change in user interface — TMate used to get this right. This was just my way of saying "nicely done, guys, now I'm looking forward to the rest of it" :)

0
Comment actions Permalink

Perhaps you could describe some of its
functionality in this thread so I know what I am
missing? Or maybe you
can point to some JIRA requests?


Not sure about Jira requests, but here are a few things I liked about TMate:

? Repository history was fetched and analyzed only once, and automatically. TMate stored everything on a local server. I know this is planned for Browse Changes as well.
? Many ways to visualize your repository history. I could group changesets by author, date or path, and filter by any of these criteria. The UI for that was nice and intuitive.
? Read/Unread changesets. When you're working as an integrator/reviewer, it's great to know which changsets you've already seen and which of them are new.
? Pending updates. You could see changesets available at the server that will be integrated the next time you run an update. This was a nice way to prevent conflicts before they actually happen.
? Simple but effective bug tracking integration. You could define a regex and a substitution URL, and TMate would replace every match with a link to your bug tracking system.

These are from the top of my mind. Somehow TMate just felt right.

0

Please sign in to leave a comment.