- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo 1.0 release plan

by Alexandre Bergel

What about having short screencasts that show basic steps such as class and method creation, using the debugger,... I have SnapZPro, I could make up some Cheers, Alexandre On 4 Nov 2008, at 10:38, Adrian Lienhard wrote: > Hi Matthias, > > yes, that would be very useful (I added it to the wiki)! > Can you help with this? > > Cheers, > Adrian > > On Nov 4, 2008, at 12:52 , Matthias Berth wrote: > >> Hi Adrian, >> >> how about some getting started information - inside the image and >> on a >> web page? What would be useful for beginners? >> >> Cheers >> >> Matthias >> >> On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <adi(a)netstyle.ch> >> wrote: >>> Hi everyone, >>> >>> Last week in Bern, Marcus, Stef, and I have been discussing a plan >>> for a >>> first release of Pharo. Overall, the goal is to produce a >>> valuable, stable >>> "product" within reasonable time. Is there anything important we >>> missed? Any >>> suggestions? >>> >>> >>> FUNCTIONAL REQUIREMENTS >>> -------------------------------------------- >>> Integrate Polymorph >>> Integrate TrueType >>> Main EToys removal >>> Refactor Traits API >>> >>> >>> NON-FUNCTIONAL REQUIREMENTS >>> -------------------------------------------- >>> All tests green >>> License clean (check OLPC changes) >>> First consistent version of the website (work in progress) >>> >>> >>> INFRASTRUCTURE >>> -------------------------------------------- >>> Increase efficiency of producing new updates (work in progress) >>> Prepare second update stream to maintain released version >>> >>> >>> TENTATIVE SCHEDULE >>> -------------------------------------------- >>> Going beta in January >>> Release of version 1.0 in February >>> >>> >>> Cheers, >>> Adrian >>> ___________________ >>> http://www.adrian-lienhard.ch/ >>> >>> >>> _______________________________________________ >>> 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 4, 2008

Re: [Pharo-project] Pharo 1.0 release plan

by Adrian Lienhard

Hi Matthias, yes, that would be very useful (I added it to the wiki)! Can you help with this? Cheers, Adrian On Nov 4, 2008, at 12:52 , Matthias Berth wrote: > Hi Adrian, > > how about some getting started information - inside the image and on a > web page? What would be useful for beginners? > > Cheers > > Matthias > > On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: >> Hi everyone, >> >> Last week in Bern, Marcus, Stef, and I have been discussing a plan >> for a >> first release of Pharo. Overall, the goal is to produce a valuable, >> stable >> "product" within reasonable time. Is there anything important we >> missed? Any >> suggestions? >> >> >> FUNCTIONAL REQUIREMENTS >> -------------------------------------------- >> Integrate Polymorph >> Integrate TrueType >> Main EToys removal >> Refactor Traits API >> >> >> NON-FUNCTIONAL REQUIREMENTS >> -------------------------------------------- >> All tests green >> License clean (check OLPC changes) >> First consistent version of the website (work in progress) >> >> >> INFRASTRUCTURE >> -------------------------------------------- >> Increase efficiency of producing new updates (work in progress) >> Prepare second update stream to maintain released version >> >> >> TENTATIVE SCHEDULE >> -------------------------------------------- >> Going beta in January >> Release of version 1.0 in February >> >> >> Cheers, >> Adrian >> ___________________ >> http://www.adrian-lienhard.ch/ >> >> >> _______________________________________________ >> 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

Nov. 4, 2008

[Pharo-project] KI diff package

by Pavel Krivanek

This package http://squeak.cz/public/pub/KernelImage/temp/Remove-pavel_krivanek.1.mcz contains classes and methods that were removed in the KernelImage variant with Morphic but without Etoys. It may be used as referential material during Etoys removing. KI renames most of class initialization methods so they figure here as removed ones. -- Pavel

Nov. 4, 2008

Re: [Pharo-project] RBParser

by Gwenael Casaccio

