March 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fwd: [SoC] Wanted: Google Summer of Code 2009 Mentors and Projects

by Alexandre Bergel

Sure, Stef was already second Mentor. I added you. http://wiki.squeak.org/squeak/6121 Alexandre On 10 Mar 2009, at 17:07, Michael Rueger wrote: > Alexandre Bergel wrote: >> I would like to propose something regarding binary packages. What is > > I would be interested to stay in the loop (secondary mentor?) on > this one. > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 10, 2009

Re: [Pharo-project] Fwd: [SoC] Wanted: Google Summer of Code 2009 Mentors and Projects

by Michael Rueger

Alexandre Bergel wrote: > I would like to propose something regarding binary packages. What is I would be interested to stay in the loop (secondary mentor?) on this one. Michael

March 10, 2009

[Pharo-project] [ANN][Dev-Images] March 2009 versions

by Damien Cassou

Hi, I've just uploaded new dev and web images based on Squeak3.9.1-7075, Squeak3.10.2-7179 and Pharo0.1-10248. More information and download: http://damiencassou.seasidehosting.st/Smalltalk/squeak-dev Pharo-based images can be downloaded at: http://code.google.com/p/pharo/wiki/Downloads?tm=2 Download statistics at http://damiencassou.dabbledb.com/publish/dev-imagesdownloads Changes in this version: --------------------------- - Pharo images are based on version 10248 - 3.9 based images now also have Polymorph installed - Polymorph fixes (by Gary Chambers) - Performance improvements - More tooltips - Added support in UIManager for new choice dialog with message, backwards compatible with other UIManager subclasses - Fix bugs - Code cleanup - (I can send more details by email to those who are interested) - OmniBrowser changes (by David RÃ¶thlisberger) - Integrated Dyanmic Protocols - Moved fixed button panel to the top, next to mercury panel - Improved layout and appearance to comply with Polymorph - Improved performance (caching of class cats in tree) - Columns get focus on mouse over (preference) - Code quality improvings as suggested by SmallLint - Refactorings (eg. moved unneeded features to special package) - Many fixes and corrections - Installer has been divided into subpackages to ease installation and upgrade - Refactorings and Code critics (by Lukas Renggli) - Cleaner menus - Feature to recompile the selected item - A category environment, single class and protocol browsers - Optimize code - Code cleanup - Bug fixed - Added case insensitive refactorings - Improved usability so that names of lint rules can also be read on small screens - Spell-checking code: http://www.lukas-renggli.ch/blog/spell-checker - New rule to detect inconsistent method classifications - Each lint rule is defined in its own class now (instead of one rule per method) - Old lint rules removed Contained packages: ------------------------ This image contains the following packages (some packages are only in the squeak-web image): Aida version 5.6 Algernon version 1.2 AST version 164 AutomaticMethodCategorizer version 0.25 AutomaticMethodCategorizerOB version 0.2 DynamicBindings version 2.7 eCompletion version 0.102 eCompletion-Traits version 0.1 eCompletionOmniBrowser version 0.5 Installer version 4.3 Installer-Core version 4.3.313 Installer-Formats version 4.3.3 Installer-Scripts version 4.3.8 KomHttpServer version 7.0.30 KomServices version 1.12 Magritte-Model version 1.1.331 Magritte-Seaside version 1.1.283 Magritte-Tests version 1.1.148 OB-Enhancements version 0.311 OmniBrowser version 0.442 OmniBrowser-Algernon version 0.5 OmniBrowser-Full version 0.27 OmniBrowser-Morphic version 0.84 OmniBrowser-Refactory version 130 OmniBrowser-Regex version 0.15 OmniBrowser-Standard version 0.400 Pier version current Pier-Blog version 1.1.103 Pier-Documents version 1.1.7 Pier-EditorEnh version 1.1.17 Pier-Model version 1.1.263 Pier-Seaside version 1.1.331 Pier-Security version 1.1.119 Pier-Tests version 1.1.116 Polymorph EventEnhancements version 1.1 Polymorph Geometry version 1.1 Polymorph TaskbarIcons version 1.0 Polymorph ToolBuilder version 1.3 Polymorph Tools Diff version 1.3 Polymorph Widgets version 1.4 Refactoring Core version 40 Refactoring Spelling version 4 RoelTyper version 0.60 RSRSS2 version 2.8.3.11 Scriptaculous version 2.8.3.242 ScriptManager version 0.6 Seaside version 2.8.3.572 Seaside-Adapters-Core version pmm.2.mcz Seaside-Adapters-Swazoo version 9 Seaside-Squeak-Adapters version pmm.3.mcz SeasideAdaptersCompatibility version pmm.1.mcz Shout version 3.15-tween.72 ShoutWorkspace version 1-tween.4 SmaCC runtime version 13 Sport version 2.31 Squeak dev packages version 0.28 Squeak web packages version 0.2 SUnit-improved version 4.0.118 SUnitGUI-improved version 4.0.50 Swazoo version 2.1 Universes version 52 Universes OmniBrowser version 0.38 VBRegex version 1.9 YAXO version 14 -- Damien Cassou http://damiencassou.seasidehosting.st

