- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Optimize Pharo for slow horse

by Hilaire Fernandes

Thanks Levente for your tips, they will be useful! Hilaire

July 14, 2010

[Pharo-project] [ANN] SimpleLogger released

by GermÃ¡n Arduino

Hi: Frequently I need to log operations on text files for things I develop for my customers. I released now a tool (VERY simple) that I use to do so. I hope may be useful to someone. The url is http://www.squeaksource.com/SimpleLogger.html Cheers. GermÃ¡n.

July 13, 2010

Re: [Pharo-project] Optimize Pharo for slow horse

by StÃ©phane Ducasse

yes what I imply is that we do not want to have the runtime semantics changed because of a type system. Stef On Jul 13, 2010, at 5:05 PM, Johan Fabry wrote: > > Sorry, I did not invent the terminology, we'll just have to do with this ... > > On 12 Jul 2010, at 16:45, StÃ©phane Ducasse wrote: > >> instead of gradual typing I prefer the term pluggable types because it is really clear what it means. >> >> On Jul 12, 2010, at 10:03 PM, Johan Fabry wrote: >> >>> >>> Gradual typing could help there, doing optimisations where possible. Eric has a PhD student (Oscar) working on gradual typing, with Pharo as the test bed. Next semester there should start a second one with me (Esteban) that is going to look at the vm side of things: if type info is available, use it to optimise ... >>> >>> So, we are working on it ;-) >> > > -- > Johan Fabry > jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry > 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

July 13, 2010

Re: [Pharo-project] Cleaning morphic?

by StÃ©phane Ducasse

Hi I got a flu last week. :) Now how to proceed: step by step :) Start little do it often. So what I suggest is that you go one fix at a time, you send it to the list, open a ticket, people get a chance to argue and we loop million of times. For example - I would like to understand if they are not things to be changed now that we have true bloclosure - for menu opening... like PluggableXXXX and fix that - I would like to have less subclass of StringHolder :) - Something good would be to check the fix Juan did in CUIS for the scrollbars and friends. Yes cleaning morphic is important. > I know morphic is one of the greatest issues Squeak and Pharo have. And I'm tired of the kilometric morph hierarchies with tons of methods that noone uses, and the impossible traceability of the morphic code... > > And I'm sure that a lot of people tried it before... And this isn't the highest priority. But I think morphic cleansing should be done. > > So, while i'm now in bed beacause of a flu, hehe, I want at least remove unused morph classes and unused methods... Or maybe we can separate some things from the core. Of course I will be "spamming" in the list asking for the changes I will do :P. > > what do you think? Do I open a ticket? > > Guille > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 13, 2010

Re: [Pharo-project] Ryerson University, Toronto

by StÃ©phane Ducasse

