Re: [Pharo-users] One comment to new Pharo5 debugger

[Johan Fabry]

I will just leave this here, so that people that prefer the buttons in their 
original place can get them back ...

I did some quick investigating, and it’s straightforward. Just change the 
implementation of GTGenericStackDebugger>>codeActionsPragmas to the following:

codeActionsPragmas

^ #( codeDebuggingAction stackDebuggingAction )

 Et voila, the stack debugging action buttons now are also available just above 
the code pane!

For extra goodness, the following two-liner is now also going into my startup 
preferences, run-once code part:

GTGenericStackDebugger compile: 'codeActionsPragmas
^ #(stackDebuggingAction codeDebuggingAction)' classified: 'building actions'

Voila, I will never miss those buttons again :-)

--
Does this mail seem too brief? Sorry for that, I don’t mean to be rude! Please 
see http://emailcharter.org  .

Johan Fabry   -   http://pleiad.cl/~jfabry
PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University of 
Chile

> On May 26, 2016, at 11:01, stepharo  wrote:
> 
> 
>> Yes, and there was also some discussion on the Pharo-users mailing list. 
>> Apparently the same comments more or less ...
>> 
>> I give a big +1 on moving the buttons down, so that they are between the 
>> stack and the code pane. I still don’t understand why they need to be so far 
>> away from the code pane, it makes much more sense above the code pane + we 
>> save on mouse movements.
> 
> Because doru got trapped into his own view on "UI design".
> 
> Even apple does not respect its own design documents. 
> 
> Stef

Re: [Pharo-users] Having STON generate flatter output

[Sven Van Caekenberghe]

Yes, STON uses depth-first traversal of the object graph. Since it uses 
numbered references, the traversal has to be fixed. This excludes other 
traversals, as far as I can see.

> On 26 May 2016, at 22:00, Peter Uhnák  wrote:
> 
> At a first glance it seems to me that it uses DFS instead of BFS, because it 
> doesn't distinguish what is it actually following.
> So maybe the strategy could be to follow BFS and use subinstances of 
> Collection as references.
> 
> Peter
> 
> On Thu, May 26, 2016 at 9:20 PM, Offray Vladimir Luna Cárdenas 
>  wrote:
> Hi,
> 
> I didn't find that strategy and finally created a #flatten method before 
> serializing my grafoscopio trees, with just what I wanted. At [1] you can 
> find the last version of the notebook show at this screenshot:
> 
> 
> 
> [1] http://mutabit.com/repos.fossil/panama-papers/artifact/cbfe8929edf64212
> 
> I know is this doesn't solve in anyway your problem... but may be it could 
> inspire you in some way. I was asking also for a flatter STON and the idea of 
> a method to flatten the tree wrote by myself was not evident at the 
> beginning, but was a very good solution.
> 
> Cheers,
> 
> Offray
> 
> 
> On 26/05/16 13:52, Peter Uhnák wrote:
>> Hi,
>> 
>> is it possible to configure STON to generate more flat output?
>> 
>> Imagine a scenario where an element can have children and the children have 
>> reference to their parent
>> 
>> 
>> ​
>> Now the problem is that the output of STON will depend on the order of the 
>> items,
>> so if I have "nice" ordering for the following, I will get a flat output
>> 
>> 
>> ​
>> If however the ordering is different, the output will be more nested
>> 
>> 
>> ​
>> As the ordering is not stable, I often end up with results like this (zoomed 
>> out)
>> 
>> 
>> ​
>> The image above has depth of about fourteen, even though it could be 
>> represented with just depth of four.
>> 
>> In the current state I cannot actually look at the generated output because 
>> it's impossible to find anything, which is problematic when an error occurs.
>> 
>> So the question is if it is possible to push the actual objects as far up as 
>> possible, and use references "@12" only on the deeper levels.
>> 
>> Thanks,
>> Peter
>> 
> 
> 

Re: [Pharo-users] One comment to new Pharo5 debugger

[stepharo]

Yes, and there was also some discussion on the Pharo-users mailing 
list. Apparently the same comments more or less ...


I give a big +1 on moving the buttons down, so that they are between 
the stack and the code pane. I still don’t understand why they need to 
be so far away from the code pane, it makes much more sense above the 
code pane + we save on mouse movements.


Because doru got trapped into his own view on "UI design".

Even apple does not respect its own design documents.

