January 2014 - Pharo-dev - lists.pharo.org

mouse-wheel (on Windows)

by paolo.bernardi.67＠gmail.com

hi all, there are some differences between how vm handles Windows messages of type "mouse-wheel" and all the other ones? It seems to me that primitiveEventProcessingControl suspends vm's message handling, but does not suspend mouse-wheel ones. thanks

Jan. 29, 2014

Re: [Pharo-dev] Where to report bugs?

by Benjamin

On 29 Jan 2014, at 18:52, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > > Still many different agendas busy time. > It does not mean no interest it means that people are busy. If we wait someone has nothing to do, it will never happen :) > But since we all know that we will not move before the release then there is not much point for people > to look at them because they are busy. When we will decide that this is time to look then the right people > will do it. And I was sad that we would have to throw away all the time you spend on it. Except that if we want to change at the same time we release, we should start having a look now. And I do not care throwing away what I did, thatâs life :P > Yes but again busy. > VM, > jenkins > Mate > PhD > Papers > coding > Nautilus > bug fixes > everybody needs free cycles and since december none of us have. > but this is orthogonal to no interest. But itâs a matter of priority. > >>> We do not change the commit tools >>> either. > > This was related to the git story Again, if we want to change soon after the release we should not start to thing about it two month after. Ben

Jan. 29, 2014

Re: [Pharo-dev] Where to report bugs?

by Pharo4Stef

> How many people are doing this? > How big is the team? Still many different agendas busy time. It does not mean no interest it means that people are busy. >> is a long list of duties before even thinking about Pharo. >> >> So we must evaluate our energy before changing to a new architecture. >> And there are always pros and cons. >> >> Evaluating for REAL a new bugtracker is not something that we do in one afternoon. > > Yes I know, that is exactly why I did not send the mail this morning but more than a month ago. But since we all know that we will not move before the release then there is not much point for people to look at them because they are busy. When we will decide that this is time to look then the right people will do it. And I was sad that we would have to throw away all the time you spend on it. >> And we do not do that two months before a release. > > No indeed, but you do it the day after the release. > And as you say, it does not take one afternoon to get an idea if it is good or not. Yes but again busy. VM, jenkins Mate PhD Papers coding Nautilus bug fixes everybody needs free cycles and since december none of us have. but this is orthogonal to no interest. >> We do not change the commit tools >> either. This was related to the git story

Jan. 29, 2014

Re: [Pharo-dev] [Review]: Case 12737 Morph sends mouseUp twice to handlers

by Pharo4Stef

On 29 Jan 2014, at 22:12, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > Filters > My case s(2nd item) Thanks! I found using the customize and I started to review my bug entries and close some of them. I will check the list because I remember that I totally puzzled by the behavior I got. > > Ben > > On 29 Jan 2014, at 18:05, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > >> Thanks >> It reminds a really strange bug I got showing that there were hidden useless calls. but I cannot find if I entered an entry. >> Any idea how I can find the entries that I added to fogbogz >> >> Setf >> On 29 Jan 2014, at 02:47, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >>> https://pharo.fogbugz.com/default.asp?12737 >>> >>> DoIt: >>> Morph new >>> on: #mouseUp send: #inspect to: 1; >>> openInWorld. >>> Two inspectors will appear. >>> >>> Fix in inbox: >>> SLICE-Issue-12737-Morph-sends-mouseUp-twice-to-handlers-SeanDeNigris.1 >>> Please review. It definitely fixes the problem, but it fiddles around inside >>> Morphic so... >>> Test included - fails before, passes after >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: http://forum.world.st/Review-Case-12737-Morph-sends-mouseUp-twice-to-handle… >>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>> >> >> >

Jan. 29, 2014

Re: [Pharo-dev] Where to report bugs?

by Benjamin

On 29 Jan 2014, at 18:19, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > Ben > > - creating a company > - being the head of a research group > - HDR of noury > - PhD of Nick > - Papers there and there > - admin there and there > - dealing with people > - dealing with people > - dealing with people > - having a door always open > - having a door always open > - being second of a lab of 300 researchers > - coding on boring stuff > - working on projects > - thinking about money for the team How many people are doing this? How big is the team? > is a long list of duties before even thinking about Pharo. > > So we must evaluate our energy before changing to a new architecture. > And there are always pros and cons. > > Evaluating for REAL a new bugtracker is not something that we do in one afternoon. Yes I know, that is exactly why I did not send the mail this morning but more than a month ago. > And we do not do that two months before a release. No indeed, but you do it the day after the release. And as you say, it does not take one afternoon to get an idea if it is good or not. > We do not change the commit tools > either. ?? Ben

Jan. 29, 2014

