- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

by Tudor Girba

Hi Uko, I think you mean that triple clicking on the cursor when it is inside the line should select the line, right? Cheers, Doru On Wed, Oct 1, 2014 at 8:54 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > If my 2 cents make sense, it will be nice to have things similar to text > editors. E.g. triple click for line select. > > Uko > > On 01 Oct 2014, at 07:51, stepharo <stepharo(a)free.fr> wrote: > > > My perception is that this kind of small changes adds no value. >> It just removes a small bit of value. >> So it's going to frustrate someone for nothing. >> Not a big frustration, I concede, but a gratuitous one. >> > > I think its the opposite. People will simply adapt. > > > Seriously I find that attitude really sad. > So why don't add TxText with average syntax higthlitghting and that igor > just does something else > on the sake that people will adapt. > > For me there is no justification for not having the same behavior with is > working perfectly well. > It is not a question of dogma but just pragmatic > - it works well > - it is handy > - it is not incompatible with the double click dogma. > > > Finally, the best thing it brings is exposing that some events are >> handled incorrectly. >> At least I hope it will give us a chance to correct them :) >> > > :) > > Doru > > > >> >> 2014-09-30 22:59 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: >> >>> Hi, >>> >>> I can see how people get use with this behavior, but I am quite >>> certain that the solution from PluggableTextMorph was a workaround solution >>> due to a missing double click event. Now we have that event and we can use >>> it where it is appropriate. >>> >>> It's not that we copy things for the sake of copying, but I simply >>> think double clicking is a better choice here. click-pause-click >>> introduces, from a cognitive perspective, a hidden modal mode. That is, you >>> have no chance of knowing in which state you are. I was several times >>> annoyed by inadvertently selecting pieces of code (often during demos). At >>> the same time, I believe it is reasonable to assume that programmers know >>> how to double click. >>> >>> So, yes, I did think of it quite explicitly :) >>> >>> Doub >>> >>> Cheers, >>> Doru >>> >>> >>> >>> On Tue, Sep 30, 2014 at 10:46 PM, Nicolas Cellier < >>> nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>>> I find click pause click useful. >>>> No stress nor necessary adjustment of double-click delay. >>>> What could be the intention of a user clicking repeatedly on the same >>>> area? >>>> Did you think of it? >>>> If copying what everyone else does is the sole value, then let's not >>>> do Pharo. >>>> >>>> 2014-09-30 21:34 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: >>>> >>>>> Hi, >>>>> >>>>> I explained before but it went unnoticed. The selection happens on >>>>> double click like in any other editor. >>>>> >>>>> The regular PluggableTextMorph also tries to do it on a kind of a >>>>> double click, only it is implemented as click-pause-click. So, if you click >>>>> once, wait 5 minutes, and click again, it will select. This is not >>>>> particularly useful. >>>>> >>>>> So, Rubric selects on double click. >>>>> >>>>> Now, as I mentioned before, there happens to be a random double >>>>> click issue. I cannot reproduce it, but sometimes it happens. Also, when I >>>>> save the image and load it back, the problem is gone. Please note that this >>>>> issue is not related to Rubric, but to the double click event throughout >>>>> the entire image. For example, if you see that double click does not work >>>>> in Rubric, try to double click on the window title to maximize a window and >>>>> you will see that it does not work. >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> >>>>> On Tue, Sep 30, 2014 at 8:42 PM, stepharo <stepharo(a)free.fr> wrote: >>>>> >>>>>> With the previous tools I can select a piece of text by clicking >>>>>> after its last element and now I cannot >>>>>> or I can but sometimes. >>>>>> >>>>>> So what is the fix? >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Every thing has its own flow" >>>>> >>>> >>>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 1, 2014

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

by kilon alios

