Changes toolwindow

Very nice (indeed, nicer than the equivalent window in TMate). However, it needs to be available some way other than through the through the "Windows/Tool Windows..." submenu. It's bad enough that some less frequently needed windows are only available that way (Ant, TODO), but Changes is going to be used a lot more often. I would suggest a menu item under version control. I'll submit a JIRA.

(No, of course I don't have my workspace ringed with toolwindow buttons. Who has enough screen real-estate to waste it like that?)

--Dave Griffith

22 comments

Hello Dave,

Are you aware of quicklists rule for this usecase? Create new quicklists
and drop most frequently used toolwindows from Window|Toolwindows menu there
and assign a single shortcut.

I agree Changes should have better default availability though.

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

A few things that I've noticed while using it this morning:

1. When I start expanding the folders in the Changes window while it's updating (it says "Updating C:\my\project\directory\src\etc" just above the treeview), the folders are randomly collapsed. Either don't collapse them while updating or prevent the tree from being used while updating.

2. The sorting seems to be random.

3. When grouping changes by directory and module, there are no buttons to expand or collapse all folders, although Keypad-* seems to work (what's the keybinding for collapse all?).

Ciao,
Gordon

0

Hello Gordon,

Thanks, these will be fixed in next EAP.

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Another side effect of this change in the method of committing is that
the cvs server output toolwindow now shows a command for every file
rather than every module. I used to be able to construct a commit
report for our bug tracker pretty quickly by chopping out the command
sections of the server output, and being left with a revision
modification list for all the files involved. Now it's very difficult,
slow and tedious to do this, and so I'm going back to 5162 to commit.
But obviously I am concerned about the future here - will it always be
like this?
Are there any plans for functionality to provide a commit report after
commit that can be logged into an issue tracker?

N.

0

Just a few more things...

When I have files selected in the Changes window, creating a new changelist should automatically move the selected files into the new changelist, or give an option to do so (whose setting is remembered).

This is a minor quibble, but the tooltip for the Commit button says "Commit selected changelists" but selecting multiple changelists disables the button. It's either one or the other ;)

Ciao,
Gordon

0

Hello Gordon,

move the selected files into the new changelist

F6 (move) will do approximately the same. It gives you an ability to create
new changelist to move selected changes to.

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

I discovered this after I created the new changelist expecting it to move the file I had selected into the new changelist. I'm just saying that it didn't behave how I initially expected it to. I think it's more intuitive to "create a new changelist with these selected files" than to "move these selected files into a new changelist". Subtle, I know, but there's no reason why you can't make it work both ways.

Ciao,
Gordon

0

Topic hijacked - but somewhat related.

Something I've wanted for awhile now is the ability to only commit
"part" of a class, or file.

Say I'm working on some refactoring and hit a small typo bug in an
SQL/HQL somewhere thats affecting/holding up some testing.

I don't want to commit the whole file as I'm not currently done with my
refactoring. So I'd like to move the "small change" into its own change
set which could be committed independently of the rest of the file.

Am I the only one to want this crazy idea?

Mark




Gordon Tyler wrote on 03/03/06 10:32:

I discovered this after I created the new changelist expecting it to
move the file I had selected into the new changelist. I'm just saying
that it didn't behave how I initially expected it to. I think it's
more intuitive to "create a new changelist with these selected files"
than to "move these selected files into a new changelist". Subtle, I
know, but there's no reason why you can't make it work both ways.

Ciao, Gordon

0

Not that straitforward but something to support this workflow is planned: http://www.jetbrains.net/jira/browse/IDEADEV-4727

0

Maxim Shafirov wrote on 03/03/06 13:29:

Not that straitforward but something to support this workflow is
planned: http://www.jetbrains.net/jira/browse/IDEADEV-4727


Voted and watched - I'm sure you guys will come up with something
that'll work well...

0

I guess I missed something: what is this "quicklists" business?

BoD


Maxim Shafirov (JetBrains) a écrit :

Hello Dave,

Are you aware of quicklists rule for this usecase? Create new quicklists
and drop most frequently used toolwindows from Window|Toolwindows menu
there and assign a single shortcut.

I agree Changes should have better default availability though.

------------------
Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Hello BoD,

Go to Settings|Keymaps
Make sure you're not using a default one. Create your own if not done yet.

There's a quicklists section on the top right. Create one and fill with favorite
actions that do not have shortcuts assigned themselves.
Now you have entry for the quicklist under quicklists node in keymap editor
itself. Assign a shortcut to it.
Voi la.

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Am I the only one who thinks this should be another option in the
Project pulldown next to Project, Packages, etc, instead of a new
toolwindow?

Dave Griffith wrote:

Very nice (indeed, nicer than the equivalent window in TMate). However, it needs to be available some way other than through the through the "Windows/Tool Windows..." submenu. It's bad enough that some less frequently needed windows are only available that way (Ant, TODO), but Changes is going to be used a lot more often. I would suggest a menu item under version control. I'll submit a JIRA.

(No, of course I don't have my workspace ringed with toolwindow buttons. Who has enough screen real-estate to waste it like that?)

--Dave Griffith

0

Hello Keith,

Available (and meaningful) actions effectively vary between changes and project
view, that's why they should not be merged.

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Maxim Shafirov (JetBrains) wrote on 07/03/06 04:50:

Available (and meaningful) actions effectively vary between changes and
project view, that's why they should not be merged.


How about "in addition too" - having a changes filter along with
project/packages/scope could be handy.

0

Some more feedback...

In my project, I have part of my build directory included in the module paths because my ant build generates source files that I want IDEA to know about.

However, the Changes window shows these in the Unversioned Files list but those files and their containing directories will never be under version control.

I know this is a somewhat unusual situation, but is there anything that can be done about this?

Ciao,
Gordon

0

Hello Gordon,

What version control you're using?

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Hello Gordon,

CVS.

So you have a viable workaround for this. Just add those directories to .cvsignore
file.

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

I would be using .cvsignore if I could, but neither the directory containing the generated source files nor any of its ancestor directories are under CVS control. The build directory is parallel to the CVS controlled src directory.

Perhaps some ascii art:



Ciao,
Gordon

0

Hello Gordon,

Huh, it seems we're to implement our own ignore list then. A JIRA item please?

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

http://www.jetbrains.net/jira/browse/IDEA-7052.

In that, I've described a possible solution where one is able to mark "Generated Sources" in the Module Paths, which are like Sources or Test Sources but would be ignored by version control.

0

Please sign in to leave a comment.