Changelist as custom scope?


Sometimes I would like to have a custom scope that shows the files that are
part of an existing changelist.
I imagine I could select a changelist from the "Changes" view, and have an
context menu action "Show as custom scope".

However, I don't know of a clean way to delete such a scope later. A context
menu inside the scopes drowdown seems not to be a very clean UI.

Any ideas/comments?
(this seems somewhat related to the recent Mylar comments)

-tt


23 comments
Comment actions Permalink

+1 (although I would probably suggest that scopes be automatically maintained as changelists are created and destroyed, rather than requiring user intervention).

--Dave Griffith

0
Comment actions Permalink

+1 (although I would probably suggest that scopes be automatically
maintained as changelists are created and destroyed, rather than
requiring user intervention).


That makes sense.

I was thinking of the situation where I create a custom scope from a changeset,
and afterwards decide that I want to work on something else.
In such a case I might want to remove an unnecessary custom scope from the
dropdown list. But I guess I could do that using the "Edit Scopes" button
in the project tree.

-tt


0
Comment actions Permalink

Hello Dave,

+1 (although I would probably suggest that scopes be automatically
maintained as changelists are created and destroyed, rather than
requiring user intervention).


JIRA request for this please? (Indeed, the scopes for changelists should
be available automatically, with no user interaction required.)

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


0
Comment actions Permalink

Hello Dmitry,

JIRA request for this please? (Indeed, the scopes for changelists
should be available automatically, with no user interaction required.)


I will create one today. But first some more discussion :)

Questions:
-Should "changelist scopes" be created automatically, or on demand?
-Should "Unversioned files" (pseudo)changelist be available as well?
-Are there other changelist related features that are related to this request?
(I think it does not make sense for "Commited" changes)
-Other ideas...?

-tt


0
Comment actions Permalink

Hello Taras,

Do you want to have additional scopes in Scope View? Or just use that scope
for Find Usages? Because for Analyze actions those scopes are already available
...

Thank you

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

Sometimes I would like to have a custom scope that shows the files
that are
part of an existing changelist.
I imagine I could select a changelist from the "Changes" view, and
have an
context menu action "Show as custom scope".
However, I don't know of a clean way to delete such a scope later. A
context menu inside the scopes drowdown seems not to be a very clean
UI.

Any ideas/comments?
(this seems somewhat related to the recent Mylar comments)
-tt





0
Comment actions Permalink

Hello Anna,

Do you want to have additional scopes in Scope View? Or just use that
scope for Find Usages? Because for Analyze actions those scopes are
already available ...


Yes, I want those scopes in Scope View. Let me explain why:
Usually I'm working on a few bugs/issues at a time. I create a separate changelist
for each one, but sometimes I collect multiple small issues in one change
list.

Having this in scope view allows for more focused navigation and overview
of what I'm working on.
At the moment I sometimes use favorites feature to create such an "issue
oriented" scope.

-tt


0
Comment actions Permalink

Hello Taras,

I see your points ;)

For sure they must be added automatically.

I don't think that unversioned files should be added (it can be a lot of
files which may led to performance issues without any benifit?)

Why not use favorites view? Scopes view assumes that you can influence on
what files you monitor by some pattern. There is no such a pattern here.
Just a suggestion though ...

And we think that we need to unify all kinds of scopes we have

Thank you

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

Hello Dmitry,

>> JIRA request for this please? (Indeed, the scopes for changelists
>> should be available automatically, with no user interaction
>> required.)
>>

I will create one today. But first some more discussion :)

Questions:
-Should "changelist scopes" be created automatically, or on demand?
-Should "Unversioned files" (pseudo)changelist be available as well?
-Are there other changelist related features that are related to this
request?
(I think it does not make sense for "Commited" changes)
-Other ideas...?
-tt



0
Comment actions Permalink

Hello Anna,

I don't think that unversioned files should be added (it can be a lot
of files which may led to performance issues without any benifit?)


I agree: "Unversioned Files" scope does not make sense.


Why not use favorites view? Scopes view assumes that you can influence
on what files you monitor by some pattern. There is no such a pattern
here. Just a suggestion though ...

And we think that we need to unify all kinds of scopes we have


In that case I propose to make it work like this (project view dropdown):

-Project
-Packages
-Scope
---Project
---Production
---Tests
---Problems
-Favorites
---myfav1
---myfav2
-Changelists (perhaps "Changes")
---changelist1
---changelist2

Does that make sense?

Regards,
Taras


0
Comment actions Permalink

Hello Taras,

Looks like current toolwindow Changes on the place of Project View ;)

What actions would you like to use?

Thank you

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

Hello Anna,