Why it has to be black or white just implement both or all of these ideas and let user choose in pharo settings. Problem solved Î£ÏÎ¹Ï 1 ÎÎºÏ 2014 9:55 Ï.Î¼., Î¿ ÏÏÎ®ÏÏÎ·Ï "Yuriy Tymchuk" <yuriy.tymchuk(a)me.com> ÎÎ³ÏÎ±ÏÎµ: > If my 2 cents make sense, it will be nice to have things similar to text > editors. E.g. triple click for line select. > > Uko > > On 01 Oct 2014, at 07:51, stepharo <stepharo(a)free.fr> wrote: > > > My perception is that this kind of small changes adds no value. >> It just removes a small bit of value. >> So it's going to frustrate someone for nothing. >> Not a big frustration, I concede, but a gratuitous one. >> > > I think its the opposite. People will simply adapt. > > > Seriously I find that attitude really sad. > So why don't add TxText with average syntax higthlitghting and that igor > just does something else > on the sake that people will adapt. > > For me there is no justification for not having the same behavior with is > working perfectly well. > It is not a question of dogma but just pragmatic > - it works well > - it is handy > - it is not incompatible with the double click dogma. > > > Finally, the best thing it brings is exposing that some events are >> handled incorrectly. >> At least I hope it will give us a chance to correct them :) >> > > :) > > Doru > > > >> >> 2014-09-30 22:59 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: >> >>> Hi, >>> >>> I can see how people get use with this behavior, but I am quite >>> certain that the solution from PluggableTextMorph was a workaround solution >>> due to a missing double click event. Now we have that event and we can use >>> it where it is appropriate. >>> >>> It's not that we copy things for the sake of copying, but I simply >>> think double clicking is a better choice here. click-pause-click >>> introduces, from a cognitive perspective, a hidden modal mode. That is, you >>> have no chance of knowing in which state you are. I was several times >>> annoyed by inadvertently selecting pieces of code (often during demos). At >>> the same time, I believe it is reasonable to assume that programmers know >>> how to double click. >>> >>> So, yes, I did think of it quite explicitly :) >>> >>> Doub >>> >>> Cheers, >>> Doru >>> >>> >>> >>> On Tue, Sep 30, 2014 at 10:46 PM, Nicolas Cellier < >>> nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>>> I find click pause click useful. >>>> No stress nor necessary adjustment of double-click delay. >>>> What could be the intention of a user clicking repeatedly on the same >>>> area? >>>> Did you think of it? >>>> If copying what everyone else does is the sole value, then let's not >>>> do Pharo. >>>> >>>> 2014-09-30 21:34 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: >>>> >>>>> Hi, >>>>> >>>>> I explained before but it went unnoticed. The selection happens on >>>>> double click like in any other editor. >>>>> >>>>> The regular PluggableTextMorph also tries to do it on a kind of a >>>>> double click, only it is implemented as click-pause-click. So, if you click >>>>> once, wait 5 minutes, and click again, it will select. This is not >>>>> particularly useful. >>>>> >>>>> So, Rubric selects on double click. >>>>> >>>>> Now, as I mentioned before, there happens to be a random double >>>>> click issue. I cannot reproduce it, but sometimes it happens. Also, when I >>>>> save the image and load it back, the problem is gone. Please note that this >>>>> issue is not related to Rubric, but to the double click event throughout >>>>> the entire image. For example, if you see that double click does not work >>>>> in Rubric, try to double click on the window title to maximize a window and >>>>> you will see that it does not work. >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> >>>>> On Tue, Sep 30, 2014 at 8:42 PM, stepharo <stepharo(a)free.fr> wrote: >>>>> >>>>>> With the previous tools I can select a piece of text by clicking >>>>>> after its last element and now I cannot >>>>>> or I can but sometimes. >>>>>> >>>>>> So what is the fix? >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Every thing has its own flow" >>>>> >>>> >>>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > >

Oct. 1, 2014

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

by Tudor Girba

