October 2008 - Pharo-dev - lists.pharo.org

[Pharo-project] Linux VM build files.

by bryce＠kampjes.demon.co.uk

The make files I ended up with are here: http://ftp.squeak.org/Exupery/vms/freetypeMakeFiles.tz They're not ideal but should work on all Unix platforms with gmake. Given they're only for building on Unix that's probably good enough for now. And they're heavily commented because they're not ideal. I've also incorporated the rest of the image building necessary for FreeType into the exupery-dev Universes project. I've created a FreeType Plus-Core package and a Refactoring Tests package. The FreeType Plus-Core package is to avoid loading the prebuilt freetype plugins as that breaks if the FT2Plugin directory exists beside the VM. The Refactoring Tests is loaded because three of Exupery's tests build on refactoring tests. Feel free to take over these packages. Bryce

Oct. 5, 2008

Re: [Pharo-project] [ANN] Pharo web released

by Damien Cassou

On Sun, Oct 5, 2008 at 2:26 PM, Janko MivÅ¡ek <janko.mivsek(a)eranova.si> wrote: > Thank you much Damien, just at the right moment, just at that moment I need > such an image! You have to thank Marcus, he published the right fix at the right moment. Four days ago, I was not able to produce a pharo-web :-). -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

Oct. 5, 2008

Re: [Pharo-project] [ANN] Pharo web released

by Janko MivÅ¡ek

Thank you much Damien, just at the right moment, just at that moment I need such an image! Janko Damien Cassou wrote: > I've just released pharo-web based on Pharo 10087: > http://gforge.inria.fr/frs/download.php/8422/pharo0.1-10087web08.10.1.zip -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

Oct. 5, 2008

[Pharo-project] [ANN] Pharo web released

by Damien Cassou

Hi, I've just released pharo-web based on Pharo 10087: http://gforge.inria.fr/frs/download.php/8422/pharo0.1-10087web08.10.1.zip Bye -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

Oct. 5, 2008

Re: [Pharo-project] [update] 10087

by Adrian Lienhard

On Oct 4, 2008, at 22:14 , StÃ©phane Ducasse wrote: > Excellent > I will continue the etoy curving and look at kernel extension. > > Marcus it would be good if you could have a look at the traits fixes > Apparently adrian told me that I made a mistake :) or wait until I finish it... it's on my todo list (like the world menu). Since I already worked on it I think it makes more sense I finish it and we do not put additional load on Marcus. When its done, however, I would appreciate another person having a look over the changes. Adrian

Oct. 5, 2008

Re: [Pharo-project] Performance observation

by Adrian Lienhard

We use the Squeak VNC server http://www.squeaksource.com/RFB.html, which works very well. Adrian On Oct 4, 2008, at 16:47 , Bill Schwab wrote: > Hello all, > > As part of some catch-up work from a couple of weeks ago, I'm using my > 1.8 GHz/500MB Ubuntu box and a remote desktop client to do some > configuration on a win2k3 VM running on a blade server on campus. By > many standards, I am using a pig-slow machine jumping through lots of > hoops to reach a machine that has only part of a CPU at the other end. > > One striking thing is that the remote desktop client on Ubuntu is > putting its Windows XP counter part to shame for speed for most > things; > the XP client drags on everything; this is generally (almost) snappy, > and much nicer to use as result. The XP box in my office, IIRC, is a > 3.x GHz machine (faster than what I am using now to be sure); it too > might have "only" 500MB of RAM - I can check that later if it matters. > > The client is clearly optimizing window moves and at least some > scrolling operations, uncoverings, etc. Pharo running over there > looks > comparatively slow, no doubt because ever windowing operation is > seen as > a change to the on main window. I do not know what to make of it, > other > than it might be a argument in favor of one native window per system > window. > > Just thought I'd mention it. > > Bill > > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 5, 2008

[Pharo-project] about class abtractness

by StÃ©phane Ducasse

