You remember certainly this book that said that most users
are looking at ui the same way that we see a bear dansing in tutu while
it should be a classical dancer with grace.
So users adapt to things even if some of them are hurting them.
I don't. I do not like that I have to fight to get things that were
totally trivial to do.
Tools should adapt and help not the inverse.
Stef
Le 7/6/16 à 23:37, Tudor Girba a écrit :
Hi Stef,
Thanks for the feedback. Sorry for the long email, but I you raised several
issues and I thought it is worth addressing them.
The feature we are talking about came into being after several suggestions on
this mailing list (and quite some long discussions) that had the scenario of
keeping track of several executions. In the first version of the Playground it
was not possible to paste directly in the playground. We did not impose
anything, it was the contrary.
From your email I see that you would rather prefer the variant of embedding
the text as is after pressing Enter. Is this correct?
Here is another variant:
- Cmd+p
- Cmd+v ==> paste the string directly in the editor without comments
I think this would fit well.
What do you think?
More replies about Spotter inline.
On Jun 7, 2016, at 8:09 AM, stepharo <[email protected]> wrote:
Le 5/6/16 à 23:00, Tudor Girba a écrit :
Hi Stef,
The quotes appear only when you add the result in the playground.
No need to explain I'm not idiot and I know it.
The typical use case for this is to keep track of several results.
No need to explain I'm not idiot and I know it.
In this situation you do not want to modify the code to not affect the
highlighting and this is why it gets in a comment.
This is fun because I never ever needed it. But this is probably what everybody
else is doing that since this is the default.
I just write simple code and tests. Indeed I'm not that smart.
But your tools only embedd your scenario and let the other users forced to
adapt.
Well you do not want but I do.
I spent my evening removing quotes while writing tests.
What I hate with the GTTools is that you want to teach me how I should work.
Sorry but good tools do not do that.
Good tools empower the users and not constraint them.
I work a lot faster when I do not have to remove the wonderful comments or when
I have to copy and paste.
This commenting is breaking the flow of efficient people. May be GT team do not
work write tests in the
debugger but I do most of the time and I'm forced by the environment to remove
quotes all over the places.
If you want to copy the content without quotes, you can do:
Cmd+p -> popup
Cmd+c -> selects the current line and copies the text
Esc
Cmd+v
Sorry but I do not want.
I just want to print and modify directly.
7 keystrokes vs 2
Perhaps we can add another keybinding like Shift+Enter for adding the text
without quotes.
And why not the inverse.
By default printing is printing and if you want to do something else then you
have a special binding.
Now I'm upset with this general attitude (Oh I will teach how you can be a nice
user) that I will turn them off
or go and hack my own settings. Still I'm amazingly sad about this state of
affair.
All these story about GT is hurting me because of this attitude: we are so
smart and we thought a lot and we will teach you
You are mistaken here. We propose solutions that are different because this is
the only way to get to something new, but afterwards we iterate multiple times,
sometimes even a long time after the introduction of the original feature. For
example, for the problem you are mentioning with the Playground appears 1.5
years after we introduced the Playground. The fact that they these interfaces
are new breaks existing reflexes and the iterations that happen after are
focused mostly on trying to figure out whether this is inconvenient because is
new or because it is actually suboptimal.
This discussion is one of those. We wanted to solve the most often appearing
case in which we use Cmd+p as a way to preview quickly the result. Pasting the
code in the existing playground is an edge case for Cmd+p, not the primary
case. After having proposed a solution for the primary problem, people raised
the issue of the temporary results and then we created the idea of Enter and
have comments. This might not be your use case, but others have it.
how you should work... and at the end I the end-user has to adapt.
Look at the Spotter discussions: you looked for the graal and I was just
telling to you that I cannot find
simple information such as class refs!
So what saddens me the most is that
- you pretend to have end-user trying your tools but I have impression
that they are not real power users
or this is yourself and it means that you are never exposed to other people.
I can still not use Spotter because the way I put my hand on my keyboard.
So should change
- 1 my hands
- 2 my brain
- 3 my keyboard
- 4 do not use the tools?
- funnily enough if I would not have complain aggressively then it looks
like we would have the same than before.
This is incorrect. If you would not complain aggressively, we would simply have
a smoother conversation about solutions.
Your flow is not mine and I go faster my way but your tools force me to get
slow.
I do not have the time to produce a video but I would even if it would give a
bad press to Pharo.
I will do a presentation in the rmod team. Because people do not watch
themselves why acting.
Let’s do a remote session and I watch you do things. This week I am available
this Thursday morning or Friday after 11.
Good tools empower the users not constraint them.
GTTools feel often like an overengineer guitar that would have hampered Jimmy
Hendrix to do crazy solos.
Could well be.
Doru
Cheers,
Doru
On Jun 5, 2016, at 10:20 PM, stepharo <[email protected]> wrote:
Hi
I would like to know if there is a setting to remove the "" when printing the
result of an expression.
I know that playground has been thought to help me, but today I watched myself
removing the comments
code so often that I would like to get a setting because such wrapping of
results is really boring for me.
I'm spending my time removing them and I start to wonder why they are any
useful.
I would help me to write fast tests for example in the debugger.
Stef
--
www.tudorgirba.com
www.feenk.com
"What we can governs what we wish."
--
www.tudorgirba.com
www.feenk.com
"Obvious things are difficult to teach."