Hi Stef, Thanks for your comments. In particular, the one about clicking on the current cursor. I never saw it like that because I always used the mouse. So in fact, I was wrong in seeing it as click-pause-click because it should have been as click-on-cursor. I actually like this one. However, the current behavior from TextMorph is incompatible with double click because if I double click on the cursor, then the selection is set and then deleted because the current implementation treats the double click as two clicks. But, I believe we could change that one and have both the click-on-cursor and the double-click select. I opened a ticket: https://pharo.fogbugz.com/f/cases/14132/Rubric-should-support-click-on-curs… Cheers, Doru On Wed, Oct 1, 2014 at 7:51 AM, stepharo <stepharo(a)free.fr> wrote: > > My perception is that this kind of small changes adds no value. >> It just removes a small bit of value. >> So it's going to frustrate someone for nothing. >> Not a big frustration, I concede, but a gratuitous one. >> > > I think its the opposite. People will simply adapt. > > > Seriously I find that attitude really sad. > So why don't add TxText with average syntax higthlitghting and that igor > just does something else > on the sake that people will adapt. > > For me there is no justification for not having the same behavior with is > working perfectly well. > It is not a question of dogma but just pragmatic > - it works well > - it is handy > - it is not incompatible with the double click dogma. > > > > Finally, the best thing it brings is exposing that some events are >> handled incorrectly. >> At least I hope it will give us a chance to correct them :) >> > > :) > > Doru > > > >> >> 2014-09-30 22:59 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: >> >>> Hi, >>> >>> I can see how people get use with this behavior, but I am quite >>> certain that the solution from PluggableTextMorph was a workaround solution >>> due to a missing double click event. Now we have that event and we can use >>> it where it is appropriate. >>> >>> It's not that we copy things for the sake of copying, but I simply >>> think double clicking is a better choice here. click-pause-click >>> introduces, from a cognitive perspective, a hidden modal mode. That is, you >>> have no chance of knowing in which state you are. I was several times >>> annoyed by inadvertently selecting pieces of code (often during demos). At >>> the same time, I believe it is reasonable to assume that programmers know >>> how to double click. >>> >>> So, yes, I did think of it quite explicitly :) >>> >>> Doub >>> >>> Cheers, >>> Doru >>> >>> >>> >>> On Tue, Sep 30, 2014 at 10:46 PM, Nicolas Cellier < >>> nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>>> I find click pause click useful. >>>> No stress nor necessary adjustment of double-click delay. >>>> What could be the intention of a user clicking repeatedly on the same >>>> area? >>>> Did you think of it? >>>> If copying what everyone else does is the sole value, then let's not >>>> do Pharo. >>>> >>>> 2014-09-30 21:34 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: >>>> >>>>> Hi, >>>>> >>>>> I explained before but it went unnoticed. The selection happens on >>>>> double click like in any other editor. >>>>> >>>>> The regular PluggableTextMorph also tries to do it on a kind of a >>>>> double click, only it is implemented as click-pause-click. So, if you click >>>>> once, wait 5 minutes, and click again, it will select. This is not >>>>> particularly useful. >>>>> >>>>> So, Rubric selects on double click. >>>>> >>>>> Now, as I mentioned before, there happens to be a random double >>>>> click issue. I cannot reproduce it, but sometimes it happens. Also, when I >>>>> save the image and load it back, the problem is gone. Please note that this >>>>> issue is not related to Rubric, but to the double click event throughout >>>>> the entire image. For example, if you see that double click does not work >>>>> in Rubric, try to double click on the window title to maximize a window and >>>>> you will see that it does not work. >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> >>>>> On Tue, Sep 30, 2014 at 8:42 PM, stepharo <stepharo(a)free.fr> wrote: >>>>> >>>>>> With the previous tools I can select a piece of text by clicking >>>>>> after its last element and now I cannot >>>>>> or I can but sometimes. >>>>>> >>>>>> So what is the fix? >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Every thing has its own flow" >>>>> >>>> >>>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 1, 2014

Re: [Pharo-dev] GTTool bug:

by Marcus Denker

On 30 Sep 2014, at 20:41, stepharo <stepharo(a)free.fr> wrote: > edit: aText label: labelString accept: anAction > "Open an editor on the given string/text" > > ^(Smalltalk tools workspace openLabel: labelString) > acceptContents: aText; > acceptAction: anAction; > yourself. > > Yes, we are abusing the workspace for an editor, this is not good. We should have an editor that is an editor, not a workspace. > -> DNU > > UIManager default > edit: 'jlklkjk' > label: 'lkjlkjjkl' >

Oct. 1, 2014

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

by Yuriy Tymchuk

