March 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] TextMorph scrolling the text on edit or selection operations

by Johan Fabry

It would be very good to have a full test suite for Spec, but unit tests for UI stuff is complicated :-/ > On Mar 21, 2015, at 18:06, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Also even though this was morphic issue, perhaps we should start adding tests for spec since there are none. :( ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

March 22, 2015

Re: [Pharo-dev] TextMorph scrolling the text on edit or selection operations

by Johan Fabry

Hi Ben, Itâs noticeable if you use small windows a lot, like I do. I guess you must have a bigger screen than mine ;-) There is a description halfway down the thread on how to reproduce it, just before I uploaded the slice. Date is 19/08/2014 <https://pharo.fogbugz.com/f/cases/12569/TextModel-should-not-move-scroll-wh…> > On Mar 22, 2015, at 09:00, Ben Coman <btc(a)openInWorld.com> wrote: > > Can't say that I noticed it. There is no information on that issue on how to reproduce it. Sounds like you've got two use cases. Can you provide some specific examples of these so I can observe the behaviour. > cheers -ben > > On Sun, Mar 22, 2015 at 3:19 AM, Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: > Hi all, > > I am assuming that I am not the only one that gets very annoyed when a TextMorph scrolls the text when typing, such that the line I am typing is always at the bottom, or scrolls the debugger when I am stepping over instructions. I looked into this (bug > https://pharo.fogbugz.com/f/cases/12569/TextModel-should-not-move-scroll-wh… <https://pharo.fogbugz.com/f/cases/12569/TextModel-should-not-move-scroll-wh…> actually) and I found a fix. > > But first I want to understand why the code is as it is. Anybody have any idea why PluggableTextMorph>>setTextBasic: starts with scrollBar setValue: 0.0. ?? If I remove this line the very annoying behavior is gone, and as far as I can see there are no negative consequences on text handling (and scrolling) in general. So I am wondering why it is there at all. > > A slice with my fix is in the inbox if you want to play a bit with it: SLICE-Issue-12569-TextModel-should-not-move-scroll-when-accepting-text-johanfabry.1 > > Please have a look, this behavior has been getting on my nerves for quite some time now â¦ > > > ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- > > Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

March 22, 2015

Re: [Pharo-dev] Color arithmetical operations are broken

by Aliaksei Syrel

> > Color white - (Color white alpha:0) = Color white > Color white - (Color white alpha:0.5) = Color gray. > Color white - (Color white alpha:1.0) = Color black. > For what do you need the color arithmetic ? > Maybe there are already other operations defined on Color that you can > used instead. That is too complicated :) The idea was to have one-line fix that just leaves the behaviour as it was before, simply makes it not produce garbage. Basically there should be a long discussion after pharo 4 is released. How it is now: (Color white alpha: 0) = Color transparent => false Color white - (Color white alpha: 0) = Color black => true >From logical point of view is should not be black. But from mathematical point of view Color is just a vector and operations with it should be the same or almost the same as with vectors. For what do you need the color arithmetic ? I wanted to get linear discrete transformation from one color to another to use it in animation Cheers, Alex On Sun, Mar 22, 2015 at 1:54 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 22 Mar 2015, at 13:35, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-03-22 12:43 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>: > >> >> >> 2015-03-21 15:51 GMT+01:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> >>> Why not take the average of alpha in all cases? >>> >>> Eliot (phone) >>> >>> On Mar 21, 2015, at 6:32 AM, Aliaksei Syrel <alex.syrel(a)gmail.com> >>> wrote: >>> >> >> >> Or weight the argument by its alpha and don't change the alpha of the >> receiver: >> Color white - (Color white alpha:0) = Color white >> Color white - (Color white alpha:0.5) = Color gray. >> Color white - (Color white alpha:1.0) = Color black. >> >> For what do you need the color arithmetic ? >> Maybe there are already other operations defined on Color that you can >> used instead. >> >> As the arithmetic operations on Color doesn't work (for years?), maybe we >> should remove >> the operation now, and replace them with a more verbose api >> addRGB/ addRGBA/ subRGBA .... >> >> nicolai >> >> > Ah, this issue is already closed. That was a rather short discussion. And > #/ and #* still don't work > for colors. > > > Yesâ¦ I think we have a problem that there is no âthis is ready for > integrationâ check. > > We need to get more carefulâ¦ > > Marcus >

March 22, 2015

Re: [Pharo-dev] [Reflectivity] simple #before and #after links working...

by Marcus Denker