Stef

Re: [Pharo-users] One comment to new Pharo5 debugger

[Esteban Lorenzano]

> On 26 May 2016, at 14:49, Johan Fabry  wrote:
> 
> Yes, and there was also some discussion on the Pharo-users mailing list. 
> Apparently the same comments more or less ...
> 
> I give a big +1 on moving the buttons down, so that they are between the 
> stack and the code pane. I still don’t understand why they need to be so far 
> away from the code pane, it makes much more sense above the code pane + we 
> save on mouse movements.

is because of the “moldable” nature of the debugger, since the code panel could 
be anything (like a custom browser, etc.), it is not certain that buttons can 
be there… only “constant” place is the top of the browser… 
that does not means I do not agree it would be better closer to the code 
itself… but I will need to take a care look to that before proposing a possible 
change. 

Esteban

> 
> --
> Does this mail seem too brief? Sorry for that, I don’t mean to be rude! 
> Please see http://emailcharter.org  .
> 
> Johan Fabry   -   http://pleiad.cl/~jfabry 
> PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University of 
> Chile
> 
>> On May 26, 2016, at 04:37, Christophe Demarey > > wrote:
>> 
>> Hi Sabine,
>> 
>> this point was also « discussed » (no answer) here: 
>> http://forum.world.st/gtdebugger-debug-actions-buttons-td4874316.html 
>> 
>> Yes, the new buttons are counter-productive and there is even no setting to 
>> have them usable …
>> You can still with to the SpecDebugger through settings
>> 
>> 
>>> Le 25 mai 2016 à 22:49, Peter Uhnák >> > a écrit :
>>> 
>>> Hi,
>>> 
>>> yes, this question was raised before, but there are some disagreements over 
>>> how it should be, so it may take some time 
>>> http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html 
>>> 
>>> 
>>> You can also use a startup script to reassign them, such as this one. 
>>> https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformDebugger.st
>>>  
>>> 
>>> But a startup script is a temporary solution.
>>> 
>>> On Wed, May 25, 2016 at 9:43 PM, Sabine Manaa >> > wrote:
>>> Hi,
>>> 
>>> today I moved to Pharo5. It is great to get feedback and solutions for
>>> problems so quickly. It is a pleasure to work with Pharo and to have the
>>> community. I am grateful for having this.
>>> 
>>> I have one comment. I don't want to complain, I can use it but I was
>>> wondering about the new position and size of the debugger buttons.
>>> 
>>> There is a longer distance now from code text pane to the buttons - I see
>>> this as disadvantage to earlier versions of Pharo from the user experience.
>>> The buttons are a lot of smaller - same disadvantage - both if you use the
>>> mouse.
>>> 
>>> Ok, after seeing that, I thought "Sabine, you should use keyboard shortcuts
>>> here, too" (I use much of them but interesting - til now not in the
>>> debugger).
>>> 
>>> Then I saw the shortcuts for
>>> Proceed cmd+r
>>> Restart cmd-shift-a
>>> Into cmd-e
>>> over cmd-shift-o
>>> through cmd-shift-t
>>> 
>>> especially into, over and through have so different key combinations, two
>>> with shift, one without shift. When I debug, I often use for example
>>> into-into-over-over-over-throuhg-through--into-into etc...and with the
>>> combinations cmd-e and cmd-shit-e, it is more "finger-work". It would be
>>> better to have all those shortcuts with or all shortcuts without shift. And
>>> the letters not so far away at the keyboard (e-o-t)
>>> 
>>> This is only my opinion and my first impression after one day with Pharo5. I
>>> am sure, after a few days, I forgot that this was uncomfortable because I
>>> have the shortcuts coming automatically into my fingers.
>>> 
>>> Regards
>>> Sabine
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> View this message in context: 
>>> http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html 
>>> 
>>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com 
>>> .
>>> 
>>> 
>> 
> 

Re: [Pharo-users] One comment to new Pharo5 debugger

[Johan Fabry]

Yes, and there was also some discussion on the Pharo-users mailing list. 
Apparently the same comments more or less ...

I give a big +1 on moving the buttons down, so that they are between the stack 
and the code pane. I still don’t understand why they need to be so far away 
from the code pane, it makes much more sense above the code pane + we save on 
mouse movements.

--
Does this mail seem too brief? Sorry for that, I don’t mean to be rude! Please 
see http://emailcharter.org  .