If my 2 cents make sense, it will be nice to have things similar to text editors. E.g. triple click for line select. Uko > On 01 Oct 2014, at 07:51, stepharo <stepharo(a)free.fr> wrote: > > >> My perception is that this kind of small changes adds no value. >> It just removes a small bit of value. >> So it's going to frustrate someone for nothing. >> Not a big frustration, I concede, but a gratuitous one. >> >> I think its the opposite. People will simply adapt. > > Seriously I find that attitude really sad. > So why don't add TxText with average syntax higthlitghting and that igor just does something else > on the sake that people will adapt. > > For me there is no justification for not having the same behavior with is working perfectly well. > It is not a question of dogma but just pragmatic > - it works well > - it is handy > - it is not incompatible with the double click dogma. > >> >> Finally, the best thing it brings is exposing that some events are handled incorrectly. >> At least I hope it will give us a chance to correct them :) >> >> :) >> >> Doru >> >> >> >> 2014-09-30 22:59 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>>: >> Hi, >> >> I can see how people get use with this behavior, but I am quite certain that the solution from PluggableTextMorph was a workaround solution due to a missing double click event. Now we have that event and we can use it where it is appropriate. >> >> It's not that we copy things for the sake of copying, but I simply think double clicking is a better choice here. click-pause-click introduces, from a cognitive perspective, a hidden modal mode. That is, you have no chance of knowing in which state you are. I was several times annoyed by inadvertently selecting pieces of code (often during demos). At the same time, I believe it is reasonable to assume that programmers know how to double click. >> >> So, yes, I did think of it quite explicitly :) >> >> Doub >> >> Cheers, >> Doru >> >> >> >> On Tue, Sep 30, 2014 at 10:46 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com <mailto:nicolas.cellier.aka.nice@gmail.com>> wrote: >> I find click pause click useful. >> No stress nor necessary adjustment of double-click delay. >> What could be the intention of a user clicking repeatedly on the same area? >> Did you think of it? >> If copying what everyone else does is the sole value, then let's not do Pharo. >> >> 2014-09-30 21:34 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>>: >> Hi, >> >> I explained before but it went unnoticed. The selection happens on double click like in any other editor. >> >> The regular PluggableTextMorph also tries to do it on a kind of a double click, only it is implemented as click-pause-click. So, if you click once, wait 5 minutes, and click again, it will select. This is not particularly useful. >> >> So, Rubric selects on double click. >> >> Now, as I mentioned before, there happens to be a random double click issue. I cannot reproduce it, but sometimes it happens. Also, when I save the image and load it back, the problem is gone. Please note that this issue is not related to Rubric, but to the double click event throughout the entire image. For example, if you see that double click does not work in Rubric, try to double click on the window title to maximize a window and you will see that it does not work. >> >> Cheers, >> Doru >> >> >> >> On Tue, Sep 30, 2014 at 8:42 PM, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: >> With the previous tools I can select a piece of text by clicking after its last element and now I cannot >> or I can but sometimes. >> >> So what is the fix? >> >> Stef >> >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> >> "Every thing has its own flow" >> >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> >> "Every thing has its own flow" >> >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> >> "Every thing has its own flow" >

Oct. 1, 2014

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

by stepharo

> My perception is that this kind of small changes adds no value. > It just removes a small bit of value. > So it's going to frustrate someone for nothing. > Not a big frustration, I concede, but a gratuitous one. > > > I think its the opposite. People will simply adapt. Seriously I find that attitude really sad. So why don't add TxText with average syntax higthlitghting and that igor just does something else on the sake that people will adapt. For me there is no justification for not having the same behavior with is working perfectly well. It is not a question of dogma but just pragmatic - it works well - it is handy - it is not incompatible with the double click dogma. > > Finally, the best thing it brings is exposing that some events are > handled incorrectly. > At least I hope it will give us a chance to correct them :) > > > :) > > Doru > > > 2014-09-30 22:59 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>>: > > Hi, > > I can see how people get use with this behavior, but I am > quite certain that the solution from PluggableTextMorph was a > workaround solution due to a missing double click event. Now > we have that event and we can use it where it is appropriate. > > It's not that we copy things for the sake of copying, but I > simply think double clicking is a better choice here. > click-pause-click introduces, from a cognitive perspective, a > hidden modal mode. That is, you have no chance of knowing in > which state you are. I was several times annoyed by > inadvertently selecting pieces of code (often during demos). > At the same time, I believe it is reasonable to assume that > programmers know how to double click. > > So, yes, I did think of it quite explicitly :) > > Doub > > Cheers, > Doru > > > > On Tue, Sep 30, 2014 at 10:46 PM, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com > <mailto:nicolas.cellier.aka.nice@gmail.com>> wrote: > > I find click pause click useful. > No stress nor necessary adjustment of double-click delay. > What could be the intention of a user clicking repeatedly > on the same area? > Did you think of it? > If copying what everyone else does is the sole value, then > let's not do Pharo. > > 2014-09-30 21:34 GMT+02:00 Tudor Girba > <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>>: > > Hi, > > I explained before but it went unnoticed. The > selection happens on double click like in any other > editor. > > The regular PluggableTextMorph also tries to do it on > a kind of a double click, only it is implemented as > click-pause-click. So, if you click once, wait 5 > minutes, and click again, it will select. This is not > particularly useful. > > So, Rubric selects on double click. > > Now, as I mentioned before, there happens to be a > random double click issue. I cannot reproduce it, but > sometimes it happens. Also, when I save the image and > load it back, the problem is gone. Please note that > this issue is not related to Rubric, but to the double > click event throughout the entire image. For example, > if you see that double click does not work in Rubric, > try to double click on the window title to maximize a > window and you will see that it does not work. > > Cheers, > Doru > > > > On Tue, Sep 30, 2014 at 8:42 PM, stepharo > <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > > With the previous tools I can select a piece of > text by clicking after its last element and now I > cannot > or I can but sometimes. > > So what is the fix? > > Stef > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Oct. 1, 2014

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

