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

Re: [Pharo-project] Three current versions: 1.0, 1.1, 1.2

by StÃ©phane Ducasse

adrian there are some fixed simple UTF and other pending fixes that we could integrate (was planning for after lunch) Stef >> Also, people who know there is something that really needs to be fixed for a 1.1 release should speak up now. >> >> Cheers, >> Adrian >> > > - ConnectionQueue. (2476) > - WeakKeyDictionaries. > Easiest would probably be to port the one in Squeak now (with related finalization classes), as Levente did some work on that compared to what was in Squeak 4.0 / Pharo 1.0 which made it faster without breaking it when not registered for finalization. > Alternatively wait for VM's to be built with Igor's finalization enhancements, require those for 1.1 WeakRegistries, and rewrite WeakKeyDictionaries to no longer assume they may be used/are always registered for finalization. (1628, 2309) > - Encoding for code importing/exporting (setConverterForCode methods 1608 , 1872) > are some fixed? Stef > Cheers, > Henry > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 9, 2010

Re: [Pharo-project] Three current versions: 1.0, 1.1, 1.2

by StÃ©phane Ducasse

On Jun 9, 2010, at 9:29 AM, Adrian Lienhard wrote: > Stef, I think you misunderstood me. I didn't imply that we need to fix the 179 issues for 1.1. But what we should really do is to identify whether there is any show stopper. sure :) > I started going through the 1.1-tagged issues yesterday and I have moved stuff that is not critical to 1.2 (or close what doesn't need any further action). Yes I saw and I started to do that a while ago too. > Maybe it would be better not to tag issues with 1.2 unless we know that we want to take them into account for 1.2. Else we end up being in the same situation as now. may be :) > > Also, people who know there is something that really needs to be fixed for a 1.1 release should speak up now. > > Cheers, > Adrian > > > On Jun 9, 2010, at 08:03 , StÃ©phane Ducasse wrote: > >> >> On Jun 8, 2010, at 8:53 PM, Adrian Lienhard wrote: >> >>> I think it's a bad idea to just switch the downloads from 1.0 to 1.1 now. We don't even have a release candidate yet, hence 1.1 hasn't seen much testing. 1.1 may be ok for personal use but is it also safe to be deployed on a mission critical system? I'm all for short release cycles, but please don't take such shortcuts. A high quality is really important if we want to support the companies using Pharo and attract new ones. >> >> We can keep 1.0 download but we will issue 1.1 rc now. >> >>> So the next steps should be: identifying the critical issues (currently there are 179 open issues tagged 1.1!), then fixing them, then we do a first RC. >> We will not fix all these issues but moved them to 1.2. >> Since most of them exit in 1.0 and you can work with them I do not see why suddenly we should fix them in 1.1 especially >> just before the release. So stability also means that you should not change the system at wrong moment. >> And now this is not the moment to change it. >> >> Stef >> >> >>> Cheers, >>> Adrian >>> >>> On Jun 8, 2010, at 15:45 , Mariano Martinez Peck wrote: >>> >>>> On Tue, Jun 8, 2010 at 9:46 AM, Niko Schwarz <niko.schwarz(a)googlemail.com>wrote: >>>> >>>>> Of course not. Just switch the default download (the big one, all over >>>>> the site) site to 1.1. >>>>> >>>>> I just suggest to switch from 1.0 to 1.1 as stable at the same time >>>>> that we switch from 1.1 to 1.2 for development. >>>> >>>> >>>> I think this is a good idea. >>>> >>>> >>>>> Then we never have 3 >>>>> "current" versions at once. >>>>> >>>>> Cheers, >>>>> >>>>> Niko >>>>> >>>>> -- >>>>> http://scg.unibe.ch/staff/Schwarz >>>>> twitter.com/nes1983 >>>>> Tel: +41 076 235 8683 >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 9, 2010

Re: [Pharo-project] Three current versions: 1.0, 1.1, 1.2

by Henrik Johansen

