- Pharo-dev - lists.pharo.org

[Pharo-project] Shadowing the ivar by temps in Pharo

by Igor Stasenko

This is not first time, i discovering that Pharo silently accepts the methods which having argument/temp names same as intance variable names. Squeak 3.10, however warns about it, upon installation and prevents edited method to be accepted until this is fixed. -- Transcript -- (doubleBuffered is shadowed in "GLDisplayScreen") (depth is shadowed in "GLDisplayScreen>>#glEnableMainWindowContext:") Is this a bug or feature? -- Best regards, Igor Stasenko AKA sig.

July 30, 2009

Re: [Pharo-project] SmalltalkImage current platformName [WAS] Re: Baseline test results on pharo core 10392

by Igor Stasenko

2009/7/30 Igor Stasenko <siguctua(a)gmail.com>: [snip ] > right, this is what i'm actually proposing.. use it in a way like: > > menuBuilder := OSProcess platformMenuBuilder. > > menuBuilder ifNotNil: [ > Â menuBuilder addMenu: #('File Edit Help Other Boring Stuff')... > ] > err.. OSPlatform, not OSProcess :) -- Best regards, Igor Stasenko AKA sig.

July 30, 2009

Re: [Pharo-project] SmalltalkImage current platformName [WAS] Re: Baseline test results on pharo core 10392

by Igor Stasenko

2009/7/30 Douglas Brebner <squeaklists(a)fang.demon.co.uk>: > Andreas Wacknitz wrote: >> >> Am 29.07.2009 um 21:13 schrieb Mariano Martinez Peck: >> >>> >>> >>> On Wed, Jul 29, 2009 at 6:06 PM, Andreas Wacknitz <A.Wacknitz(a)gmx.de >>> <mailto:A.Wacknitz@gmx.de>> wrote: >>> >>> >>> Â Â Am 29.07.2009 um 20:08 schrieb Marcus Denker: >>> >>> >>> >>> Â Â sooner or later. And I can't see that >>> Â Â Â Â Â Â OSPlatform current isMacOSX >>> Â Â is really that much better than >>> Â Â Â Â Â Â SmalltalkImage current platformName = 'Mac OS' >>> >>> >>> >>> Yes it is. I it is not MUCH better, but a bit better and easy to >>> implement. Tomorrow the platform name changes and you have to change >>> your code all over the image. At least, with this, you have the >>> hardcoded in a single place. After this, with a single "senders" you >>> can see where it is used and how to modify this for a more OO stuff. >> >> I beg to disagree. First, you could also search for senders of >> "platformName". Second, what to do when you need to add a new platform? >> At the moment there is "isUnix". But there might be differences >> between Linux, Solaris, RiscOS, FreeBSD, ... > There can be considerable differences. e.g. the gnu tools used by Linux > have different command line options from the BSD tools which could > impact things like OSProcess. >> You don't want a single search and multiple change but a single search >> AND change. >> In my opinion the proposed code is only a minor improvement. >> >> > Maybe one possible solution would be to select on features, e.g. > something like PlatformFeatures>>#menuSupport? I believe Common Lisp > does something like that with their *features* variable. > right, this is what i'm actually proposing.. use it in a way like: menuBuilder := OSProcess platformMenuBuilder. menuBuilder ifNotNil: [ menuBuilder addMenu: #('File Edit Help Other Boring Stuff')... ] > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

July 30, 2009

Re: [Pharo-project] Making GLMorphic plugin work in Pharo

by Igor Stasenko

Btw the last thing i added is Frame Buffer Object extension (see GLFboBuffer & friends). It is not tested very well, and not integrated with GLCanvas. FBOs, if they are available, can be used to render into texture as if you render on screen. I planned to use it for caching the window contents when you dragging it.. there , of course, many other use cases. -- Best regards, Igor Stasenko AKA sig.

July 30, 2009

Re: [Pharo-project] Beginner Tasks

by Douglas Brebner

Serge Stinckwich wrote: > 2009/7/30 Simon Denier <Simon.Denier(a)inria.fr>: > >> Stef is talking of http://www.squeaksource.com/TestServerSimple.html >> Now this is a rather rudimentary adaptation from a tool made by Swiss guys. >> It runs automatically when launching the image, loads packages and runs >> tests for different projects. >> Right now it is tailored for Moose projects >> I guess that the area that need improvements are: >> - configuration of projects to load, with prerequisites (using Metacello >> perhaps?). Right now this is hard-coded, see TSProject class>>run >> - headless running (sometimes some interactive dialogs still pop up, >> especially when there is a problem loading a package, and this ruins the >> automatization) >> - better handling of errors (problems such as above) >> > > What could be nice is a build server like this one : > https://hudson.dev.java.net/ > Look here for a running example: http://build.willowgarage.com/ > > Don't we already have a build server in the form of Keiths Bob & Sake? It even has a Seaside interface.

July 30, 2009

Re: [Pharo-project] Beginner Tasks

by Serge Stinckwich

2009/7/30 Simon Denier <Simon.Denier(a)inria.fr>: > Stef is talking ofÂ http://www.squeaksource.com/TestServerSimple.html > Now this is a rather rudimentary adaptation from a tool made by Swiss guys. > It runs automatically when launching the image, loads packages and runs > tests for different projects. > Right now it is tailored for Moose projects > I guess that the area that need improvements are: > - configuration of projects to load, with prerequisites (using Metacello > perhaps?). Right now this is hard-coded, see TSProject class>>run > - headless running (sometimes some interactive dialogs still pop up, > especially when there is a problem loading a package, and this ruins the > automatization) > - better handling of errors (problems such as above) What could be nice is a build server like this one : https://hudson.dev.java.net/ Look here for a running example: http://build.willowgarage.com/ -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