by stepharo

On 1/10/14 00:47, Nicolas Cellier wrote: > You're right, a modal UI that would involve a triple, quadruple click > or cycle between even more states would be annoying. > But just switching a selection, how so? Personnally I don't mind. Is > it a matter of taste? > Anyway, the whole text editor is modal, mind you, did you see this > thing named cursor? > If I pause, then start typing again, it writes where I stopped 5 > minutes ago instead of where my own focus shifted... That's quite > stupid ;) > Or maybe you suggest the right solution would be a vanishing cursor > materializing the loss of focus of the text widget after an arbitrary > delay, for the sake of relaxing my cognitive load? > > From the implementation point of view, handling click-pause-click is > more than simple by reusing the existing selection state and is not > requiring any arbitrary Delay and its additional states. > So I don't see a huge value in suppressing it. I agree with nicolas. > Is it motivated by cleaning code duplication after adding a specific > double click handling? > Or is reducing the features to a core set a goal per se? > > My perception is that this kind of small changes adds no value. +1 > It just removes a small bit of value. > So it's going to frustrate someone for nothing. > Not a big frustration, I concede, but a gratuitous one. I agree > > Finally, the best thing it brings is exposing that some events are > handled incorrectly. > At least I hope it will give us a chance to correct them :) > > 2014-09-30 22:59 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>>: > > Hi, > > I can see how people get use with this behavior, but I am quite > certain that the solution from PluggableTextMorph was a workaround > solution due to a missing double click event. Now we have that > event and we can use it where it is appropriate. > > It's not that we copy things for the sake of copying, but I simply > think double clicking is a better choice here. click-pause-click > introduces, from a cognitive perspective, a hidden modal mode. > That is, you have no chance of knowing in which state you are. I > was several times annoyed by inadvertently selecting pieces of > code (often during demos). At the same time, I believe it is > reasonable to assume that programmers know how to double click. > > So, yes, I did think of it quite explicitly :) > > Doub > > Cheers, > Doru > > > > On Tue, Sep 30, 2014 at 10:46 PM, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com > <mailto:nicolas.cellier.aka.nice@gmail.com>> wrote: > > I find click pause click useful. > No stress nor necessary adjustment of double-click delay. > What could be the intention of a user clicking repeatedly on > the same area? > Did you think of it? > If copying what everyone else does is the sole value, then > let's not do Pharo. > > 2014-09-30 21:34 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>>: > > Hi, > > I explained before but it went unnoticed. The selection > happens on double click like in any other editor. > > The regular PluggableTextMorph also tries to do it on a > kind of a double click, only it is implemented as > click-pause-click. So, if you click once, wait 5 minutes, > and click again, it will select. This is not particularly > useful. > > So, Rubric selects on double click. > > Now, as I mentioned before, there happens to be a random > double click issue. I cannot reproduce it, but sometimes > it happens. Also, when I save the image and load it back, > the problem is gone. Please note that this issue is not > related to Rubric, but to the double click event > throughout the entire image. For example, if you see that > double click does not work in Rubric, try to double click > on the window title to maximize a window and you will see > that it does not work. > > Cheers, > Doru > > > > On Tue, Sep 30, 2014 at 8:42 PM, stepharo > <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > > With the previous tools I can select a piece of text > by clicking after its last element and now I cannot > or I can but sometimes. > > So what is the fix? > > Stef > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" > >