>> I don't think that unversioned files should be added (it can be a lot
>> of files which may led to performance issues without any benifit?)
>>

I agree: "Unversioned Files" scope does not make sense.

>> Why not use favorites view? Scopes view assumes that you can
>> influence on what files you monitor by some pattern. There is no such
>> a pattern here. Just a suggestion though ...
>>
>> And we think that we need to unify all kinds of scopes we have
>>

In that case I propose to make it work like this (project view
dropdown):

-Project
-Packages
-Scope
---Project
---Production
---Tests
---Problems
-Favorites
---myfav1
---myfav2
-Changelists (perhaps "Changes")
---changelist1
---changelist2
Does that make sense?

Regards,
Taras



0
Comment actions Permalink

Hello Anna,

Looks like current toolwindow Changes on the place of Project View ;)


Yes, but with package structure included (I think?)

What actions would you like to use?


I do not understand the question :) Could you describe in more detail?

-tt


0
Comment actions Permalink

Hello Taras,

>> Looks like current toolwindow Changes on the place of Project View ;)
>>

Yes, but with package structure included (I think?)


You can enable "Group by directory" in Changes view as well.

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


0
Comment actions Permalink

Hello Taras,

I want to clarify the difference with current Changes View and I assumed
that you want to use additional actions (not just grouping which is already
exist)?

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

Hello Anna,

>> Looks like current toolwindow Changes on the place of Project View ;)
>>

Yes, but with package structure included (I think?)

>> What actions would you like to use?
>>

I do not understand the question :) Could you describe in more
detail?

-tt



0
Comment actions Permalink

In a perfect world, there would also be a "current changelist" scope. By selecting "current changelist" in the project view, when you change changelists (e.g., via the excellent ChangesBar plugin) the files visible in the project view would change as well, giving a nice Mylar-ish effect.

BTW, the ability to filter analyses by changelist is extremely well hidden. I've written analysis plugins and I didn't even know it was there. I suggest changing "Uncommitted files" wording to "Changelist".

--Dave Griffith

0
Comment actions Permalink

Neat. May I humbly suggest that that should be the default? I was always annoyed by the flat layout, and had no idea it was changeable.

--Dave Griffith

0
Comment actions Permalink

Hello Anna,

Here is a quick paint mockup of how I imagine things to look.

-tt



Attachment(s):
test.png
0
Comment actions Permalink

Hello Anna,

What do you think about the mockup screenshot?
Is it what you had in mind or are there differences?

Regards,
-tt


0
Comment actions Permalink

Hello Taras,

It's ok but I do not see new functionality here :(

Group by packages is available in changes toolwindow. We do not understand
why do you need additional view ... How do you want to operate with it?

Thank you.

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

Hello Anna,

What do you think about the mockup screenshot?
Is it what you had in mind or are there differences?
Regards,
-tt



0
Comment actions Permalink

Anna,

To understand where we're going here, I think you need to examine the Mylar project for Eclipse. The core idea is that the IDE should help you maintain mental state as you switch between tasks. To that end, it implements a concept of "Contexts", which are basically sets of files you were interested in for a given task. Contexts are maintained automatically, and switching between tasks switches the IDE back to the context visible at the time the task was last used. There are a bunch of actions you can do with contexts (store them, share them, tie them to task tracking issues, search/analyze over them), but most of the value of Mylar can be gotten without that.

IDEA doesn't have contexts. It has favorites (no auto-update) and changelists (auto-update, cleaned on commit/remote run, only contains modified files rather than visited or open files) both of which are kind of close to being contexts, but not quite.

Basically where Taras and I are going is that changelists could be extended slightly, allowing their interaction with the project panel to be more context-like. The project panel is the main task "entry point", and there's a lot of value in making it context aware. The change list panel, while both essential and very nice, will never serve the same "entry point" need.

--Dave Griffith

0
Comment actions Permalink

I think I understand what you're saying.

But isn't restricting the project view contents to only the files modified in a given context somewhat too restrictive ?

Wouldn't it be more appropriate to have for example the files not being part of the changelist grayed out (but still visible) ?

0
Comment actions Permalink

Or collapsed. IDEA could then periodically collapse out items that weren't in the context.

--Dave Griffith

0
Comment actions Permalink

I guess my Point is it should not become a pain to find a file you've modified yet (but you want to look at and/or modify)

0
Comment actions Permalink

Hello Dmitry,

Hello Dave,

>> +1 (although I would probably suggest that scopes be automatically
>> maintained as changelists are created and destroyed, rather than
>> requiring user intervention).
>>

JIRA request for this please? (Indeed, the scopes for changelists
should be available automatically, with no user interaction required.)


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


0

Please sign in to leave a comment.