Hi, In fact I've seen the method patch literal in the parser which transformed the literals as strings so as we've strings in the scanner I've take the decision to remove this method and kept the literals as string. And off course I don't have launch the refactorings tests :s Cheers, Gwenael On 11/1/08 10:21 AM, Lukas Renggli wrote: > On Fri, Oct 31, 2008 at 10:42 AM, Gwenael Casaccio<mrgwen(a)gmail.com> wrote: >> I've commit a new version I've removed all the RB*Token > > I've loaded your changes, but it seems to break the refactoring > browser. All literals (numbers, symbols, true, false, nil, ...) are > printed as strings ('123', '#foo', 'true', 'false', ...). Did I forget > to load something, or is this a bug? > > Cheers, > Lukas > > >> On 10/29/08 6:21 PM, Lukas Renggli wrote: >>>> As I've said to you Marcus, I've worked on the RBParser/RBScanner. I've >>>> fixed these classes and now you can parse the entire image. At this >>>> moment >>>> the refactoring is not yet finished but I've made some good progress. >>> Good news. >>> >>> I was not aware that you were working on RBParser. Stef told me that >>> you also improved the refactorings. I think you should commit and work >>> on the public repository to get more attention. I guess there were >>> many other changes going on in RB codebase in the meantime. >>> >>> Cheers, >>> Lukas >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > >

Nov. 4, 2008

Re: [Pharo-project] Pharo 1.0 release plan

by Matthias Berth

Hi Adrian, how about some getting started information - inside the image and on a web page? What would be useful for beginners? Cheers Matthias On Sun, Nov 2, 2008 at 1:02 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Hi everyone, > > Last week in Bern, Marcus, Stef, and I have been discussing a plan for a > first release of Pharo. Overall, the goal is to produce a valuable, stable > "product" within reasonable time. Is there anything important we missed? Any > suggestions? > > > FUNCTIONAL REQUIREMENTS > -------------------------------------------- > Integrate Polymorph > Integrate TrueType > Main EToys removal > Refactor Traits API > > > NON-FUNCTIONAL REQUIREMENTS > -------------------------------------------- > All tests green > License clean (check OLPC changes) > First consistent version of the website (work in progress) > > > INFRASTRUCTURE > -------------------------------------------- > Increase efficiency of producing new updates (work in progress) > Prepare second update stream to maintain released version > > > TENTATIVE SCHEDULE > -------------------------------------------- > Going beta in January > Release of version 1.0 in February > > > Cheers, > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 4, 2008

Re: [Pharo-project] Pharo 1.0 release plan

by Damien Pollet

On Mon, Nov 3, 2008 at 3:55 PM, Marcus Denker <denker(a)iam.unibe.ch> wrote: > I vote for Pharo-Core and Pharo. +1 also, can we have the bike shed in blue ? -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Nov. 4, 2008

Re: [Pharo-project] Pharo 1.0 release plan

by Dan Corneanu

> ok, then, let's take Pharo-Core and Pharo. +1

Nov. 4, 2008

Re: [Pharo-project] Too much updates without an image

by Marcus Denker

On 04.11.2008, at 10:30, Damien Cassou wrote: > Hi, > > could you please release an image with the latest changes so that I > can base the new pharo-dev on them? > I will make one today > -- > 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) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Nov. 4, 2008

[Pharo-project] Too much updates without an image

by Damien Cassou

Hi, could you please release an image with the latest changes so that I can base the new pharo-dev on them? -- 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)

Nov. 4, 2008

[Pharo-project] Re: OT: how much Smalltalk code is in Linux kernel

by nicolas cellier

Alexandre Bergel <alexandre@...> writes: > > Maybe some comment using "..." are present in the code that is ignored > for some reason from the compiler. > > Cheers, > Alexandre > > On 3 Nov 2008, at 19:16, Michael Roberts wrote: > > > -9 lines? did I read that right? > > > > Mike > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project@... > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > Or it could have been an overflow because of a part of Kernel not written in Smalltalk ;) A short int overflow of course, because no one would write 2^32-1-9 lines of Smalltalk! Hehe, the good question could be how many lines of Smalltalk to write a linux? Ask VPRI Nicolas

Nov. 4, 2008