On Jul 13, 2010, at 5:21 PM, Chris Cunnington wrote: > Last night was a meeting of the Toronto Smalltalk Users Group. It was made clear to me that our host for the meetings (who wasn't there, because we meet on a patio in summer) at Ryerson University, Dr. Joshua Panar had chosen Pharo to introduce to his second year programming students. > > http://www.scs.ryerson.ca/~jpanar/ > > I pushed for Squeak and run over by Bob and Yanni. This is foul perfidy on their part of which they have not heard the last. > > It seems to me that a lot could be accomplished if somebody from the Pharo executive could send Josh some sort of email of introduction. He is in a position to do a lot for Pharo, and a single email from somebody on your side would doubtlessly energize him a great deal. I think he'd find that very encouraging. He's a very nice guy. ***Excellent***! I will contact him I converted all my lectures to powerpoint so that people can freely use them. http://stephane.ducasse.free.fr/Tmp/PowerPoint/ > > Chris > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 13, 2010

[Pharo-project] [ANN] new config versions for Seaside30, Grease, Magritte2, Pier2, Pier2AddOns

by Dale Henrichs

ConfigurationOfGrease - 1.0-alpha9.3 ConfigurationOfSeaside30 - 3.0.0-alpha5.15 ConfigurationOfMagritte2 - 2.0.5 ConfigurationOfPier2 - 2.0.6 ConfigurationOfPierAddOns2 - 2.0.6 ConfigurationOfSeaside - 1.0.5 The configurations are available in http://www.squeaksource.com/MetacelloRepository. Note that the mcz files in the Seaside3.0 config predates the mcz files in 3.0 RC that was recently announced, so I apologize for the potential confusion. We are shipping GemStone/S 64 2.4.4.1 very soon now and I needed to coordinate the releases of Seaside3.0/Magritte2/Pier2 that are available on GemStone. The announcement of 3.0 RC came too late to incorporate into our release cycle. I'll be pushing out updated configs shortly. The big change with this release is that there is a new 'Base' group defined that loads the minimal packages for running Seaside (i.e., no development packages, no examples, no java script. etc.) thus making it possible to perform a load into a production image of only the packages/features you want. The new versions of the Magritte2, Pier2 and PierAddOns2 are structured to load only what is absolutely needed for each of those projects, again making it possible to load Pier2 into an image without having the entire Seaside3.0 development come along. One of the upshots of loading only the minimum required is that you will need to choose an adaptor to explicitly load (Kom or Swazoo for Pharo/Squeak folks). So if you want to load a minimal Pier2 and use the Kom adaptor, you will evaluate an expression like the following (after loading the Seaside3.0 and Pier2 configurations: (ConfigurationOfPier2 project version: '2.0.6') load. (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') load: #( 'Seaside-Adaptors-Comanche' ). If you want to add the Seaside3.0 development environment to your image, you would evaluate the following: (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') load: #( 'Development' ). and if you wanted the development environment plus tests you'd evaluate the following: (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') load: #( 'Development Tests' ). As for the ConfigurationOfSeaside, I have decided that the 'Seaside 3.0' target will load the full Seaside3.0 code base. However, I have added a 'Seaside 3.0 Production' target that loads the minimal Seaside packages plus both adaptors. I have updated the #workspace method with additional examples. For the GemStone users out there keep your eyes peeled for the announcement of GemStone/S 64 2.4.4.1 where I will provide additional (mostly) GemStone-specific information. Well with as many moving pieces involved in this announcement I expect that there will be a stitch or two dropped (which reminds me that you ought to make sure you are using the latest version of Metacello when loaded Seaside3.0) so feel free to drop me a line with comments/problems and I will see if I can address them. Now that GemStone has caught up with Pharo and Squeak (very soon, I promise:) I don't anticipate making these multi-config coordinated releases any time soon... Putting together a Seaside 3.0 RC config is next up on the list... Dale

July 13, 2010

[Pharo-project] Ryerson University, Toronto

by Chris Cunnington

Last night was a meeting of the Toronto Smalltalk Users Group. It was made clear to me that our host for the meetings (who wasn't there, because we meet on a patio in summer) at Ryerson University, Dr. Joshua Panar had chosen Pharo to introduce to his second year programming students. http://www.scs.ryerson.ca/~jpanar/ I pushed for Squeak and run over by Bob and Yanni. This is foul perfidy on their part of which they have not heard the last. It seems to me that a lot could be accomplished if somebody from the Pharo executive could send Josh some sort of email of introduction. He is in a position to do a lot for Pharo, and a single email from somebody on your side would doubtlessly energize him a great deal. I think he'd find that very encouraging. He's a very nice guy. Chris

July 13, 2010

Re: [Pharo-project] Optimize Pharo for slow horse

by Johan Fabry

Sorry, I did not invent the terminology, we'll just have to do with this ... On 12 Jul 2010, at 16:45, StÃ©phane Ducasse wrote: > instead of gradual typing I prefer the term pluggable types because it is really clear what it means. > > On Jul 12, 2010, at 10:03 PM, Johan Fabry wrote: > >> >> Gradual typing could help there, doing optimisations where possible. Eric has a PhD student (Oscar) working on gradual typing, with Pharo as the test bed. Next semester there should start a second one with me (Esteban) that is going to look at the vm side of things: if type info is available, use it to optimise ... >> >> So, we are working on it ;-) > -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

July 13, 2010

Re: [Pharo-project] Optimize Pharo for slow horse

by Johan Fabry

As far as I can see, he is in the formalizing (a subset of) Smalltalk phase. We must be patient, such formal stuff cannot be hurried ;-) On 12 Jul 2010, at 16:45, StÃ©phane Ducasse wrote: > I would love to hear more about oscar. I would love to know where the libraries could be improved to have more coherent type information. > I told him when I visited you but so far we got no feedback. We will see if there are some results. > > Stef > >> >> Gradual typing could help there, doing optimisations where possible. Eric has a PhD student (Oscar) working on gradual typing, with Pharo as the test bed. Next semester there should start a second one with me (Esteban) that is going to look at the vm side of things: if type info is available, use it to optimise ... >> >> So, we are working on it ;-) > -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

July 13, 2010

Re: [Pharo-project] Cleaning morphic?

by Levente Uzonyi

On Tue, 13 Jul 2010, Guillermo Polito wrote: > I know morphic is one of the greatest issues Squeak and Pharo have. And I'm > tired of the kilometric morph hierarchies with tons of methods that noone > uses, and the impossible traceability of the morphic code... You can't be sure that a method or class is not used if you only look at the senders or users. Morphic uses a lot of automatic generated selectors combined with #perform:withArguments: (and friends) which makes it very hard to track down senders. Though checking the senders of #asSymbol can help. Levente > > And I'm sure that a lot of people tried it before... And this isn't the > highest priority. But I think morphic cleansing should be done. > > So, while i'm now in bed beacause of a flu, hehe, I want at least remove > unused morph classes and unused methods... Or maybe we can separate some > things from the core. Of course I will be "spamming" in the list asking for > the changes I will do :P. > > what do you think? Do I open a ticket? > > Guille >

July 13, 2010