On Jun 9, 2010, at 9:29 16AM, Adrian Lienhard wrote: > > Also, people who know there is something that really needs to be fixed for a 1.1 release should speak up now. > > Cheers, > Adrian > - ConnectionQueue. (2476) - WeakKeyDictionaries. Easiest would probably be to port the one in Squeak now (with related finalization classes), as Levente did some work on that compared to what was in Squeak 4.0 / Pharo 1.0 which made it faster without breaking it when not registered for finalization. Alternatively wait for VM's to be built with Igor's finalization enhancements, require those for 1.1 WeakRegistries, and rewrite WeakKeyDictionaries to no longer assume they may be used/are always registered for finalization. (1628, 2309) - Encoding for code importing/exporting (setConverterForCode methods 1608 , 1872) Cheers, Henry

June 9, 2010

[Pharo-project] Fwd: Smalltalk opportunity

by Marcus Denker

Hi, Not Pharo or Squeak, but nevertheless always nice to see smalltalk jobs posted: Begin forwarded message: > To: <pharo-project-owner(a)lists.gforge.inria.fr> > Subject: FW: Smalltalk opportunity > > A request > > From: Ahmed Baig > Sent: 03 June 2010 15:08 > To: pharo-project(a)lists.gforge.inria.fr > Subject: Smalltalk opportunity > > Hi, > > Stumbled on your website â looks interesting â wonder if you can help me â i am recruiting for a â3rd Line Application Support professional with experience of Smalltalkâ for a global Investment Bank based in Zurich Switzerland. > > Can you post this somewhere â no job description just the above. My contact details are ahmed.baig(a)hatstand-ltd.com OR +44 (0)7944 354 070 > > Many thanks in advance for your assistance, > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 9, 2010

[Pharo-project] Metacello and file repositories

by Torsten Bergmann

Monticello allows you to use local directories as alternatives to web based squeaksource repositories. When I select one in the Monticello browser it displays "c:\pharo\myapp\repo\" (maybe "file://c:\pharo\myapp\repo\" would have been better - but thats a Monticello issue. Question: Is it possible to use Metacello configurations with directory repositories too? Currently this fails for me since Metacello always tries to use a HTTP repo while loading: --------------------------------------------------------------------- baseline10: spec "The first baseline for the MyApp project" <version: '1.0-baseline'> spec for: #pharo do: [ spec blessing: #baseline. spec description: '1.0 baseline for MyApp'. spec repository: 'c:\pharo\myapp\repo\'. "Packages" spec package: 'MyApp-Core-Model'; ... --------------------------------------------------------------------- Any comments? Thanks T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

June 9, 2010

Re: [Pharo-project] Three current versions: 1.0, 1.1, 1.2

by Adrian Lienhard

