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

Re: [Pharo-project] Preparing the sprint

by Lukas Renggli

I made the page editable by public. No need to login, just click on edit at the top right of the page. Lukas 2009/10/12 Oscar Nierstrasz <oscar(a)iam.unibe.ch>: > > I made a wiki page: > > http://scg.unibe.ch/wiki/events/PharoSprintLille09 > > It would be nice if people who are planning to attend have write > access to the wiki. Please ask me or Lukas Renggli if you need to be > added as a wiki user. > > - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 12, 2009

Re: [Pharo-project] Preparing the sprint

by StÃ©phane Ducasse

On Oct 12, 2009, at 10:53 AM, Adrian Lienhard wrote: > This is a good list. I would like to add: > > - evaluate Metacello as a package management system for Pharo (Dale > announced Metacello beta on the Seaside-dev mailing list yesterday) > - simple testserver (load updates from stream, run test, report > results by mail) > - remove Accuny from image and use NiceFonts in Pharo-core > - review closure fixes and make all tests green (I'm working on this) Excellent! I added the list to http://code.google.com/p/pharo/wiki/PharoSprint

Oct. 12, 2009

Re: [Pharo-project] Preparing the sprint

by StÃ©phane Ducasse

Ok I would prefer if we use the pharo wiki there is a page for the sprint at: http://code.google.com/p/pharo/wiki/PharoSprints stef On Oct 12, 2009, at 1:38 PM, Oscar Nierstrasz wrote: > > I made a wiki page: > > http://scg.unibe.ch/wiki/events/PharoSprintLille09 > > It would be nice if people who are planning to attend have write > access to the wiki. Please ask me or Lukas Renggli if you need to be > added as a wiki user. > > - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 12, 2009

Re: [Pharo-project] PackageOrganizer vs Package class side

by StÃ©phane Ducasse

After browsing more code I think that having a PackageOrganiser would support better the migration of existing code. Stef On Oct 11, 2009, at 11:23 PM, Schwab,Wilhelm K wrote: > Stef, > > I'm not sure I'm following what you mean by a single class. I would > probably go for a singleton manager and a package class with > instances for each package. > > Loosely related , it would be _really_ nice to be able to assign > multiple categories to methods. > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo- > project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse > Sent: Sunday, October 11, 2009 2:36 PM > To: Pharo Development > Subject: [Pharo-project] PackageOrganizer vs Package class side > > Hi all > > I coded a bit with david today on the package support and I would > like to know what you think about having Package class side methods > for register, named: ...... vs having and explicit separate class. > > I'm tend towards having one single class. > > Right now in Pharo packageInfo and PackageOrganizer responsibility > are not that clear. > > Stef > > _______________________________________________ > 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

Oct. 12, 2009

Re: [Pharo-project] Preparing the sprint

by Oscar Nierstrasz

I made a wiki page: http://scg.unibe.ch/wiki/events/PharoSprintLille09 It would be nice if people who are planning to attend have write access to the wiki. Please ask me or Lukas Renggli if you need to be added as a wiki user. - on

Oct. 12, 2009

Re: [Pharo-project] Preparing the sprint

by Alain Plantec

Adrian Lienhard a Ã©crit : > This is a good list. I would like to add: > > - evaluate Metacello as a package management system for Pharo (Dale > announced Metacello beta on the Seaside-dev mailing list yesterday) > - simple testserver (load updates from stream, run test, report > results by mail) > - remove Accuny from image and use NiceFonts in Pharo-core > - review closure fixes and make all tests green (I'm working on this) > > Sprint participants, please extend the list! > Hi all, I will work on the new setting framework integration (replacement of old global preferences by local variables + setting declaration). Cheers Alain > Cheers, > Adrian > > On Oct 10, 2009, at 10:01 , StÃ©phane Ducasse wrote: > > >> Hi guys >> >> I would like to have several kinds of tasks so that people can pick up >> Now let me know if you have other points >> >> - fixing stuff for 1.0 >> - integrating pending for 1.1 >> - OB related UI >> - fixing more elaborated points for 1.1 >> - package structure >> - improving the system (smalllint?) >> - Popup discard >> - TextEditor from Squeak/CUIS >> - ToolBuilder changes >> - checking squeak fixes >> - Preparing release candidate >> - fixing _ >> - free fonts >> - Dreaming about the future >> - filesystem? Rio/ >> - newcompiler >> - true package >> - management of noncore packages >> - browsers >> - release/integration process >> >> BTW what is costing me most of my time is cleaning the inbox. >> Can we script that because moving these files is a pain. >> >> Syeg >> >> _______________________________________________ >> 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 > > >

Oct. 12, 2009

Re: [Pharo-project] Debugger (Array does not understand: #empty)

by Ramiro Diaz Trepat

Thanks Johan, I knew about the analogousCodeTo: issue, but I thought it was already fixed in the latest versions of Pharo. Cheers r On Mon, Oct 12, 2009 at 10:43 AM, Johan Brichau <johan.brichau(a)uclouvain.be>wrote: > I'm getting it too > > hotfix so you can continue to work: change the send of #empty to > #isEmpty in MethodProperties>>analogousCodeTo: > > > On 12 Oct 2009, at 01:01, Ramiro Diaz Trepat wrote: > > > Using the latests Pharo image, I get the exception on the subject > > when clicking on any part of the stack. > > Is this a known issue? > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > ---------------------------- > Johan Brichau > johan.brichau(a)uclouvain.be > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 12, 2009

Re: [Pharo-project] Debugger (Array does not understand: #empty)

by Johan Brichau

I'm getting it too hotfix so you can continue to work: change the send of #empty to #isEmpty in MethodProperties>>analogousCodeTo: On 12 Oct 2009, at 01:01, Ramiro Diaz Trepat wrote: > Using the latests Pharo image, I get the exception on the subject > when clicking on any part of the stack. > Is this a known issue? > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ---------------------------- Johan Brichau johan.brichau(a)uclouvain.be

Oct. 12, 2009

Re: [Pharo-project] [Seaside] Komanche ?

by Adrian Lienhard

Hi Ramiro, Yes, this is an issue of the Mac VM only. It was reported in the sense that I sent a mail with instructions to reproduce the problem to the Squeak-vm mailing list and John acknowledged the problem. I don't know whether John intends to fix this, though. Adrian On Oct 11, 2009, at 22:06 , Ramiro Diaz Trepat wrote: > Hi Adrian, > I did open both images with the same VM. I am sure this must be the > problem then. As I said in one of the mails, the problem in my case > went > away when I bounced all the images. > It only happens in the Mac VM then? > Do we need to report this bug somewhere or is it already reported? > Cheers > > r > > > On Sun, Oct 11, 2009 at 8:56 PM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: > >> Did you open another image with the same VM? There is a wired >> behavior of >> the Mac VM that makes the second image listen on the same ports as >> the >> already running image. This may (or may not) be related. >> >> See >> http://lists.squeakfoundation.org/pipermail/vm-dev/2009-June/002726.html >> >> Adrian >> >> >> On Oct 11, 2009, at 17:18 , Ramiro Diaz Trepat wrote: >> >> Robert, can you see your port still listening with this command ? >>> >>> sudo lsof -i -P | grep -i listen >>> >>> >>> >>> >>> On Sun, Oct 11, 2009 at 3:53 PM, Ramiro Diaz Trepat >>> <ramiro(a)diaztrepat.name>wrote: >>> >>> Ah, if Robert still has an image with the issue and if he does not >>> mind >>>> giving it away for autopsy, maybe someone could look at it :)May >>>> be John >>>> Macintosh can help us. >>>> >>>> >>>> >>>> On Sun, Oct 11, 2009 at 3:49 PM, Robert Sirois <watchlala(a)hotmail.com >>>>> wrote: >>>> >>>> I'm running the latest mac vm as well. I believe I attempted the >>>> same >>>>> things to no avail. >>>>> >>>>> RS >>>>> >>>>> Date: Sun, 11 Oct 2009 16:39:37 +0200 >>>>>> >>>>> >>>>> Subject: Re: [Seaside] Komanche ? >>>>>> From: renggli(a)gmail.com >>>>>> To: seaside(a)lists.squeakfoundation.org >>>>>> >>>>>> I use the same configuration with the 4.1.1beta2U VM. >>>>>> >>>>>> Lukas >>>>>> >>>>>> 2009/10/11 Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>: >>>>>> >>>>>>> Correlation does not mean causality, I know. But in my case >>>>>>> this >>>>>>> >>>>>> happened >>>>> >>>>>> right after saving my image, although I had saved it many times >>>>>> before >>>>>>> without issues. >>>>>>> Cheers >>>>>>> >>>>>>> >>>>>>> On Sun, Oct 11, 2009 at 3:01 PM, Ramiro Diaz Trepat < >>>>>>> >>>>>> ramiro(a)diaztrepat.name> >>>>> >>>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> Hi Lukas, >>>>>>>> I am using the latest Pharo, and I have loaded Seaside with >>>>>>>> >>>>>>> ScriptLoader >>>>> >>>>>> loadSeaside30. I am using it on a Mac with Leopard. >>>>>>>> I have managed to reuse that port, with random tests and I do >>>>>>>> not >>>>>>>> >>>>>>> believe >>>>> >>>>>> there may be causality here, but I will tell you anyway what I >>>>>> did. >>>>>>>> When this happens, I removed the problematic adaptor from the >>>>>>>> Seaside >>>>>>>> Control Panel and created a new one (on the same port), then >>>>>>>> I tried >>>>>>>> >>>>>>> closing >>>>> >>>>>> the image and restarting and it did not fix the problem. >>>>>> Although >>>>>>>> >>>>>>> when I >>>>> >>>>>> closed another non Seaside image I was running and then >>>>>> restarted the >>>>>>>> problematic image it worked. >>>>>>>> I wonder now if it is not a mac vm issue or socket issue. >>>>>>>> Robert, >>>>>>>> >>>>>>> are you >>>>> >>>>>> also running on a mac? >>>>>>>> In spite I got the image working again, it is quite worring >>>>>>>> because >>>>>>>> >>>>>>> we >>>>> >>>>>> don't know the cause when an image stops answering requests >>>>>> (although >>>>>>>> >>>>>>> the >>>>> >>>>>> image itself was not hanged at all and kept working fine), and, >>>>>> most >>>>>>>> >>>>>>> weird >>>>> >>>>>> of all, there is no exception or trace of a fault happening. >>>>>> This is >>>>>>>> >>>>>>> really >>>>> >>>>>> what is making me wonder if it is not a low level socket issue >>>>>> that >>>>>>>> >>>>>>> never >>>>> >>>>>> gets to the image for it to throw an exception or anything at >>>>>> all. >>>>>>>> Cheers >>>>>>>> >>>>>>>> r >>>>>>>> >>>>>>>> ps: I'm cross posting to Pharo because I believe this is not a >>>>>>>> >>>>>>> Seaside >>>>> >>>>>> issue. >>>>>>>> >>>>>>>> On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois < >>>>>>>> >>>>>>> watchlala(a)hotmail.com> >>>>> >>>>>> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> I'm using Pharo 1.0.10419, but I'm not sure how to check the >>>>>>>>> other >>>>>>>>> >>>>>>>> two. I >>>>> >>>>>> think I'm still running 2.9 in the image I checked. >>>>>>>>> >>>>>>>>> RS >>>>>>>>> >>>>>>>>> Date: Sun, 11 Oct 2009 12:30:37 +0200 >>>>>>>>>> Subject: Re: [Seaside] Komanche ? >>>>>>>>>> From: renggli(a)gmail.com >>>>>>>>>> To: seaside(a)lists.squeakfoundation.org >>>>>>>>>> >>>>>>>>>> I've never seen this problem before. >>>>>>>>>> >>>>>>>>>> What version of Pharo? Kom? Seaside? >>>>>>>>>> >>>>>>>>>> Lukas >>>>>>>>>> >>>>>>>>>> 2009/10/11 Robert Sirois <watchlala(a)hotmail.com>: >>>>>>>>>> >>>>>>>>>>> I've also had this problem for quite a while now and have >>>>>>>>>>> not >>>>>>>>>>> >>>>>>>>>> found >>>>> >>>>>> any way to fix the problem either. >>>>>>>>>>> >>>>>>>>>>> RS >>>>>>>>>>> >>>>>>>>>>> Ramiro Diaz Trepat <ramiro(a)diaztrepat.name> wrote: >>>>>>>>>>> >>>>>>>>>>> Something really strange happened to me more than once >>>>>>>>>>> now.In a >>>>>>>>>>>> simple dev >>>>>>>>>>>> image (Pharo + Seaside3 + Kom on a Mac) after saving the >>>>>>>>>>>> image >>>>>>>>>>>> >>>>>>>>>>> at >>>>> >>>>>> some >>>>>>>>>>>> point, Komanche stops answering anything at all, >>>>>>>>>>>> althought the >>>>>>>>>>>> >>>>>>>>>>> port >>>>> >>>>>> keeps >>>>>>>>>>>> listening (as listed on a terminal). >>>>>>>>>>>> No errors are displayed anywere but the port becomes >>>>>>>>>>>> unusable >>>>>>>>>>>> >>>>>>>>>>> from >>>>> >>>>>> that >>>>>>>>>>>> point on. >>>>>>>>>>>> If I wish to continue using the same image I have to add >>>>>>>>>>>> another >>>>>>>>>>>> adaptor in >>>>>>>>>>>> the Seaside Control Panel and start again. >>>>>>>>>>>> The "dead" ports never become usable again, not even >>>>>>>>>>>> stopping >>>>>>>>>>>> >>>>>>>>>>> and >>>>> >>>>>> removing >>>>>>>>>>>> the adaptor and adding a new one. >>>>>>>>>>>> I am not even sure that this is a Komanche issue, as I >>>>>>>>>>>> said no >>>>>>>>>>>> >>>>>>>>>>> error >>>>> >>>>>> of >>>>>>>>>>>> anykind is visible. >>>>>>>>>>>> Has anyone come across this before? >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> seaside mailing list >>>>>>>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>>>>>>> >>>>>>>>>>>> >>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>> >>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> seaside mailing list >>>>>>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>>>>>> >>>>>>>>>>> >>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>> >>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Lukas Renggli >>>>>>>>>> http://www.lukas-renggli.ch >>>>>>>>>> _______________________________________________ >>>>>>>>>> seaside mailing list >>>>>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>>>>> >>>>>>>>>> >>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>> >>>>>> >>>>>>>>> ________________________________ >>>>>>>>> Your E-mail and More On-the-Go. Get Windows Live Hotmail >>>>>>>>> Free. Sign >>>>>>>>> >>>>>>>> up >>>>> >>>>>> now. >>>>>>>>> _______________________________________________ >>>>>>>>> seaside mailing list >>>>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> seaside mailing list >>>>>>> seaside(a)lists.squeakfoundation.org >>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Lukas Renggli >>>>>> http://www.lukas-renggli.ch >>>>>> _______________________________________________ >>>>>> seaside mailing list >>>>>> seaside(a)lists.squeakfoundation.org >>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/ >>>>>> seaside >>>>>> >>>>> >>>>> ------------------------------ >>>>> Hotmail: Trusted email with Microsoftâs powerful SPAM >>>>> protection. Sign >>>>> up >>>>> now. <http://clk.atdmt.com/GBL/go/177141664/direct/01/> >>>>> >>>>> _______________________________________________ >>>>> seaside mailing list >>>>> seaside(a)lists.squeakfoundation.org >>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>> >>>>> >>>>> >>>> _______________________________________________ >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Oct. 12, 2009

Re: [Pharo-project] Preparing the sprint

by Adrian Lienhard

This is a good list. I would like to add: - evaluate Metacello as a package management system for Pharo (Dale announced Metacello beta on the Seaside-dev mailing list yesterday) - simple testserver (load updates from stream, run test, report results by mail) - remove Accuny from image and use NiceFonts in Pharo-core - review closure fixes and make all tests green (I'm working on this) Sprint participants, please extend the list! Cheers, Adrian On Oct 10, 2009, at 10:01 , StÃ©phane Ducasse wrote: > Hi guys > > I would like to have several kinds of tasks so that people can pick up > Now let me know if you have other points > > - fixing stuff for 1.0 > - integrating pending for 1.1 > - OB related UI > - fixing more elaborated points for 1.1 > - package structure > - improving the system (smalllint?) > - Popup discard > - TextEditor from Squeak/CUIS > - ToolBuilder changes > - checking squeak fixes > - Preparing release candidate > - fixing _ > - free fonts > - Dreaming about the future > - filesystem? Rio/ > - newcompiler > - true package > - management of noncore packages > - browsers > - release/integration process > > BTW what is costing me most of my time is cleaning the inbox. > Can we script that because moving these files is a pain. > > Syeg > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 12, 2009