Debug console configuration

Hello all,

Is there a way to change the debug console to the "classic" configuration?
I find that the new way takes to much space on the screen.

Thansk

21 comments
Comment actions Permalink

Hello Shaul,

Is there a way to change the debug console to the "classic"
configuration? I find that the new way takes to much space on the
screen.


Do you know that you can collapse any of the panes by double-clicking its
title?

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


0
Comment actions Permalink

Well, personally I don't like the new debug console at all. It would be great to at least have the option to switch to the classic one.

0
Comment actions Permalink

+1

Well, personally I don't like the new debug console at all. It would
be great to at least have the option to switch to the classic one.



0
Comment actions Permalink

Yes, I noticed this option, but I still like the option to revert back to the old style.

0
Comment actions Permalink

Debug panel must be more configurable. I still think that pin different tabs of it to different sides of screen would be great.

And of course it must persist it's state between debug sessions. But I think it would be done anyway.

0
Comment actions Permalink

Which debugger views do you usually use? What kind of space are you
disappointed with?

Thanks,

On 2007-03-22 14:59:10 +0300, Shaul <shaul.kushelevsky@corp.idt.net> said:

Hello all,

Is there a way to change the debug console to the "classic" configuration?
I find that the new way takes to much space on the screen.

Thansk



--
Kirill Kalishev
JetBrains, Inc.
http://jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

(As for me...)

1. Console. Logging is main debug thing.
2. After Console - Variables and Threads.

Best layout, that I can imagine - console to bottom and variables to the right/left side. Threads can be as a drop-down or below/above variables.

In old layout all the views were in the same place. Now, when I need to open horizontal console and vertical variables - they use many space. That's because I need the console to be the same size, as it was in "old" layout. So, variables take additional space (totally they take up to 2 times more space) compared to "old layout".

When we've "wide" laptop screen, it is really bad.

0
Comment actions Permalink

Does detaching/maximizing of views help you in any way?

On 2007-03-26 20:43:20 +0400, Alexander Babaev <no_reply@jetbrains.com> said:

(As for me...)

1. Console. Logging is main debug thing.
2. After Console - Variables and Threads.

Best layout, that I can imagine - console to bottom and variables to
the right/left side. Threads can be as a drop-down or below/above
variables.

In old layout all the views were in the same place. Now, when I need to
open horizontal console and vertical variables - they use many space.
That's because I need the console to be the same size, as it was in
"old" layout. So, variables take additional space (totally they take up
to 2 times more space) compared to "old layout".

When we've "wide" laptop screen, it is really bad.



--
Kirill Kalishev
JetBrains, Inc.
http://jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Sure it helps. And view detaching helps a bit. But when I need/want to monitor both console/variables and source code - it looks bad.

Variables - is a vertical view. There are often many of them. And they take little place horizontally. And console is often - horizontal type of view.

0
Comment actions Permalink

Kirill,

During program execution I mainly use the console view. But as soon as
program execution is interrupted, I use the frames, variables, and
sometimes the watches view. I almost never look at the console view
while program execution is interrupted.

So my favorite layout would be to have the frames, variables, and
watches views in one tab and the console view in another tab. (I think
one of the very early Selena builds had it this way - it was great!)