>> > I will revert the change in the visitorâ¦ this way we are sure that we do not get any problems. > > https://pharo.fogbugz.com/f/cases/15207/Undo-compiler-change-from-case-15196 <https://pharo.fogbugz.com/f/cases/15207/Undo-compiler-change-from-case-15196> > > I am really looking forward to that in Pharo5â¦ it is (one of my) largest mistakes that after my PhD I did not focus on > getting Reflectivity into Pharoâ¦ it is still amazing, even 5 years later, I think. (but I am biased ;-) > > Marcus > > > Thanks Marcus. It sets a good example for everyone (including me). Anyway, its a nice bit of honey to draw more people to follow the Pharo 5 trunk ;) > cheers -ben I will be so great that nobody will use Pharo4 everâ¦ ;-) Marcus

March 22, 2015

Re: [Pharo-dev] [Reflectivity] simple #before and #after links working...

by Ben Coman

On Sun, Mar 22, 2015 at 9:24 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 22 Mar 2015, at 11:41, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 22 Mar 2015, at 11:33, Ben Coman <btc(a)openInWorld.com> wrote: > > That is very cool. But I need to ask the tough question - given that the > feature freeze was three weeks ago, what do we gain by adding this in Pharo > 4? > > * Is it needed for demonstrations that won't be based off latest features > in Pharo 5 ? > > * Are third party libraries expected to be based only off Pharo 4 MetaLink > features, rather than additional MetaLink features it sounds like Pharo 5 > will get ? > > which means this slice should not impact anything > > > Because "should" being the operative word... is a slippery slope. If we > have a philosophy of freezing features before a Release, then we should > have the discipline to hold to that - at least in last 7 days before > Release. > > > Yes, maybe we should postpone itâ¦ releasing is boring, I have to admit :-) > > I will revert the change in the visitorâ¦ this way we are sure that we do > not get any problems. > > > https://pharo.fogbugz.com/f/cases/15207/Undo-compiler-change-from-case-15196 > > I am really looking forward to that in Pharo5â¦ it is (one of my) largest > mistakes that after my PhD I did not focus on > getting Reflectivity into Pharoâ¦ it is still amazing, even 5 years later, > I think. (but I am biased ;-) > > Marcus > > Thanks Marcus. It sets a good example for everyone (including me). Anyway, its a nice bit of honey to draw more people to follow the Pharo 5 trunk ;) cheers -ben

March 22, 2015

Re: [Pharo-dev] [Reflectivity] simple #before and #after links working...

by Marcus Denker

> On 22 Mar 2015, at 11:41, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 22 Mar 2015, at 11:33, Ben Coman <btc(a)openInWorld.com> wrote: >> >> That is very cool. But I need to ask the tough question - given that the feature freeze was three weeks ago, what do we gain by adding this in Pharo 4? >> >> * Is it needed for demonstrations that won't be based off latest features in Pharo 5 ? >> >> * Are third party libraries expected to be based only off Pharo 4 MetaLink features, rather than additional MetaLink features it sounds like Pharo 5 will get ? >> >>> which means this slice should not impact anything >> >> Because "should" being the operative word... is a slippery slope. If we have a philosophy of freezing features before a Release, then we should have the discipline to hold to that - at least in last 7 days before Release. >> > > Yes, maybe we should postpone itâ¦ releasing is boring, I have to admit :-) > I will revert the change in the visitorâ¦ this way we are sure that we do not get any problems. https://pharo.fogbugz.com/f/cases/15207/Undo-compiler-change-from-case-15196 <https://pharo.fogbugz.com/f/cases/15207/Undo-compiler-change-from-case-15196> I am really looking forward to that in Pharo5â¦ it is (one of my) largest mistakes that after my PhD I did not focus on getting Reflectivity into Pharoâ¦ it is still amazing, even 5 years later, I think. (but I am biased ;-) Marcus

March 22, 2015

What do we do: 14198 Time>>print24 prints nanos, though it claims not to

by Marcus Denker

Hi, what do we do with this: https://pharo.fogbugz.com/f/cases/14198/Time-print24-prints-nanos-though-it… We intergrated it even the last comment before integrating started with "I still don't agree totally (with the solution, I do see there is an issue).â Do we revert it? Is is good enough? Marcus

March 22, 2015

Re: [Pharo-dev] Basic inspect not working

by Marcus Denker

I will open an issue. > On 22 Mar 2015, at 13:41, Nicolai Hess <nicolaihess(a)web.de> wrote: > > Did we miss the postload for issue 15182?

March 22, 2015

Re: [Pharo-dev] Basic inspect not working

by Marcus Denker

> On 22 Mar 2015, at 13:41, Nicolai Hess <nicolaihess(a)web.de> wrote: > > Did we miss the postload for issue 15182? > Basic Inspect gives > PharoCommonTools(Object)>>doesNotUnderstand: #basicInspector > > Yes.

March 22, 2015

Re: [Pharo-dev] Upgrading Fuel Data

by Sean P. DeNigris

> I hope this makes image migrations a bit easier Thanks! Iâm sure it will :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Upgrading-Fuel-Data-tp4809243p4814076.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 22, 2015