Stef, I think you misunderstood me. I didn't imply that we need to fix the 179 issues for 1.1. But what we should really do is to identify whether there is any show stopper. I started going through the 1.1-tagged issues yesterday and I have moved stuff that is not critical to 1.2 (or close what doesn't need any further action). Maybe it would be better not to tag issues with 1.2 unless we know that we want to take them into account for 1.2. Else we end up being in the same situation as now. Also, people who know there is something that really needs to be fixed for a 1.1 release should speak up now. Cheers, Adrian On Jun 9, 2010, at 08:03 , StÃ©phane Ducasse wrote: > > On Jun 8, 2010, at 8:53 PM, Adrian Lienhard wrote: > >> I think it's a bad idea to just switch the downloads from 1.0 to 1.1 now. We don't even have a release candidate yet, hence 1.1 hasn't seen much testing. 1.1 may be ok for personal use but is it also safe to be deployed on a mission critical system? I'm all for short release cycles, but please don't take such shortcuts. A high quality is really important if we want to support the companies using Pharo and attract new ones. > > We can keep 1.0 download but we will issue 1.1 rc now. > >> So the next steps should be: identifying the critical issues (currently there are 179 open issues tagged 1.1!), then fixing them, then we do a first RC. > We will not fix all these issues but moved them to 1.2. > Since most of them exit in 1.0 and you can work with them I do not see why suddenly we should fix them in 1.1 especially > just before the release. So stability also means that you should not change the system at wrong moment. > And now this is not the moment to change it. > > Stef > > >> Cheers, >> Adrian >> >> On Jun 8, 2010, at 15:45 , Mariano Martinez Peck wrote: >> >>> On Tue, Jun 8, 2010 at 9:46 AM, Niko Schwarz <niko.schwarz(a)googlemail.com>wrote: >>> >>>> Of course not. Just switch the default download (the big one, all over >>>> the site) site to 1.1. >>>> >>>> I just suggest to switch from 1.0 to 1.1 as stable at the same time >>>> that we switch from 1.1 to 1.2 for development. >>> >>> >>> I think this is a good idea. >>> >>> >>>> Then we never have 3 >>>> "current" versions at once. >>>> >>>> Cheers, >>>> >>>> Niko >>>> >>>> -- >>>> http://scg.unibe.ch/staff/Schwarz >>>> twitter.com/nes1983 >>>> Tel: +41 076 235 8683 >>>> >>>> _______________________________________________ >>>> 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 >> >> >> _______________________________________________ >> 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

June 9, 2010

Re: [Pharo-project] little fix for Slice

by laurent laffont

On Wed, Jun 9, 2010 at 8:52 AM, Patrick Barroca <patrick.barroca(a)gmail.com>wrote: > An update of the screencast would be great. > > I also have started the Â«How to contributeÂ» section of the > collaboractive book where I plan to aggregate content of > http://pharo-project.org/community/issue-tracking and > http://code.google.com/p/pharo/wiki/HowToContribute. > and http://code.google.com/p/pharo/wiki/IntegrationProcessDescription :) Laurent > > > 2010/6/9 laurent laffont <laurent.laffont(a)gmail.com>: > > Cool. It seems I need to update the 'How to contribute' screencast :) > > Laurent Laffont > > > > http://pharocasts.blogspot.com/ > > http://magaloma.blogspot.com/ > > > > > > On Tue, Jun 8, 2010 at 11:57 PM, Patrick Barroca < > patrick.barroca(a)gmail.com> > > wrote: > >> > >> Hi, > >> > >> After the first fix published during last sprint I just posted to > >> PharoInbox another slice with a little bugfix and input validations. > >> > >> Name: SLICE-Issue-2478-NicerSliceCreationContinued-PatrickBarroca.1 > >> Author: PatrickBarroca > >> Time: 8 June 2010, 11:31:49 pm > >> UUID: e7e7182b-1145-584b-ac24-9db73c5ff46c > >> Ancestors: > >> Dependencies: MonticelloGUI-PatrickBarroca.60, > >> Collections-Strings-PatrickBarroca.121 > >> > >> Nicer slice creation with input validations > >> > >> > >> On Wed, May 26, 2010 at 1:57 PM, StÃ©phane Ducasse > >> <stephane.ducasse(a)inria.fr> wrote: > >> > hi all > >> > > >> > Does any of you want to help? with a little exercise? > >> > > >> > It would be nice to help the user to provide coherent slice name > >> > I suggest > >> > > >> > SLICE-number-title > >> > > >> > title with only alphanumberical-characters > >> > any taker? > >> > > >> > because this would be cool to get another step forward > >> > > >> > http://code.google.com/p/pharo/issues/detail?id=2478 > >> > > >> > Stef > >> > > >> > _______________________________________________ > >> > Pharo-project mailing list > >> > Pharo-project(a)lists.gforge.inria.fr > >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > >> > >> > >> > >> -- > >> Patrick Barroca > >> > >> _______________________________________________ > >> 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 > > > > > > -- > Patrick Barroca > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 9, 2010

[Pharo-project] (Almost :) easy way to help pharocasts