March 10, 2009

Re: [Pharo-project] Fwd: [SoC] Wanted: Google Summer of Code 2009 Mentors and Projects

by Alexandre Bergel

Thanks Alexandre On 10 Mar 2009, at 12:21, Mariano Martinez Peck wrote: > pass: viewpoints > > On Tue, Mar 10, 2009 at 5:26 AM, Alexandre Bergel > <alexandre(a)bergel.eu> wrote: > I would like to propose something regarding binary packages. What is > the password of the swiki? > > Alexandre > > > On 9 Mar 2009, at 20:44, StÃ©phane Ducasse wrote: > > >> > >>> From: "Aik-Siong Koh" <askoh(a)askoh.com> > >>> Date: March 9, 2009 5:00:35 AM CEST > >>> To: soc(a)lists.squeakfoundation.org > >>> Subject: [SoC] Wanted: Google Summer of Code 2009 Mentors and > >>> Projects > >>> Reply-To: askoh(a)askoh.com, Squeak Summer of Code mailing list <soc(a)lists.squeakfoundation.org > >>>> > >>> > >>> It is time for us to apply for Google Summer of Code 2009 (Mar > >>> 9-13th). In > >>> order to be successful we need to show that we have lots of > mentors > >>> and > >>> projects. Please visit > >>> http://wiki.squeak.org/squeak/6118 > >>> and put your name as mentor and post your projects. Also join the > >>> SoC > >>> mailing list. GSOC has been very good to the Squeak community in > >>> the past > >>> two years. > >>> > >>> Thanks, > >>> Aik-Siong Koh > >>> GSOC 2009 admin > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 10, 2009

Re: [Pharo-project] Fwd: [SoC] Wanted: Google Summer of Code 2009 Mentors and Projects

by Mariano Martinez Peck

pass: viewpoints On Tue, Mar 10, 2009 at 5:26 AM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > I would like to propose something regarding binary packages. What is > the password of the swiki? > > Alexandre > > > On 9 Mar 2009, at 20:44, StÃ©phane Ducasse wrote: > > >> > >>> From: "Aik-Siong Koh" <askoh(a)askoh.com> > >>> Date: March 9, 2009 5:00:35 AM CEST > >>> To: soc(a)lists.squeakfoundation.org > >>> Subject: [SoC] Wanted: Google Summer of Code 2009 Mentors and > >>> Projects > >>> Reply-To: askoh(a)askoh.com, Squeak Summer of Code mailing list < > soc(a)lists.squeakfoundation.org > >>>> > >>> > >>> It is time for us to apply for Google Summer of Code 2009 (Mar > >>> 9-13th). In > >>> order to be successful we need to show that we have lots of mentors > >>> and > >>> projects. Please visit > >>> http://wiki.squeak.org/squeak/6118 > >>> and put your name as mentor and post your projects. Also join the > >>> SoC > >>> mailing list. GSOC has been very good to the Squeak community in > >>> the past > >>> two years. > >>> > >>> Thanks, > >>> Aik-Siong Koh > >>> GSOC 2009 admin > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 10, 2009

