Give debuggers more space ... :-)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
27 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Give debuggers more space ... :-)

marcel.taeumel
Hi, all! 

May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...


Best,
Marcel


Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

Hannes Hirzel
+1

On 9/26/19, Marcel Taeumel <[hidden email]> wrote:
> Hi, all!
>
> May I add more spaces to Context >> #printOn:? ... and a "#" in front of the
> selector ...
>
>
> Best,
> Marcel

Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

Christoph Thiede
In reply to this post by marcel.taeumel

+1, provides a much better readability. Maybe we could switch to a PluggableMultiColumnListSpec here some day? :)




Best,

Christoph


Von: Squeak-dev <[hidden email]> im Auftrag von Taeumel, Marcel
Gesendet: Donnerstag, 26. September 2019 13:36:16
An: Alan Grimes via Squeak-dev
Betreff: [squeak-dev] Give debuggers more space ... :-)
 
Hi, all! 

May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...


Best,
Marcel


Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

Tobias Pape

> On 26.09.2019, at 14:11, Thiede, Christoph <[hidden email]> wrote:
>
> +1, provides a much better readability. Maybe we could switch to a PluggableMultiColumnListSpec here some day? :)
>
and make the left column flush-right

...

>
>
> Best,
> Christoph
> Von: Squeak-dev <[hidden email]> im Auftrag von Taeumel, Marcel
> Gesendet: Donnerstag, 26. September 2019 13:36:16
> An: Alan Grimes via Squeak-dev
> Betreff: [squeak-dev] Give debuggers more space ... :-)
>  
> Hi, all!
>
> May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...
>
>
>
> Best,
> Marcel



Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

Christoph Thiede

... even with support for filtering, if Christian would provide his PluggableMultiColumnListMorph implementation :)




@Tobias: TextAlignments in MultiColumns are not yet supported, are they?


Von: Squeak-dev <[hidden email]> im Auftrag von Tobias Pape <[hidden email]>
Gesendet: Donnerstag, 26. September 2019 14:14:51
An: The general-purpose Squeak developers list
Betreff: Re: [squeak-dev] Give debuggers more space ... :-)
 

> On 26.09.2019, at 14:11, Thiede, Christoph <[hidden email]> wrote:
>
> +1, provides a much better readability. Maybe we could switch to a PluggableMultiColumnListSpec here some day? :)
>
and make the left column flush-right

...

>
>
> Best,
> Christoph
> Von: Squeak-dev <[hidden email]> im Auftrag von Taeumel, Marcel
> Gesendet: Donnerstag, 26. September 2019 13:36:16
> An: Alan Grimes via Squeak-dev
> Betreff: [squeak-dev] Give debuggers more space ... :-)

> Hi, all!
>
> May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...
>
>
>
> Best,
> Marcel





Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

marcel.taeumel
Hmm... this does not work well for long class names :-)

Here is another version that looks more like our message sets:

Best,
Marcel

Am 26.09.2019 14:22:13 schrieb Thiede, Christoph <[hidden email]>:

... even with support for filtering, if Christian would provide his PluggableMultiColumnListMorph implementation :)




@Tobias: TextAlignments in MultiColumns are not yet supported, are they?


Von: Squeak-dev <[hidden email]> im Auftrag von Tobias Pape <[hidden email]>
Gesendet: Donnerstag, 26. September 2019 14:14:51
An: The general-purpose Squeak developers list
Betreff: Re: [squeak-dev] Give debuggers more space ... :-)
 

> On 26.09.2019, at 14:11, Thiede, Christoph <[hidden email]> wrote:
>
> +1, provides a much better readability. Maybe we could switch to a PluggableMultiColumnListSpec here some day? :)
>
and make the left column flush-right

...

>
>
> Best,
> Christoph
> Von: Squeak-dev <[hidden email]> im Auftrag von Taeumel, Marcel
> Gesendet: Donnerstag, 26. September 2019 13:36:16
> An: Alan Grimes via Squeak-dev
> Betreff: [squeak-dev] Give debuggers more space ... :-)

> Hi, all!
>
> May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...
>
>
>
> Best,
> Marcel





Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

Edgar J. De Cleene-3
In reply to this post by Christoph Thiede
Re: [squeak-dev] Give debuggers more space ... :-) Could we have the vars in alphabetic order ?
Edgar
@morplenauta





Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

timrowledge
In reply to this post by marcel.taeumel


> On 2019-09-26, at 5:38 AM, Marcel Taeumel <[hidden email]> wrote:
>
> Hmm... this does not work well for long class names :-)

Could we do some reasonably intelligent wrapping?
LongClassNameThatReallyOverloadsTheNotifierWidth
       > #sensibleMessageName
It would mean making the list items able to be 'multi line' for display and click handling.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Useful random insult:- Not an idiot, but plays one in his life.



Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

Nicola Mingotti
In reply to this post by marcel.taeumel
+1

seems much more readable.

bye
nicola



On 9/26/19 4:36 AM, Marcel Taeumel wrote:
Hi, all! 

May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...


Best,
Marcel


    



Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

