- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Using pharo in a course?

by Marcus Denker

On 30.01.2009, at 15:32, StÃ©phane Ducasse wrote: > ideally we planed for march now what is left to do: > - trait fixes > - etoy removal > - licensing. > Yes, this is what is left from the list of things for 1.0 (and: use TT fonts by default). I hope to be able to work again on pharo soon (too many papers with deadlines...) Marcus > Stef > > On Jan 30, 2009, at 3:20 PM, michael_atkisson(a)comcast.net wrote: > >> Not to add any pressure or be annoying, but what is the current >> estimate of when 1.0 will >> be released? I am just curious. >> >> -------------- Original message -------------- >> From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >>> Use pharo (better UI). >>> Once we will have pharo 1.0 we will work on pharo by example. >>> Seaside is now developed using pharo. >>> >>> Stef >>> >>> >>> On Jan 29, 2009, at 5:53 PM, Marco D'Ambros wrote: >>> >>>> Hi all! >>>> >>>> I will start teaching a course about software engineering and web >>>> development, and I decided to do it with seaside. >>>> I was wondering whether to use pharo or squeak... which are the >>>> benefits and drawbacks of pharo with respect to squeak, in the >> context >>>> of a bachelor course? >>>> The students know about object oriented programming but don't >> about >>>> smalltalk, so in the first weeks we will teach smalltalk. >>>> >>>> Any suggestions? >>>> >>>> Thanks and cheers >>>> Marco D'Ambros >>>> >>>> _______________________________________________ >>>> 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 -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Jan. 30, 2009

Re: [Pharo-project] Plugin organization

by Lukas Renggli

> so what are the organizations we can use? > Ideally I would like to have the test associated with their packages. > > XXX > XXXTests > > but may be people found a better way That doesn't work, because you end up with overlapping package names. This is how we name packages in Seaside 2.9: http://code.google.com/p/seaside/wiki/PackageNaming Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 30, 2009

Re: [Pharo-project] [ENH] Literal Byte Arrays

by Lukas Renggli

> Statically, the compiler could make the conversion. No? Sure, that would be a possibility, but it is not standard. Almost all modern Smalltalk implementations support the #[ ] syntax. The parsers of the NewCompiler and the RefactoringBrowser already support the syntax for literal byte arrays for decades. Why the resistance? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 30, 2009

Re: [Pharo-project] Plugin organization

by Michael Rueger

StÃ©phane Ducasse wrote: > so what are the organizations we can use? > Ideally I would like to have the test associated with their packages. > > XXX > XXXTests The problem with that naming scheme is that then the tests would always be loaded together with their tests because of the simple string matching Monticello does. Which isn't something you want when doing application/runtime builds. That's why I proposed the Plugin-* and Tests-* naming schemes. Michael

Jan. 30, 2009

Re: [Pharo-project] Using pharo in a course?

by StÃ©phane Ducasse

ideally we planed for march now what is left to do: - trait fixes - etoy removal - licensing. Stef On Jan 30, 2009, at 3:20 PM, michael_atkisson(a)comcast.net wrote: > Not to add any pressure or be annoying, but what is the current > estimate of when 1.0 will > be released? I am just curious. > > -------------- Original message -------------- > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > Use pharo (better UI). > > Once we will have pharo 1.0 we will work on pharo by example. > > Seaside is now developed using pharo. > > > > Stef > > > > > > On Jan 29, 2009, at 5:53 PM, Marco D'Ambros wrote: > > > > > Hi all! > > > > > > I will start teaching a course about software engineering and web > > > development, and I decided to do it with seaside. > > > I was wondering whether to use pharo or squeak... which are the > > > benefits and drawbacks of pharo with respect to squeak, in the > context > > > of a bachelor course? > > > The students know about object oriented programming but don't > about > > > smalltalk, so in the first weeks we will teach smalltalk. > > > > > > Any suggestions? > > > > > > Thanks and cheers > > > Marco D'Ambros > > > > > > _______________________________________________ > > > 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

Jan. 30, 2009

Re: [Pharo-project] Plugin organization

by StÃ©phane Ducasse

On Jan 30, 2009, a > > The same convention could also be applied to test packages btw to > avoid > all this very "creative" naming, patching the "test" somewhere into > the > category name. YES so what are the organizations we can use? Ideally I would like to have the test associated with their packages. XXX XXXTests but may be people found a better way Stef

Jan. 30, 2009

Re: [Pharo-project] Using pharo in a course?

by Alexandre Bergel

Before esug I hope. Alexandre On 30 Jan 2009, at 15:20, michael_atkisson(a)comcast.net wrote: > Not to add any pressure or be annoying, but what is the current > estimate of when 1.0 will > be released? I am just curious. > > -------------- Original message -------------- > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > Use pharo (better UI). > > Once we will have pharo 1.0 we will work on pharo by example. > > Seaside is now developed using pharo. > > > > Stef > > > > > > On Jan 29, 2009, at 5:53 PM, Marco D'Ambros wrote: > > > > > Hi all! > > > > > > I will start teaching a course about software engineering and web > > > development, and I decided to do it with seaside. > > > I was wondering whether to use pharo or squeak... which are the > > > benefits and drawbacks of pharo with respect to squeak, in the > context > > > of a bachelor course? > > > The students know about object oriented programming but don't > about > > > smalltalk, so in the first weeks we will teach smalltalk. > > > > > > Any suggestions? > > > > > > Thanks and cheers > > > Marco D'Ambros > > > > > > _______________________________________________ > > > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 30, 2009

Re: [Pharo-project] [ENH] Literal Byte Arrays

by Alexandre Bergel

Maybe this is something the compiler could do without extending the syntax since, I far as I understood, "#(...) asByteArray" is always equivalent to"#[...]" Statically, the compiler could make the conversion. No? Alexandre On 30 Jan 2009, at 10:55, Lukas Renggli wrote: >> so do I understand correctly that your point is to replace >> asByteArray by #[] > > Yes, instead of writing > > #( 1 2 3 ) asByteArray > > you write > > #[ 1 2 3 ] > > Which is much faster and saves memory, as no conversion and no copying > happens at runtime. All Smalltalk dialects (with the exception of > GemStone) support this syntax. Pharo should have it too. > > 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 30, 2009

Re: [Pharo-project] Using pharo in a course?

by michael_atkisson＠comcast.net

Not to add any pressure or be annoying, but what is the current estimate of when 1.0 will be released? I am just curious. -------------- Original message -------------- From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Use pharo (better UI). > Once we will have pharo 1.0 we will work on pharo by example. > Seaside is now developed using pharo. > > Stef > > > On Jan 29, 2009, at 5:53 PM, Marco D'Ambros wrote: > > > Hi all! > > > > I will start teaching a course about software engineering and web > > development, and I decided to do it with seaside. > > I was wondering whether to use pharo or squeak... which are the > > benefits and drawbacks of pharo with respect to squeak, in the context > > of a bachelor course? > > The students know about object oriented programming but don't about > > smalltalk, so in the first weeks we will teach smalltalk. > > > > Any suggestions? > > > > Thanks and cheers > > Marco D'Ambros > > > > _______________________________________________ > > 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

Jan. 30, 2009

Re: [Pharo-project] Call for UI gripes

by David RÃ¶thlisberger

> OB buttons - David and I will get there eventually! yep. I integrated your patch, but it needs some fine-tuning. There are still places where OB directly sets button colors. This is easy to fix. The bigger problem is that with your patch we get problems in all other systems not using Polymorph. I'm working on a patch to make it work in both environments. David

Jan. 30, 2009