Some comments

> Font size is ridiculous! Make it at minimum 12 for the permanent visual
elements

This is subjective… I am even considering making the size smaller for
myself (after all, in Pharo 4 it was size 9).

> Line numbers: where is it used, not in the system browser

This is disabled by default, so it shouldn't be a problem.

> "Format as you read" -> what is tooltips good for?

This is autoformatting without the need to reformat the code yourself, very
useful if you are reading some old/unformatted codebase.

For example open Morph>>acceptDroppingMorph:event: and click on the button
— it will reformat the code without changing the code itself.

> AST navigation: what is it? I don't understand its description. What
nodes?

Do we really need a block of text of description for everything? If you
know what AST is then it is pretty self-explanatory. If you don't know what
AST is then the option has no value for you, because the navigation would
be random.

> Nautilis: where is the local senders tools?

You need to scope your view (top left corner button "Scoped")

> Spotter
Why Ctrl+[->]? my intuition tells me [->] as indicated by the blue icon
arrow, please fix it!

Because -> and <- is already taken. Pretty much any shortcut in the system
has ctrl/alt/command in it, so I don't see why this only thing in the
entire system should be different. You can also hover over the button to
see the shortcut.
Not to mention that you have two different right arrows (ctrl+right,
ctrl+shift+right), so just because you immediately see one use case doesn't
mean that it's the only one/best one. There was A LOT of discussion on the
mailing list regarding Spotter's usability and shortcuts.

> Playground
Why Ctrl+shift+g to open  a pane, looks like Ctrl+g is working.
Nevertheless Ctrl+g is not very handy short cut, it hurts the fingers! Can
it be changed?

Because it's not the same. do-it-all-and-go (ctrl+shift+g) executes all the
code and inspects it in the next pane, while ctrl+g (do-it-and-go) just the
selected block/current line.

> When do-it-all-and-go, the meta pane does not look nice: there are
sliders but there is enough place

What extra space? The bottom half is for the selected method.

> Image is now 47.7MB and it does not shrink! Big fat boy :)

This is a known bug in Pharo.


Peter

On Mon, Apr 25, 2016 at 12:16 PM, Hilaire <[email protected]> wrote:

> Hi,
>
> While giving a try to Pharo5, I wrote some notes about how it fells.
> It may be useful to share it. Of course it is also very opinionated and
> may be rude. But no offense to consider, really.
>
> More time is need for a real developer experience, may be later.
>
> Hilaire
>
> --
> Dr. Geo
> http://drgeo.eu
>

Reply via email to