Kjell Godo
[_]— i want to make a multi Window Debugger which really reduces the need to 
mouse or click or fiddle diddle faddle stepping . Smalltalk stepping used to be my 
favorite hobby . <Alt>+<Tab> navigation or something keyboard only Vim where it
 remembers the clicks you clicked to Inspect a couple 3 things and plays them 
back apon any revisiting => reopening and puts the desired printOn:s into a 
popUp clustering which disappears or reappears apon leaving returning each 
click setup inspection selecting -> showing its printOn: just by keeping hitting the
 <Spacebar> . maybe the separate Windows take it in turns to coming forwards 
apon <Spacebar> . mostly you just keep hitting <Spacebar> or <F10> <F11> 
something . And the source code selection always always scrolls into dead center
 of the pain oh the pane centered top to bottom of the monitor screen without me
 fiddling with these tiny Steve Jobs scroll bars which never should have replaced 
the Adele et all ST-80 scroll flaps and that old GUI is coming back it’s just called 
WUP or WUPS or WPU or UPWoo or something which has hiding scroll bars byut 
they’re ((->tiny<-)) pfff so it takes some stressing to home in on the minute buggers . give me the old interface back again but with rich text . fancy fonts etc . oh yeah o y worse is better worse is better worse is definitely better and the GUI 
should look like things we are familiar with so our heads don’t explode speaking 
no ill of the dead but he couldn’t have been more wrong no like desk drawers and 
table tops and 3D rollodecks magic cap . but the 80 GUI never did any of that 
because why because why because it was 39 years before it’s time that’s why
Adele whoooooooooooooooooooooooooooooooooooooooooooooooo hooooo

On Thu, Sep 26, 2019 at 20:17 Nicola  <[hidden email]> wrote:
+1

seems much more readable.

bye

nicola



On 9/26/19 4:36 AM, Marcel Taeumel wrote:
Hi, all! 

May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...


Best,
Marcel


    




Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

marcel.taeumel
In reply to this post by timrowledge
> Could we do some reasonably intelligent wrapping? 

I am afraid that we cannot.

Best,
Marcel

Am 26.09.2019 20:06:53 schrieb tim Rowledge <[hidden email]>:



> On 2019-09-26, at 5:38 AM, Marcel Taeumel wrote:
>
> Hmm... this does not work well for long class names :-)

Could we do some reasonably intelligent wrapping?
LongClassNameThatReallyOverloadsTheNotifierWidth
> #sensibleMessageName
It would mean making the list items able to be 'multi line' for display and click handling.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Useful random insult:- Not an idiot, but plays one in his life.





Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

Robert Hirschfeld
In reply to this post by marcel.taeumel
+1

On 26. Sep 2019, at 13:36, Marcel Taeumel <[hidden email]> wrote:

Hi, all! 

May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...

<image.png>

Best,
Marcel




Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

marcel.taeumel

Best,
Marcel

Am 28.09.2019 13:12:55 schrieb Robert Hirschfeld <[hidden email]>:

+1

On 26. Sep 2019, at 13:36, Marcel Taeumel <[hidden email]> wrote:

Hi, all! 

May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...

<image.png>

Best,
Marcel




Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

marcel.taeumel
Note that #spaceFillWeight would work, too:


Best,
Marcel

Am 16.10.2019 12:57:04 schrieb Marcel Taeumel <[hidden email]>:


Best,
Marcel

Am 28.09.2019 13:12:55 schrieb Robert Hirschfeld <[hidden email]>:

+1

On 26. Sep 2019, at 13:36, Marcel Taeumel <[hidden email]> wrote:

Hi, all! 

May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...

<image.png>

Best,
Marcel




Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

Chris Muller-3
Hi Marcel, I do like the readability of this, but how is list filtering affected?  I realized I almost always start my filter on the stack pane with ">" to filter on method names only (and not class names).  It looks like that won't be possible anymore.


On Wed, Oct 16, 2019 at 6:03 AM Marcel Taeumel <[hidden email]> wrote:
Note that #spaceFillWeight would work, too:


Best,
Marcel

Am 16.10.2019 12:57:04 schrieb Marcel Taeumel <[hidden email]>:


Best,
Marcel

Am 28.09.2019 13:12:55 schrieb Robert Hirschfeld <[hidden email]>:

+1

On 26. Sep 2019, at 13:36, Marcel Taeumel <[hidden email]> wrote:

Hi, all! 

May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...

<image.png>

Best,
Marcel





Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

Christoph Thiede

It shouldn't be a big effort to introduce a middle column with constant ">>"s in each line, should it? :)

And then we could modify the filtering to match beyond adjacent columns.


Von: Squeak-dev <[hidden email]> im Auftrag von Chris Muller <[hidden email]>
Gesendet: Mittwoch, 16. Oktober 2019 22:56:00
An: The general-purpose Squeak developers list
Betreff: Re: [squeak-dev] Give debuggers more space ... :-)
 
Hi Marcel, I do like the readability of this, but how is list filtering affected?  I realized I almost always start my filter on the stack pane with ">" to filter on method names only (and not class names).  It looks like that won't be possible anymore.


