June 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Pharo-2.0-Tests Â» 32,mac - Build # 130 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

June 18, 2012

[Pharo-project] Pharo-2.0-Tests Â» 32,linux - Build # 130 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

June 18, 2012

[Pharo-project] squeaksource is down (eom)

by Chris Muller

June 18, 2012

Re: [Pharo-project] Mouse down events are being processed twice

by Sven Van Caekenberghe

Thanks for all the effort, Sean, it is really nice to see you contributing so much lately. Sven On 18 Jun 2012, at 16:37, Sean P. DeNigris wrote: > This was the reason for the scrollbars scrolling two rows/pages at a time. I > merged that issue into the one below. If someone will review the fix (only > one line changed), it is ready for 1.4 (all relevant tests pass - two > unrelated failures) and 2.0... > > Issue 6083: Mouse down events are being processed twice > http://code.google.com/p/pharo/issues/detail?id=6083 > > Fixes in inbox: > - for 1.4: > SLICE-Issue-6083-Mouse-down-events-are-being-processed-twice-SeanDeNigris.1 > - for 2.0: > SLICE-Issue-6083-Mouse-down-events-are-being-processed-twice-SeanDeNigris.2 > > * Fix Morph>>#handleMouseDown: to have #mouseDown:fromMorph: called only > once, via #mouseDown: > > -- > View this message in context: http://forum.world.st/Mouse-down-events-are-being-processed-twice-tp4635339… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

June 18, 2012

Re: [Pharo-project] Mouse down events are being processed twice

by StÃ©phane Ducasse

thanks sean On Jun 18, 2012, at 4:37 PM, Sean P. DeNigris wrote: > This was the reason for the scrollbars scrolling two rows/pages at a time. I > merged that issue into the one below. If someone will review the fix (only > one line changed), it is ready for 1.4 (all relevant tests pass - two > unrelated failures) and 2.0... > > Issue 6083: Mouse down events are being processed twice > http://code.google.com/p/pharo/issues/detail?id=6083 > > Fixes in inbox: > - for 1.4: > SLICE-Issue-6083-Mouse-down-events-are-being-processed-twice-SeanDeNigris.1 > - for 2.0: > SLICE-Issue-6083-Mouse-down-events-are-being-processed-twice-SeanDeNigris.2 > > * Fix Morph>>#handleMouseDown: to have #mouseDown:fromMorph: called only > once, via #mouseDown: > > -- > View this message in context: http://forum.world.st/Mouse-down-events-are-being-processed-twice-tp4635339… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

June 18, 2012

[Pharo-project] Mouse down events are being processed twice

by Sean P. DeNigris

This was the reason for the scrollbars scrolling two rows/pages at a time. I merged that issue into the one below. If someone will review the fix (only one line changed), it is ready for 1.4 (all relevant tests pass - two unrelated failures) and 2.0... Issue 6083: Mouse down events are being processed twice http://code.google.com/p/pharo/issues/detail?id=6083 Fixes in inbox: - for 1.4: SLICE-Issue-6083-Mouse-down-events-are-being-processed-twice-SeanDeNigris.1 - for 2.0: SLICE-Issue-6083-Mouse-down-events-are-being-processed-twice-SeanDeNigris.2 * Fix Morph>>#handleMouseDown: to have #mouseDown:fromMorph: called only once, via #mouseDown: -- View this message in context: http://forum.world.st/Mouse-down-events-are-being-processed-twice-tp4635339… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 18, 2012

Re: [Pharo-project] start thinking on summer release of Pharo 1.4

by Ben Coman