Johan Fabry   -   http://pleiad.cl/~jfabry
PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University of 
Chile

> On May 26, 2016, at 04:37, Christophe Demarey  
> wrote:
> 
> Hi Sabine,
> 
> this point was also « discussed » (no answer) here: 
> http://forum.world.st/gtdebugger-debug-actions-buttons-td4874316.html 
> 
> Yes, the new buttons are counter-productive and there is even no setting to 
> have them usable …
> You can still with to the SpecDebugger through settings
> 
> 
>> Le 25 mai 2016 à 22:49, Peter Uhnák > > a écrit :
>> 
>> Hi,
>> 
>> yes, this question was raised before, but there are some disagreements over 
>> how it should be, so it may take some time 
>> http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html 
>> 
>> 
>> You can also use a startup script to reassign them, such as this one. 
>> https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformDebugger.st
>>  
>> 
>> But a startup script is a temporary solution.
>> 
>> On Wed, May 25, 2016 at 9:43 PM, Sabine Manaa > > wrote:
>> Hi,
>> 
>> today I moved to Pharo5. It is great to get feedback and solutions for
>> problems so quickly. It is a pleasure to work with Pharo and to have the
>> community. I am grateful for having this.
>> 
>> I have one comment. I don't want to complain, I can use it but I was
>> wondering about the new position and size of the debugger buttons.
>> 
>> There is a longer distance now from code text pane to the buttons - I see
>> this as disadvantage to earlier versions of Pharo from the user experience.
>> The buttons are a lot of smaller - same disadvantage - both if you use the
>> mouse.
>> 
>> Ok, after seeing that, I thought "Sabine, you should use keyboard shortcuts
>> here, too" (I use much of them but interesting - til now not in the
>> debugger).
>> 
>> Then I saw the shortcuts for
>> Proceed cmd+r
>> Restart cmd-shift-a
>> Into cmd-e
>> over cmd-shift-o
>> through cmd-shift-t
>> 
>> especially into, over and through have so different key combinations, two
>> with shift, one without shift. When I debug, I often use for example
>> into-into-over-over-over-throuhg-through--into-into etc...and with the
>> combinations cmd-e and cmd-shit-e, it is more "finger-work". It would be
>> better to have all those shortcuts with or all shortcuts without shift. And
>> the letters not so far away at the keyboard (e-o-t)
>> 
>> This is only my opinion and my first impression after one day with Pharo5. I
>> am sure, after a few days, I forgot that this was uncomfortable because I
>> have the shortcuts coming automatically into my fingers.
>> 
>> Regards
>> Sabine
>> 
>> 
>> 
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html 
>> 
>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com 
>> .
>> 
>> 
> 

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

[Sabine Manaa]

Hi Peter,

thanks. But I will wait for next integration level.
I would like to try it but I have to organize my time strictly, so I have
no time to play around so much ;-(

Regards
Sabine

2016-05-26 11:33 GMT+02:00 Peter Uhnák :

> Hi,
>
> > To manage on github there are some blog around
>
> I wrote a guide for moving from SmalltalkHub to Github
> http://peteruhnak.com/blog/2016/03/02/moving-project-from-smalltalkhub-to-github/
> And Uko wrote about versioning
> http://blog.yuriy.tymch.uk/2015/07/pharo-and-github-versioning-revision-2.html
>
> now I am writing a bit more practical guide on how to use Git from Pharo…
> hopefully it will be done during weekend, I'm busy with other stuff atm.
>
> Peter
>

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

[Peter Uhnák]

Hi,

> To manage on github there are some blog around

I wrote a guide for moving from SmalltalkHub to Github
http://peteruhnak.com/blog/2016/03/02/moving-project-from-smalltalkhub-to-github/
And Uko wrote about versioning
http://blog.yuriy.tymch.uk/2015/07/pharo-and-github-versioning-revision-2.html

now I am writing a bit more practical guide on how to use Git from Pharo…
hopefully it will be done during weekend, I'm busy with other stuff atm.

Peter

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

[Sabine Manaa]

Hi Steph,

thank you for your explanation.
I was reading a little bit this morning about pharo and github.
I am looking forward to the solution you will provide in future and use
sthub till then.

Regards
Sabine



--
View this message in context: 
http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exists-tp4897315p4897474.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Having a more robust PharoLauncher in low-bandwidth conditions

[Serge Stinckwich]

On Wed, May 25, 2016 at 9:27 PM, Peter Uhnák  wrote:
>> something like wget or curl
>
> there's also zeroconf as the alternative, or directly downloading the zip
> http://files.pharo.org/image/

I'm not sure I can use images build on the CI with zeroconf.

> Also Stef made a flash stick with Pharo, videos, etc. exactly for places
> like this (with bad or no internet).

Yes, sure. But you want to dl recent images, this does not work :-)