On Wed, Oct 16, 2019 at 6:03 AM Marcel Taeumel <[hidden email]> wrote:
Note that #spaceFillWeight would work, too:


Best,
Marcel

Am 16.10.2019 12:57:04 schrieb Marcel Taeumel <[hidden email]>:


Best,
Marcel

Am 28.09.2019 13:12:55 schrieb Robert Hirschfeld <[hidden email]>:

+1

On 26. Sep 2019, at 13:36, Marcel Taeumel <[hidden email]> wrote:

Hi, all! 

May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...

<image.png>

Best,
Marcel





Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

marcel.taeumel
Hmm.. First, we would have to extend the respective ToolBuilderSpecs to let models configure such columns. #hAlignment, #columnSpecs, ...maybe similar to PluggableTreeSpecs... Data provision (col-first or row-first) then is quite simple.

Yes, one could add more columns with any characters. List filtering looks in all columns (OR combination). First column front match is a front match.



On Thu, Oct 17, 2019 at 10:14 AM +0200, "Thiede, Christoph" <[hidden email]> wrote:

It shouldn't be a big effort to introduce a middle column with constant ">>"s in each line, should it? :)

And then we could modify the filtering to match beyond adjacent columns.


Von: Squeak-dev <[hidden email]> im Auftrag von Chris Muller <[hidden email]>
Gesendet: Mittwoch, 16. Oktober 2019 22:56:00
An: The general-purpose Squeak developers list
Betreff: Re: [squeak-dev] Give debuggers more space ... :-)
 
Hi Marcel, I do like the readability of this, but how is list filtering affected?  I realized I almost always start my filter on the stack pane with ">" to filter on method names only (and not class names).  It looks like that won't be possible anymore.


On Wed, Oct 16, 2019 at 6:03 AM Marcel Taeumel <[hidden email]> wrote:
Note that #spaceFillWeight would work, too:


Best,
Marcel

Am 16.10.2019 12:57:04 schrieb Marcel Taeumel <[hidden email]>:


Best,
Marcel

Am 28.09.2019 13:12:55 schrieb Robert Hirschfeld <[hidden email]>:

+1

On 26. Sep 2019, at 13:36, Marcel Taeumel <[hidden email]> wrote:

Hi, all! 

May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...

<image.png>

Best,
Marcel





Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

Jakob Reschke-2
In reply to this post by marcel.taeumel
How will it look with long class names (or two of them)?

Am Mi., 16. Okt. 2019 um 12:57 Uhr schrieb Marcel Taeumel <[hidden email]>:




Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

marcel.taeumel
In reply to this post by marcel.taeumel
Hi, all.

Please find attached a change set to play around with this layout idea in the debugger. Needs current Trunk (#19138).


Best,
Marcel

Am 17.10.2019 19:34:18 schrieb Taeumel, Marcel <[hidden email]>:

Hmm.. First, we would have to extend the respective ToolBuilderSpecs to let models configure such columns. #hAlignment, #columnSpecs, ...maybe similar to PluggableTreeSpecs... Data provision (col-first or row-first) then is quite simple.

Yes, one could add more columns with any characters. List filtering looks in all columns (OR combination). First column front match is a front match.



On Thu, Oct 17, 2019 at 10:14 AM +0200, "Thiede, Christoph" <[hidden email]> wrote:

It shouldn't be a big effort to introduce a middle column with constant ">>"s in each line, should it? :)

And then we could modify the filtering to match beyond adjacent columns.


Von: Squeak-dev <[hidden email]> im Auftrag von Chris Muller <[hidden email]>
Gesendet: Mittwoch, 16. Oktober 2019 22:56:00
An: The general-purpose Squeak developers list
Betreff: Re: [squeak-dev] Give debuggers more space ... :-)
 
Hi Marcel, I do like the readability of this, but how is list filtering affected?  I realized I almost always start my filter on the stack pane with ">" to filter on method names only (and not class names).  It looks like that won't be possible anymore.


On Wed, Oct 16, 2019 at 6:03 AM Marcel Taeumel <[hidden email]> wrote:
Note that #spaceFillWeight would work, too:


Best,
Marcel

Am 16.10.2019 12:57:04 schrieb Marcel Taeumel <[hidden email]>:


Best,
Marcel

Am 28.09.2019 13:12:55 schrieb Robert Hirschfeld <[hidden email]>:

+1

On 26. Sep 2019, at 13:36, Marcel Taeumel <[hidden email]> wrote:

Hi, all! 

May I add more spaces to Context >> #printOn:? ... and a "#" in front of the selector ...

<image.png>

Best,
Marcel






debugger-columns.2.cs (7K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Give debuggers more space ... :-)

marcel.taeumel
In reply to this post by Jakob Reschke-2
How will it look with long class names (or two of them)?


Okay-ish.... Not sure about that "[ ] in" ... it might deserve an extra column in the middle:


Best,
Marcel

Am 17.10.2019 20:24:02 schrieb Jakob Reschke <[hidden email]>:

How will it look with long class names (or two of them)?

Am Mi., 16. Okt. 2019 um 12:57 Uhr schrieb Marcel Taeumel <[hidden email]>:




12