I would really like to have a way to specify that a class is abstract. For example I would like to be able to write a test as follow self assert: (Collection allSubclasses reject: [:each each isAbstract ]) new isEmpty now saying that isAbstract is if a class has one method sending subclassResponsibility is not really good for me. May be we could have something like isAbstract ^ self declaredAsAbstract or: [ (self whichSelectorsReferToSymbol: #subclassResponsibility) isEmpty not] Stef

Oct. 5, 2008

[Pharo-project] about ifEmptyOrNil:

by StÃ©phane Ducasse

Hi I would like to have your take on that one: isEmpty "Answer whether the receiver contains any elements." ^self size = 0 Why do we need ifEmptyOrNil: isEmptyOrNil "Answer whether the receiver contains any elements, or is nil. Useful in numerous situations where one wishes the same reaction to an empty collection or to nil" ^ self isEmpty why can we use isEmpty: or ifEmpty: aBlock ifEmpty: aBlock "Evaluate the block if I'm empty" ^ self isEmpty ifTrue: aBlock Then from an implementation point of view ifEmptyOrNil: is bogus since it never returns nil (or should not and is also ill-specified). I checked ANSI and this is really a boolean. I'm the mood to deprecate this method. Stef

Oct. 5, 2008

[Pharo-project] about idiots :)

by StÃ©phane Ducasse

Hi marcus Try to stop thinking that making errors is bad. This is a christian ideology that may block your way of looking at the world in a open way. You know like "good and bad". (Watch for example Spirit away for example I'm always fascinated by the fact that we are looking for who are the good and bad). Oscar would say "live and learn". Making error is part of life. Period! Being stupid is when - you repeat errors without learning from them. - if you would not take action after. So introducing a bug is NOT A PROBLEM and nobody is stupid. We are dealing with a really complex program. We will do mistakes, many in fact. We may break the system and put it on its knees. But we will learn and fix or rollback. Easy in computer world we clone duplicate. Imagine it you would be a drawer on expensive paper with ink that you cannot erase!! Simple. So marcus dont be stupid to think that people making mistakes are idiots. They are not! You and me are far from stupid and we will do mistakes. For sure and we will learn from them. Pharo is the proof of it :) So do not let you fun gets spoiled by this oversimplistic view on the world. Stef PS: bookmark this mail because this is the last one on that topics.! When you feel idiots read it. PSPS: one young guy at IBM made IBM lost 1 Millions dollars, so he can to see his boss to resign. The boss said no way, we reject this, we invested on you 1 Million dollars. Nice!

Oct. 5, 2008

Re: [Pharo-project] Some clearifications

by Norbert Hartl

On Sat, 2008-10-04 at 23:29 +0200, Marcus Denker wrote: > Hi, > > Maybe I need to make some thing clear > > 1) There will be mistakes. > Yep, change includes mistake! > When integrating bugfixes and enhancements, it is impossible to not > make mistakes. > The problem is that one can not check every single fix, this is just > not possible. And even > if it would be checked line-by-line and very closely, there would be > new bugs. It is just impossible > that this does not happen. > > The problem is of course that the people doing the integration > everytime a bug is introduced look > (and feel) like idiots. > It would help if people would not strengthen this feeling... if I do > something where I feel like an > idiot most of the time, at some point I will stop. > Uhhh, is it that? I didn't read that much complaints on the list. Marcus, you are doing an incredible job!! And my feeling is that you are _really_ fast integrating stuff. Seeing that it is embarrassing for me as I don't find any time to do something for pharo at the moment. > 2) There is only limited time. > > We can not look at every submission directly, we can not fix every bug > (even those introduced recently) > very fast. This does not mean that we don't like the person who > submited something (or that this person > did something wrong). It *especially* does not mean to discriminate > againt projects. e.g. if Seaside can't > be loaded because of somet stupid bug, this does not mean that seaside > is not wanted or something like that. > > 3) There is a lot of stuff that should be done > ... and the only reason it is not done is lack of time. It's not > because we are idiots. > I think we should build this community on trust. Trusting submissions of community members is not something bad in my opinion. It's not your job to check everything very deeply. It is the job of everyone to review updates/changes and to test them. Taking all together I think we need to split upstream. As long as there is only one upstream you can't check that _before_ it gets published. And people see a version in the upstream as the next stable thing. So we need a side channel for integration and testing. Norbert

Oct. 5, 2008