There is also (http://ycombinator.com) particularly if you can do any of these... (http://ycombinator.com/ideas.html) The first link of the FAQ is very informative but quite long. Not that these startup funds would fund Pharo directly, but perhaps someone using Pharo as a competitive advantage. phil(a)highoctane.be wrote: > BTW what did Mozilla FWD told you? > https://webfwd.org/ > > 2012/6/17 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> Phil >> >> just for the record, if we would get 4 engineers working full time during 2 more years >> you would not recognize Pharo. >> Now we are making progress but we are nearly all working on our free time. >> So this is not that we do not have the vision, just not enough money :). >> >> Stef >> >> >> On Jun 17, 2012, at 9:42 PM, phil(a)highoctane.be wrote: >> >> >>> Don't get me wrong. I love all of what I do see in there. I've done a >>> ton of Maven2 stuff (including setting up a quite large maven proxy), >>> so I perfectly understand the ton of hard work that goes along with >>> configs. Much important, much needed, much significant work. >>> >>> Just that I am running a business and want to make Pharo a cornerstone >>> of my technical tools. >>> >>> This means that I'll have to explain it to a lot of people partnering >>> with me. I need traction to pull them in. >>> >>> There is incredible potential in Pharo. Just that for the newcomer, >>> the paradigm switch to an image-based beast is big enough to smoothen >>> the curve. And we can do it. >>> >>> Phil >>> >>> >>> >>> 2012/6/17 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: >>> >>>> I have been a vocal critic of configs, largely on grounds of excessive complexity, but I find your message a bit harsh. >>>> >>>> Long delays and hangs are BAD, but that can be addressed using background threads. This is a prime example of why say that sockets should never block the entire image (only calling thread) and should not have anything to say about timeouts - the latter are an app programming/user decision. >>>> >>>> The list of configs appearing in the browser is encouraging. I'd hope to see ODBC listed too, but Glorp is there. If all of these configs offer and can load a #stable version, that would be huge progress. >>>> >>>> Bill >>>> >>>> >>>> ________________________________________ >>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of phil(a)highoctane.be [phil(a)highoctane.be] >>>> Sent: Sunday, June 17, 2012 6:44 AM >>>> To: Pharo-project(a)lists.gforge.inria.fr >>>> Subject: Re: [Pharo-project] start thinking on summer release of Pharo 1.4 >>>> >>>> Who is his/her right mind would be able to make sense of this without >>>> a lot of preexposure? And who the hell are those people? >>>> >>>> And figuring out they need to right click, followed by a load >>>> configuration *and* stable version? Followed by a loooong wait. And if >>>> there is no internet, well, it would freeze for a significant while. >>>> >>>> That's the feedback I get from people I try to get into the flow. Lots >>>> of blank stares... along the lines of "What the heck are you doing?" >>>> >>>> Phil >>>> >>>> >>>> 2012/6/17 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>> >>>>> On Jun 17, 2012, at 5:10 AM, Ben Coman wrote: >>>>> >>>>> >>>>>> Is Nautilus under any consideration to be the default browser for your summer release at all, or are you firmly committed to OB? >>>>>> I need to know this to continue updating Pharo By Example for 1.4. >>>>>> >>>>> this is an interesting and important issue (much more than codenames, he). >>>>> I will extend my latest answer, using what I know (maybe Benjamin has another idea, and would be good to know it): >>>>> >>>>> Nautilus is in development, there are some important functionalities that are not there yet, and some others that does not work properly. Refactors and Traits is the most important things I can think of now, but there are probably more. >>>>> Also, Nautilus relies in RPackage, which was not ready for 1.4 (but will be ready for 2.0). And some other packages (like OB itself) can be not-loadable after installing Nautilus. >>>>> To make all of this work in 1.4 can be a huge job (at least for RPackage, it is, I don't know for Nautilus). I know that RPackage cannot be backported without a lot of effort, but I don't know if Nautilus for 1.4 can be adapted to not use RPackage easily (which AFAIK, should be necessary to make it work propertly). >>>>> >>>>> So, I will like your work (which is IMO terribly important) would take Nautilus. But I also think that loading it for default in 1.4 is probably too much. >>>>> Frankly, I don't know what to do now :) >>>>> >>>>> Esteban >>>>> >>>> >>>> -- >>>> Philippe Back >>>> Dramatic Performance Improvements >>>> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >>>> phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >>>> http://philippeback.be >>>> >>>> High Octane SPRL >>>> rue cour Boisacq 101 >>>> 1301 Bierges >>>> Belgium >>>> >>>> >>> >>> -- >>> Philippe Back >>> Dramatic Performance Improvements >>> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >>> phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >>> http://philippeback.be >>> >>> High Octane SPRL >>> rue cour Boisacq 101 >>> 1301 Bierges >>> Belgium >>> >>> >> > > > >

June 18, 2012

Re: [Pharo-project] Wrong gofer command in ss3 gemstone

by Guillaume Larcheveque

Ok, sorry for inconvenience. 2012/6/18 Tobias Pape <Das.Linux(a)gmx.de> > Hi Guillaume > > Am 18.06.2012 um 11:07 schrieb Guillaume Larcheveque: > > > In the section "Getting the code" for a project, > > > > the displayed command should be: "Gofer new > > squeaksource3: 'MyProject'; > > package: 'MyPackage'; > > load" > > > > It should be useful to correct that to avoid searching the correct > syntax. > > > The error is known and fixed in code but not yet deployed. > Dale and me are short of time currently; please be patient until > we upgraded ss3. > > Best > -Tobias > > > > > -- *Guillaume Larcheveque*

June 18, 2012

Re: [Pharo-project] Look and font competition

by Henrik Sperre Johansen

On 10.06.2012 10:27, StÃ©phane Ducasse wrote: > Hi guys > > this morning Igor shows me all his work around dynlib loading of third party plugins. > And yes now we get all the third party plugins downloaded and compiled (yes with only one copy of FT2)â¦.Great stuff! > > Now we would like to organize a little competition for the official look of Pharo 2.0. So if you feel that you are a little > bit designer inside, please send us proposals. > We propose this one :) based on Curlz MT (welcome to the world of the pink little ponies) :) > > Both license-wise, unicode coverage-wise, as well as aesthetically speaking, I still think DejaVu is a very good default font choice. Cheers, Henry

June 18, 2012

Re: [Pharo-project] Wrong gofer command in ss3 gemstone

by Tobias Pape

Hi Guillaume Am 18.06.2012 um 11:07 schrieb Guillaume Larcheveque: > In the section "Getting the code" for a project, > > the displayed command should be: "Gofer new > squeaksource3: 'MyProject'; > package: 'MyPackage'; > load" > > It should be useful to correct that to avoid searching the correct syntax. The error is known and fixed in code but not yet deployed. Dale and me are short of time currently; please be patient until we upgraded ss3. Best -Tobias

June 18, 2012