Oh well, and I hate those tabs! They look ugly and waste a lot of
vertical space. E.g. the console view looses almost two lines of useful
information only because of the tab and one single toolbar button (which
in fact isn't related to the console view at all).

I would prefer to have those nice tiny title bars back and the toolbar
buttons on the left side of the respective view. Would save a lot of
vertical space.

- Martin

Kirill Kalishev wrote:

Which debugger views do you usually use? What kind of space are you
disappointed with?

Thanks,

On 2007-03-22 14:59:10 +0300, Shaul <shaul.kushelevsky@corp.idt.net> said:

>> Hello all,
>>
>> Is there a way to change the debug console to the "classic"
>> configuration?
>> I find that the new way takes to much space on the screen.
>>
>> Thansk



--
Martin Fuhrer
Fuhrer Engineering AG
http://www.fuhrer.com

0
Comment actions Permalink

>So my favorite layout would be to have the frames, variables, and
>watches views in one tab and the console view in another tab. (I think
>one of the very early Selena builds had it this way - it was great!)

+1

0
Comment actions Permalink

I think that, after trying all the new ideas out, on balance I agree...

I would have one extra request though - could the tab that the console
is moved on to flash or something if it detects an exception is dumped
to the console and the Frames/Variables/Watches view is focused?

Another idea would be for the tabs to auto switch to console during run,
and F/V/W view when interrupted; this would obviously be overridden in
the case where you manually switched to console view upon interruption
(e.g. you might be watching console output when stepping)

N.

Martin Fuhrer wrote:

Kirill,

During program execution I mainly use the console view. But as soon as
program execution is interrupted, I use the frames, variables, and
sometimes the watches view. I almost never look at the console view
while program execution is interrupted.

So my favorite layout would be to have the frames, variables, and
watches views in one tab and the console view in another tab. (I think
one of the very early Selena builds had it this way - it was great!)

Oh well, and I hate those tabs! They look ugly and waste a lot of
vertical space. E.g. the console view looses almost two lines of useful
information only because of the tab and one single toolbar button (which
in fact isn't related to the console view at all).

I would prefer to have those nice tiny title bars back and the toolbar
buttons on the left side of the respective view. Would save a lot of
vertical space.

- Martin

Kirill Kalishev wrote:

>> Which debugger views do you usually use? What kind of space are you
>> disappointed with?
>>
>> Thanks,
>>
>> On 2007-03-22 14:59:10 +0300, Shaul <shaul.kushelevsky@corp.idt.net>
>> said:
>>
>>> Hello all,
>>>
>>> Is there a way to change the debug console to the "classic"
>>> configuration?
>>> I find that the new way takes to much space on the screen.
>>>
>>> Thansk
>>
>>

0
Comment actions Permalink

For me, the best solution imaginable would be for IDEA to come up with something like the tool window management in MS Visual Studio: Make all constituents of the debug tool window stackable / tilable / detachable in any combination whatsoever. (And keep the "full screen" mode.)

Regards,
Jens

P.S.: That can't be too hard, can it?

0
Comment actions Permalink

This is a tough question. We try to avoid interface mess as much as
possible. Giving too much options produces mess. Reducing number of
options impacts ability to customize things. We want to find a good
balance between these two things.

We definitely don't want to go the Eclipse way (so far), where almost
every piece of UI can be docked everywhere. A reasonable option is to
provide some freedom "locally" yet keeping things consistent. Like the
new debugger does (or just started to do). It's much difficult task in
terms of UI design but we believe it's worth it.

On 2007-03-27 15:42:49 +0400, Jens Voss <no_reply@jetbrains.com> said:

For me, the best solution imaginable would be for IDEA to come up with
something like the tool window management in MS Visual Studio: Make all
constituents of the debug tool window stackable / tilable / detachable
in any combination whatsoever. (And keep the "full screen" mode.)

Regards,
Jens

P.S.: That can't be too hard, can it?



--
Kirill Kalishev
JetBrains, Inc.
http://jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

I can't agree with that. Debugging is a very personal thing. It's not needed very much during self-code debugging but "sometimes" we are to debug other programmer's code. And in this situation all debugging information helps.

You already have many (many) tool windows, that can be snapped/moved/pinned around workspace. Why can't you create one (just one) more? I don't think, that it would be a mess. Idea is a tool, that is extremely customizable. We can customize everything … except debug tool window. I don't think that it is correct.

I like Idea because it just works. And if I need, I can change behaviour to do it my way. But debugging is messy now in several situations, when I debug, for example, to find out, how something works.

0
Comment actions Permalink

That was response to the original post about "any window that can be
stackable/tilable/detachable". IDEA is not "extremely" customizable in
that sense.

On 2007-03-27 18:45:06 +0400, Alexander Babaev <no_reply@jetbrains.com> said:

I can't agree with that. Debugging is a very personal thing. It's not
needed very much during self-code debugging but "sometimes" we are to
debug other programmer's code. And in this situation all debugging
information helps.

You already have many (many) tool windows, that can be
snapped/moved/pinned around workspace. Why can't you create one (just
one) more? I don't think, that it would be a mess. Idea is a tool, that
is extremely customizable. We can customize everything ??¦ except debug
tool window. I don't think that it is correct.

I like Idea because it just works. And if I need, I can change
behaviour to do it my way. But debugging is messy now in several
situations, when I debug, for example, to find out, how something works.



--
Kirill Kalishev
JetBrains, Inc.
http://jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

At the moment I have
Frames########Variables#########Watches
Console################################

Is it not possible to join those two tab levels into one so that I end up with?
Console##Frames####Variables####Watches

Or just dock the console and frames (or some other combination) together like this?
Console####################Frames#####

0
Comment actions Permalink

We are investigating how to do this best, thanks for feedback. You will
see improvements very soon.

Just curious on how you work with console: do you intend always to be
aware of anything put to the console view? Is it why you want console
to be docked that way?

On 2007-04-19 20:30:12 +0400, opticyclic <no_reply@jetbrains.com> said:

At the moment I have
Frames########Variables#########Watches
Console################################

Is it not possible to join those two tab levels into one so that I end up with?
Console##Frames####Variables####Watches

Or just dock the console and frames (or some other combination)
together like this?
Console####################Frames#####



--
Kirill Kalishev
JetBrains, Inc.
http://jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Its because I have lots of log statements so I want to be able to see quite of few of them at the same time, as well as being able to see the others (frame/watches etc).
If the console could be docked with the others like this
Console####################Frames#####
you get twice as much vertical space as by doing it in its current implementation.

0

Please sign in to leave a comment.