Oct. 1, 2014

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

by stepharo

I do not get your point. I do not see why this is mode. If the cursor is already on something or at the end or beginning of something clicking on the same place, select it. This is just different but it works. and it is not incompatible with also supporting double clicking. So why now we cannot have the previous behavior which was compatible with what the world is doing but in addition let us work. We can also say that double clicking is strange. > Hi, > > I can see how people get use with this behavior, but I am quite > certain that the solution from PluggableTextMorph was a workaround > solution due to a missing double click event. Now we have that event > and we can use it where it is appropriate. > > It's not that we copy things for the sake of copying, but I simply > think double clicking is a better choice here. click-pause-click > introduces, from a cognitive perspective, a hidden modal mode. That > is, you have no chance of knowing in which state you are. I was > several times annoyed by inadvertently selecting pieces of code (often > during demos). At the same time, I believe it is reasonable to assume > that programmers know how to double click. > > So, yes, I did think of it quite explicitly :) > > Doub > > Cheers, > Doru > > > > On Tue, Sep 30, 2014 at 10:46 PM, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com > <mailto:nicolas.cellier.aka.nice@gmail.com>> wrote: > > I find click pause click useful. > No stress nor necessary adjustment of double-click delay. > What could be the intention of a user clicking repeatedly on the > same area? > Did you think of it? > If copying what everyone else does is the sole value, then let's > not do Pharo. > > 2014-09-30 21:34 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>>: > > Hi, > > I explained before but it went unnoticed. The selection > happens on double click like in any other editor. > > The regular PluggableTextMorph also tries to do it on a kind > of a double click, only it is implemented as > click-pause-click. So, if you click once, wait 5 minutes, and > click again, it will select. This is not particularly useful. > > So, Rubric selects on double click. > > Now, as I mentioned before, there happens to be a random > double click issue. I cannot reproduce it, but sometimes it > happens. Also, when I save the image and load it back, the > problem is gone. Please note that this issue is not related to > Rubric, but to the double click event throughout the entire > image. For example, if you see that double click does not work > in Rubric, try to double click on the window title to maximize > a window and you will see that it does not work. > > Cheers, > Doru > > > > On Tue, Sep 30, 2014 at 8:42 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > With the previous tools I can select a piece of text by > clicking after its last element and now I cannot > or I can but sometimes. > > So what is the fix? > > Stef > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Oct. 1, 2014

Re: [Pharo-dev] GTTools bug - why I cannot select the text by simply clicking at the end of it....

by stepharo

> I find click pause click useful. Me too. > No stress nor necessary adjustment of double-click delay. > What could be the intention of a user clicking repeatedly on the same > area? > Did you think of it? > If copying what everyone else does is the sole value, then let's not > do Pharo. > > 2014-09-30 21:34 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>>: > > Hi, > > I explained before but it went unnoticed. The selection happens on > double click like in any other editor. > > The regular PluggableTextMorph also tries to do it on a kind of a > double click, only it is implemented as click-pause-click. So, if > you click once, wait 5 minutes, and click again, it will select. > This is not particularly useful. > > So, Rubric selects on double click. > > Now, as I mentioned before, there happens to be a random double > click issue. I cannot reproduce it, but sometimes it happens. > Also, when I save the image and load it back, the problem is gone. > Please note that this issue is not related to Rubric, but to the > double click event throughout the entire image. For example, if > you see that double click does not work in Rubric, try to double > click on the window title to maximize a window and you will see > that it does not work. > > Cheers, > Doru > > > > On Tue, Sep 30, 2014 at 8:42 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > With the previous tools I can select a piece of text by > clicking after its last element and now I cannot > or I can but sometimes. > > So what is the fix? > > Stef > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" > >

Oct. 1, 2014

Re: [Pharo-dev] is Kommiter working for you in 40 latest?

by Max Leske

On 01.10.2014, at 07:37, stepharo <stepharo(a)free.fr> wrote: > is Kommiter working for you in 40 latest? > Because I get an error tellling to me that it cannot find Applications / Pharo? > It works, but itâs a pain to use for slices (dependencies not included if they are not dirty, weird problems with file access etc.). Iâm back to committing through MC directly.

Oct. 1, 2014