> But of course PharoLauncher shouldn't crash. Alternatively PharoLauncher as
> far as I know has a local cache, so maybe if you need just a fresh image and
> not the latest one you could reuse that?

I will look at PharoLauncher code if I have some time. At the moment,
I'm using wget to dl to my PharoLauncher directory.

Thank you.
-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

[stepharo]

Le 25/5/16 à 21:57, Sabine Manaa a écrit :

Hi Esteban,

do you know a documentation/entry point about moving to github?
To manage on github there are some blog around. Now what we want to 
offer is something else:
We want to have one solution where you can publish using git (but that 
people can also use fossil or mercurial if they provide the right commands)

from within Pharo.

Is it in experimental state

experimental for the integrated pharo version

or recommended for all Pharo users?

we want to offer a solution for everybody with minimum pain.


How/where to start?

Regards
Sabine

2016-05-25 21:54 GMT+02:00 EstebanLM [via Smalltalk] <[hidden email] 
>:


Hi,

yes, I recommend you to use the github version, we are moving there.
But anyway we are keeping the sthub as mirror… it just got
de-sync. And the only reason why I needed the merge, and not a
simple copy is because metadataless format got activated and I
lost the history, so I rather merge to recover history in some way… :)

cheers!
Esteban


On 25 May 2016, at 21:23, Sabine Manaa <[hidden email]
> wrote:

Hi Esteban,

great, now it works. Thank you!

In the comments, I see "merged with github". I am curious about
using github in future, too.

Regards
Sabine

2016-05-25 21:01 GMT+02:00 EstebanLM [via Smalltalk]<[hidden
email]>:

hi Sabine,

please update to latest packages of Voyage… there was a
de-sync problem with the API change in MongoTalk, that
*should* fix your issue.

cheers,
Esteban



On 25 May 2016, at 16:29, Sabine Manaa <[hidden email]
> wrote:

note that it only occurs (hanging image)  if you do
"VORepository current reset"
before. Or have a new Image.


2016-05-25 15:38 GMT+02:00 Sabine Manaa<[hidden email]
>:

I have a non-responding image with the original code
(with the signal)

2016-05-25 15:14 GMT+02:00 Holger Freyther [via
Smalltalk]<[hidden email]
>:


> On 25 May 2016, at 15:42, Esteban Lorenzano
<[hidden email]
>
wrote:
>
>

Hi,


> No I don’t… in part because is not me who make
that code, but also because it is expected: after,
you have:
>
> getCollection: aString
> ^ [ self addCollection: aString capped: false
size: nil max: nil ]
> on: MongoCollectionAlreadyExists
> do: [ :err |
> MongoCollection database: self name: aString ]
>
> so the idea is to refine the error to separate
MongoCollectionAlreadyExists so it can later be
catch and handled properly.

when adding capped collection support it seemed like
a good idea to fail if a collection already exists
that might not be capped, but given the follow up
issues I wonder if I/we should restore the original
behavior that just ignored all errors?

holger




If you reply to this email, your message will be
added to the discussion below:

http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exists-tp4897315p4897346.html
To start a new topic under Pharo Smalltalk Users,
email[hidden email]

To unsubscribe from Pharo Smalltalk Users,click here.
NAML







View this message in context:Re: Problem with Mongo on
Pharo5 ("collection already exists")




Sent from thePharo Smalltalk Users mailing list archive

Re: [Pharo-users] One comment to new Pharo5 debugger

[stepharo]

Thanks Sabine!

This is important that you report such problems.

Several people including me already reported this problem that we will 
have to address for real.


Stef


Le 25/5/16 à 21:43, Sabine Manaa a écrit :

Hi,

today I moved to Pharo5. It is great to get feedback and solutions for
problems so quickly. It is a pleasure to work with Pharo and to have the
community. I am grateful for having this.