Re: [Pharo-project] Blocked while merging

by StÃ©phane Ducasse

Hi all did you see this mail because I'm really blocked and cannot merge anymore in pharo. Stef On Mar 9, 2009, at 1:56 PM, StÃ©phane Ducasse wrote: > Hi all > > I wanted to merge and I tried with the new Diff tools and I got a > selector DNU, > so I switched back to the old merge tool but I got the following bugs > > - click on an item > bring the menu revertSelection -> DNU > diff -> DNU > install crahsed. > > Does anybody get the same, I'm using pharo 10248 > > Stef > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 10, 2009

Re: [Pharo-project] loading ClosureBootstrap-08-11-14 in Pharo.

by StÃ©phane Ducasse

ok how can we coordinate to give a try and make it working? I'm away until wednesday evening. Stef On Mar 9, 2009, at 10:08 PM, Adrian Lienhard wrote: > > On Mar 9, 2009, at 21:48 , StÃ©phane Ducasse wrote: > >> >> On Mar 9, 2009, at 9:45 PM, Lukas Renggli wrote: >> >>>> The only problem I see is that at some point you need to save, >>>> close >>> and reopen the image. I guess this is necessary so that the VM >>> forgets >>> all the old contexts still lingering around. >> >> ok this means that we should create a new image and we cannot really >> use the update >> stream to upgrade existing image. > > I think it should be doable with the update stream, no? I would try to > add the install.st at the beginning of the update and then load the > most recent versions of the packages using ScriptLoader as usual > (ignoring any existing changes). > > One also needs to carefully check that the changes do not revert any > fixes/modifications we did in Pharo. > > Adrian > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 10, 2009

Re: [Pharo-project] loading ClosureBootstrap-08-11-14 in Pharo.

by StÃ©phane Ducasse

did you try to check the conflicts for each cs that the install loads? It does not load if I remember correctly but just check for conflict. Stef On Mar 10, 2009, at 8:45 AM, Lukas Renggli wrote: >> One also needs to carefully check that the changes do not revert any >> fixes/modifications we did in Pharo. > > I guess they do revert changes, because it affects so much code across > the whole system. > > The ByteArray #[] tests amazingly still pass ;-) > > This is also the reason why I am pushing the closure implementation. > As Pharo improves it becomes more and more difficult (if not > impossible) to load such low-level changes into the image. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 10, 2009

Re: [Pharo-project] loading ClosureBootstrap-08-11-14 in Pharo.

by StÃ©phane Ducasse

Yes this was the idea Stef On Mar 9, 2009, at 10:08 PM, Adrian Lienhard wrote: > > On Mar 9, 2009, at 21:48 , StÃ©phane Ducasse wrote: > >> >> On Mar 9, 2009, at 9:45 PM, Lukas Renggli wrote: >> >>>> The only problem I see is that at some point you need to save, >>>> close >>> and reopen the image. I guess this is necessary so that the VM >>> forgets >>> all the old contexts still lingering around. >> >> ok this means that we should create a new image and we cannot really >> use the update >> stream to upgrade existing image. > > I think it should be doable with the update stream, no? I would try to > add the install.st at the beginning of the update and then load the > most recent versions of the packages using ScriptLoader as usual > (ignoring any existing changes). > > One also needs to carefully check that the changes do not revert any > fixes/modifications we did in Pharo. > > Adrian > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 10, 2009

Re: [Pharo-project] loading ClosureBootstrap-08-11-14 in Pharo.

by Lukas Renggli

> One also needs to carefully check that the changes do not revert any > fixes/modifications we did in Pharo. I guess they do revert changes, because it affects so much code across the whole system. The ByteArray #[] tests amazingly still pass ;-) This is also the reason why I am pushing the closure implementation. As Pharo improves it becomes more and more difficult (if not impossible) to load such low-level changes into the image. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 10, 2009