by laurent laffont

Hi, Pharo is moving fast and some screencasts become obsolete (deprecated methods, updated packages, ...) or need subtitles. You can: - test that screencasts work in Pharo 1.1 - re-record screencasts with subtitles (check http://pharocasts.blogspot.com/2010/02/how-i-record-screencasts-for-pharoca… and http://www.my-guides.net/en/content/view/105/26/ for subtitles) - provide new screencasts based on Pharo collaboractive book, Pharo by example or Seaside book. - give feedback. - I use Linux, I'm still looking for screencasts on how to build squeakvm on Windows and OSX. Another easy way to help if you don't have time but money :) is to click the donate button as I'm looking at buying a new laptop with bigger screen, so I can provide screencasts with higher resolution. Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

June 9, 2010

Re: [Pharo-project] little fix for Slice

by Patrick Barroca

An update of the screencast would be great. I also have started the Â«How to contributeÂ» section of the collaboractive book where I plan to aggregate content of http://pharo-project.org/community/issue-tracking and http://code.google.com/p/pharo/wiki/HowToContribute. 2010/6/9 laurent laffont <laurent.laffont(a)gmail.com>: > Cool. It seems I need to update the 'How to contribute' screencast :) > Laurent Laffont > > http://pharocasts.blogspot.com/ > http://magaloma.blogspot.com/ > > > On Tue, Jun 8, 2010 at 11:57 PM, Patrick Barroca <patrick.barroca(a)gmail.com> > wrote: >> >> Hi, >> >> After the first fix published during last sprint I just posted to >> PharoInbox another slice with a little bugfix and input validations. >> >> Name: SLICE-Issue-2478-NicerSliceCreationContinued-PatrickBarroca.1 >> Author: PatrickBarroca >> Time: 8 June 2010, 11:31:49 pm >> UUID: e7e7182b-1145-584b-ac24-9db73c5ff46c >> Ancestors: >> Dependencies: MonticelloGUI-PatrickBarroca.60, >> Collections-Strings-PatrickBarroca.121 >> >> Nicer slice creation with input validations >> >> >> On Wed, May 26, 2010 at 1:57 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >> > hi all >> > >> > Does any of you want to help? with a little exercise? >> > >> > It would be nice to help the user to provide coherent slice name >> > I suggest >> > >> > SLICE-number-title >> > >> > title with only alphanumberical-characters >> > any taker? >> > >> > because this would be cool to get another step forward >> > >> > http://code.google.com/p/pharo/issues/detail?id=2478 >> > >> > Stef >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> >> >> >> -- >> Patrick Barroca >> >> _______________________________________________ >> 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 > -- Patrick Barroca

June 9, 2010

Re: [Pharo-project] little fix for Slice

by laurent laffont

Cool. It seems I need to update the 'How to contribute' screencast :) Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ On Tue, Jun 8, 2010 at 11:57 PM, Patrick Barroca <patrick.barroca(a)gmail.com>wrote: > Hi, > > After the first fix published during last sprint I just posted to > PharoInbox another slice with a little bugfix and input validations. > > Name: SLICE-Issue-2478-NicerSliceCreationContinued-PatrickBarroca.1 > Author: PatrickBarroca > Time: 8 June 2010, 11:31:49 pm > UUID: e7e7182b-1145-584b-ac24-9db73c5ff46c > Ancestors: > Dependencies: MonticelloGUI-PatrickBarroca.60, > Collections-Strings-PatrickBarroca.121 > > Nicer slice creation with input validations > > > On Wed, May 26, 2010 at 1:57 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > hi all > > > > Does any of you want to help? with a little exercise? > > > > It would be nice to help the user to provide coherent slice name > > I suggest > > > > SLICE-number-title > > > > title with only alphanumberical-characters > > any taker? > > > > because this would be cool to get another step forward > > > > http://code.google.com/p/pharo/issues/detail?id=2478 > > > > Stef > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Patrick Barroca > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 9, 2010