July 30, 2009

Re: [Pharo-project] SmalltalkImage current platformName [WAS] Re: Baseline test results on pharo core 10392

by Douglas Brebner

Andreas Wacknitz wrote: > > Am 29.07.2009 um 21:13 schrieb Mariano Martinez Peck: > >> >> >> On Wed, Jul 29, 2009 at 6:06 PM, Andreas Wacknitz <A.Wacknitz(a)gmx.de >> <mailto:A.Wacknitz@gmx.de>> wrote: >> >> >> Am 29.07.2009 um 20:08 schrieb Marcus Denker: >> >> >> >> sooner or later. And I can't see that >> OSPlatform current isMacOSX >> is really that much better than >> SmalltalkImage current platformName = 'Mac OS' >> >> >> >> Yes it is. I it is not MUCH better, but a bit better and easy to >> implement. Tomorrow the platform name changes and you have to change >> your code all over the image. At least, with this, you have the >> hardcoded in a single place. After this, with a single "senders" you >> can see where it is used and how to modify this for a more OO stuff. > > I beg to disagree. First, you could also search for senders of > "platformName". Second, what to do when you need to add a new platform? > At the moment there is "isUnix". But there might be differences > between Linux, Solaris, RiscOS, FreeBSD, ... There can be considerable differences. e.g. the gnu tools used by Linux have different command line options from the BSD tools which could impact things like OSProcess. > You don't want a single search and multiple change but a single search > AND change. > In my opinion the proposed code is only a minor improvement. > > Maybe one possible solution would be to select on features, e.g. something like PlatformFeatures>>#menuSupport? I believe Common Lisp does something like that with their *features* variable.

July 30, 2009

Re: [Pharo-project] Bugreports... the numbers

by Tudor Girba

Nice numbers :). At this rate you have about 26 days until the final release :). Keep it up! Doru On 29 Jul 2009, at 23:24, Marcus Denker wrote: > Entries in the Bugracker: 1004 > Closed: 798 > > open: 206 > open, tagged 1.0: 49 > > First bug filed: Jun 05, 2008 > (Date today - 'Jun 05, 2008' asDate) days --> 419 > > That makes 1.9 closed reports per day. Not bad! > > Marcus > -- > Marcus Denker - http://marcusdenker.de > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Be rather willing to give than demanding to get."

July 29, 2009

[Pharo-project] Bugreports... the numbers

by Marcus Denker

Entries in the Bugracker: 1004 Closed: 798 open: 206 open, tagged 1.0: 49 First bug filed: Jun 05, 2008 (Date today - 'Jun 05, 2008' asDate) days --> 419 That makes 1.9 closed reports per day. Not bad! Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

July 29, 2009

Re: [Pharo-project] Beginner Tasks

by Michael Roberts

for the moment you don't need to load any project related code. a simple test server would 1a) download the latest published core image from inria or 1b) load all the available updates into the last image downloaded, save image locally 2) file in the baseline test code & run the tests (done - see wiki) 3) publish the results to the wiki cheers, Mike 2009/7/29 Simon Denier <Simon.Denier(a)inria.fr>: > Stef is talking ofÂ http://www.squeaksource.com/TestServerSimple.html > Now this is a rather rudimentary adaptation from a tool made by Swiss guys. > It runs automatically when launching the image, loads packages and runs > tests for different projects. > Right now it is tailored for Moose projects > I guess that the area that need improvements are: > - configuration of projects to load, with prerequisites (using Metacello > perhaps?). Right now this is hard-coded, see TSProject class>>run > - headless running (sometimes some interactive dialogs still pop up, > especially when there is a problem loading a package, and this ruins the > automatization) > - better handling of errors (problems such as above) > > On 29 juil. 09, at 18:46, Robert Peters wrote: > > What is this "testServer" you are talking about? Â I searched this forum a > little bit but didn't find any information on it. > > I write web-apps in Django for Google App Engine, and my current test suite > for a project takes 45 seconds to run. Â This frustrates me because unit > testing is (or, at least, should be) an easily distributed task (as good > unit tests do not depend on each other). Â If Python would even simply use > both cores of my main work computer, my tests would only take 23 seconds, > and if it used all computers on my local network, it could take 5-10 > seconds. Â This would be a huge saving for me. > > All of this to say I have been thinking about a 'test server' that would > take a queue of tests, set up the proper environments on as many cores as it > had available, and send out the tests, collect the responses and display > them. > > Is this what you mean by 'testServer'? > > I have wanted to help Pharo, but being an un-skilled Smalltalk programmer, > and having other Python-based projects that were more urgent, I haven't done > much about it. Â However, this 'testServer' caught my eye, because I've been > thinking about creating such a thing for my own Python-based use. Â Please > let me know if what I propose is what you intend. If so I may be willing to > try and create something for Pharo to use. > > Kind regards, > Robert > > > StÃ©phane Ducasse-2 wrote: > > > - a nicer project would be to help improving the embryonic testServer > > we have > > Stef > > > > -- > View this message in context: > http://n2.nabble.com/Beginner-Tasks-tp3187343p3351068.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Â Simon > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 29, 2009