Re: [Pharo-dev] FOSDEM

by Pharo4Stef

Not me even I would have liked so have fun for me :) > Hi Gang, > > So, #FOSDEM is this week-end. > > I looked at the schedule, which looks interesting. > https://fosdem.org/2014/schedule/track/smalltalk/ > > Who's coming apart from the speakers ? > > Phil

Jan. 29, 2014

Re: [Pharo-dev] Where to report bugs?

by Pharo4Stef

Ben - creating a company - being the head of a research group - HDR of noury - PhD of Nick - Papers there and there - admin there and there - dealing with people - dealing with people - dealing with people - having a door always open - having a door always open - being second of a lab of 300 researchers - coding on boring stuff - working on projects - thinking about money for the team is a long list of duties before even thinking about Pharo. So we must evaluate our energy before changing to a new architecture. And there are always pros and cons. Evaluating for REAL a new bugtracker is not something that we do in one afternoon. And we do not do that two months before a release. We do not change the commit tools either. This is like that. Stef On 29 Jan 2014, at 12:44, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > I actually proposed few replacement one month ago inside the RMoD team, > nobody answered except âFogbugz is badâ , and nobody tried what I proposed. > > Exactly what happened when we had to choose a replacement for Google Issue Tracker. > > Ben > > On 29 Jan 2014, at 08:33, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 29 Jan 2014, at 11:32, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: >> >>> I hope weâre not making it harder than it should for fear to feedback >>> >>> >> >> It has already been concluded that fogbugz was a mistake. Itâs just not made >> for an open source project. >> >> Now moving will be *a lot* of work and we have not even found a replacement >> that is scriptable. >> >> We first need to release Pharo3 before we sink indefinite amounts of time into this. >> >> Marcus >

Jan. 29, 2014

Re: [Pharo-dev] [Review]: Case 12737 Morph sends mouseUp twice to handlers

by Benjamin

Filters > My case s(2nd item) Ben On 29 Jan 2014, at 18:05, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > Thanks > It reminds a really strange bug I got showing that there were hidden useless calls. but I cannot find if I entered an entry. > Any idea how I can find the entries that I added to fogbogz > > Setf > On 29 Jan 2014, at 02:47, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> https://pharo.fogbugz.com/default.asp?12737 >> >> DoIt: >> Morph new >> on: #mouseUp send: #inspect to: 1; >> openInWorld. >> Two inspectors will appear. >> >> Fix in inbox: >> SLICE-Issue-12737-Morph-sends-mouseUp-twice-to-handlers-SeanDeNigris.1 >> Please review. It definitely fixes the problem, but it fiddles around inside >> Morphic so... >> Test included - fails before, passes after >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Review-Case-12737-Morph-sends-mouseUp-twice-to-handle… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >

Jan. 29, 2014

Re: [Pharo-dev] [Review]: Case 12737 Morph sends mouseUp twice to handlers

by Pharo4Stef

Thanks It reminds a really strange bug I got showing that there were hidden useless calls. but I cannot find if I entered an entry. Any idea how I can find the entries that I added to fogbogz Setf On 29 Jan 2014, at 02:47, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > https://pharo.fogbugz.com/default.asp?12737 > > DoIt: > Morph new > on: #mouseUp send: #inspect to: 1; > openInWorld. > Two inspectors will appear. > > Fix in inbox: > SLICE-Issue-12737-Morph-sends-mouseUp-twice-to-handlers-SeanDeNigris.1 > Please review. It definitely fixes the problem, but it fiddles around inside > Morphic so... > Test included - fails before, passes after > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Review-Case-12737-Morph-sends-mouseUp-twice-to-handle… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Jan. 29, 2014

Re: [Pharo-dev] No more MouseWheelEvents?

by Pharo4Stef

Simple the VM does not give us the correct events so there are simulated. This is why what igor and ronie did on getting event from the OS via NB is important and a nice experience. It shows that we can move most of the low level stuff to the image and get a lighter VM. Now we need help because this is working for linux X11 but we need it for Mac and Windows. Ronie suggested to use SDL but SDL can be heavy (in terms of API and dependency), Igor suggested that we look at the way SDL is doing it and cheery pick what we need. So basically We need Mac Windows little primitives Mac Window image level classes It would be so great to have a group of people pushing that together. Stef > How it comes we lost the MouseWheelEvents. > The SimpleHierarchicalListMorph in FileList does not scroll on MouseWheelEvents. > Or at least it worked that way in Pharo2. But now the MouseWheel creates > a keyboardevent "<Ctrl->". > (Other ListMorphs can handle this, but the ListMorph in FileList can not.) > > nicolai >

Jan. 29, 2014