I have one comment. I don't want to complain, I can use it but I was
wondering about the new position and size of the debugger buttons.

There is a longer distance now from code text pane to the buttons - I see
this as disadvantage to earlier versions of Pharo from the user experience.
The buttons are a lot of smaller - same disadvantage - both if you use the
mouse.

Ok, after seeing that, I thought "Sabine, you should use keyboard shortcuts
here, too" (I use much of them but interesting - til now not in the
debugger).

Then I saw the shortcuts for
Proceed cmd+r
Restart cmd-shift-a
Into cmd-e
over cmd-shift-o
through cmd-shift-t

especially into, over and through have so different key combinations, two
with shift, one without shift. When I debug, I often use for example
into-into-over-over-over-throuhg-through--into-into etc...and with the
combinations cmd-e and cmd-shit-e, it is more "finger-work". It would be
better to have all those shortcuts with or all shortcuts without shift. And
the letters not so far away at the keyboard (e-o-t)

This is only my opinion and my first impression after one day with Pharo5. I
am sure, after a few days, I forgot that this was uncomfortable because I
have the shortcuts coming automatically into my fingers.

Regards
Sabine


  




--
View this message in context: 
http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] One comment to new Pharo5 debugger

[Denis Kudriashov]

Hi.

Maybe me should give chance to standard Moose debugger view? (where stack
pane on the left)

2016-05-26 9:37 GMT+02:00 Christophe Demarey :

> Hi Sabine,
>
> this point was also « discussed » (no answer) here:
> http://forum.world.st/gtdebugger-debug-actions-buttons-td4874316.html
> Yes, the new buttons are counter-productive and there is even no setting
> to have them usable …
> You can still with to the SpecDebugger through settings
>
>
> Le 25 mai 2016 à 22:49, Peter Uhnák  a écrit :
>
> Hi,
>
> yes, this question was raised before, but there are some disagreements
> over how it should be, so it may take some time
> http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html
>
> You can also use a startup script to reassign them, such as this one.
> https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformDebugger.st
> But a startup script is a temporary solution.
>
> On Wed, May 25, 2016 at 9:43 PM, Sabine Manaa 
> wrote:
>
>> Hi,
>>
>> today I moved to Pharo5. It is great to get feedback and solutions for
>> problems so quickly. It is a pleasure to work with Pharo and to have the
>> community. I am grateful for having this.
>>
>> I have one comment. I don't want to complain, I can use it but I was
>> wondering about the new position and size of the debugger buttons.
>>
>> There is a longer distance now from code text pane to the buttons - I see
>> this as disadvantage to earlier versions of Pharo from the user
>> experience.
>> The buttons are a lot of smaller - same disadvantage - both if you use the
>> mouse.
>>
>> Ok, after seeing that, I thought "Sabine, you should use keyboard
>> shortcuts
>> here, too" (I use much of them but interesting - til now not in the
>> debugger).
>>
>> Then I saw the shortcuts for
>> Proceed cmd+r
>> Restart cmd-shift-a
>> Into cmd-e
>> over cmd-shift-o
>> through cmd-shift-t
>>
>> especially into, over and through have so different key combinations, two
>> with shift, one without shift. When I debug, I often use for example
>> into-into-over-over-over-throuhg-through--into-into etc...and with the
>> combinations cmd-e and cmd-shit-e, it is more "finger-work". It would be
>> better to have all those shortcuts with or all shortcuts without shift.
>> And
>> the letters not so far away at the keyboard (e-o-t)
>>
>> This is only my opinion and my first impression after one day with
>> Pharo5. I
>> am sure, after a few days, I forgot that this was uncomfortable because I
>> have the shortcuts coming automatically into my fingers.
>>
>> Regards
>> Sabine
>>
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html
>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com
>> .
>>
>>
>
>

Re: [Pharo-users] One comment to new Pharo5 debugger

[Sabine Manaa]

Hi Peter,

Thanks. I geht all the nabble mails and try to read at least the subject
but I missed this one.
I create my own shortcuts as first solution.

Regards
Sabine


Am Mittwoch, 25. Mai 2016 schrieb Peter Uhnák [via Smalltalk] :

> Hi,
>
> yes, this question was raised before, but there are some disagreements
> over how it should be, so it may take some time
> http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html
>
> You can also use a startup script to reassign them, such as this one.
> https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformDebugger.st
> But a startup script is a temporary solution.
>
> On Wed, May 25, 2016 at 9:43 PM, Sabine Manaa <[hidden email]
> > wrote:
>
>> Hi,
>>
>> today I moved to Pharo5. It is great to get feedback and solutions for
>> problems so quickly. It is a pleasure to work with Pharo and to have the
>> community. I am grateful for having this.
>>
>> I have one comment. I don't want to complain, I can use it but I was
>> wondering about the new position and size of the debugger buttons.
>>
>> There is a longer distance now from code text pane to the buttons - I see
>> this as disadvantage to earlier versions of Pharo from the user
>> experience.
>> The buttons are a lot of smaller - same disadvantage - both if you use the
>> mouse.
>>
>> Ok, after seeing that, I thought "Sabine, you should use keyboard
>> shortcuts
>> here, too" (I use much of them but interesting - til now not in the
>> debugger).
>>
>> Then I saw the shortcuts for
>> Proceed cmd+r
>> Restart cmd-shift-a
>> Into cmd-e
>> over cmd-shift-o
>> through cmd-shift-t
>>
>> especially into, over and through have so different key combinations, two
>> with shift, one without shift. When I debug, I often use for example
>> into-into-over-over-over-throuhg-through--into-into etc...and with the
>> combinations cmd-e and cmd-shit-e, it is more "finger-work". It would be
>> better to have all those shortcuts with or all shortcuts without shift.
>> And
>> the letters not so far away at the keyboard (e-o-t)
>>
>> This is only my opinion and my first impression after one day with
>> Pharo5. I
>> am sure, after a few days, I forgot that this was uncomfortable because I
>> have the shortcuts coming automatically into my fingers.
>>
>> Regards
>> Sabine
>>
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html
>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>>
>>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390p4897397.html
> To start a new topic under Pharo Smalltalk Users, email
> ml-node+s1294792n1310670...@n4.nabble.com
> 
> To unsubscribe from Pharo Smalltalk Users, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390p4897442.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] One comment to new Pharo5 debugger

[Christophe Demarey]

Hi Sabine,

this point was also « discussed » (no answer) here: 
http://forum.world.st/gtdebugger-debug-actions-buttons-td4874316.html 

Yes, the new buttons are counter-productive and there is even no setting to 
have them usable …
You can still with to the SpecDebugger through settings


> Le 25 mai 2016 à 22:49, Peter Uhnák  a écrit :
> 
> Hi,
> 
> yes, this question was raised before, but there are some disagreements over 
> how it should be, so it may take some time 
> http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html 
> 
> 
> You can also use a startup script to reassign them, such as this one. 
> https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformDebugger.st
>  
> 
> But a startup script is a temporary solution.
> 
> On Wed, May 25, 2016 at 9:43 PM, Sabine Manaa  > wrote:
> Hi,
> 
> today I moved to Pharo5. It is great to get feedback and solutions for
> problems so quickly. It is a pleasure to work with Pharo and to have the
> community. I am grateful for having this.
> 
> I have one comment. I don't want to complain, I can use it but I was
> wondering about the new position and size of the debugger buttons.
> 
> There is a longer distance now from code text pane to the buttons - I see
> this as disadvantage to earlier versions of Pharo from the user experience.
> The buttons are a lot of smaller - same disadvantage - both if you use the
> mouse.
> 
> Ok, after seeing that, I thought "Sabine, you should use keyboard shortcuts
> here, too" (I use much of them but interesting - til now not in the
> debugger).
> 
> Then I saw the shortcuts for
> Proceed cmd+r
> Restart cmd-shift-a
> Into cmd-e
> over cmd-shift-o
> through cmd-shift-t
> 
> especially into, over and through have so different key combinations, two
> with shift, one without shift. When I debug, I often use for example
> into-into-over-over-over-throuhg-through--into-into etc...and with the
> combinations cmd-e and cmd-shit-e, it is more "finger-work". It would be
> better to have all those shortcuts with or all shortcuts without shift. And
> the letters not so far away at the keyboard (e-o-t)
> 
> This is only my opinion and my first impression after one day with Pharo5. I
> am sure, after a few days, I forgot that this was uncomfortable because I
> have the shortcuts coming automatically into my fingers.
> 
> Regards
> Sabine
> 
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html 
> 
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> 
>