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

Re: [Pharo-project] Object>>at:modify:???

by StÃ©phane Ducasse

Ok we can deprecate it. On Oct 22, 2010, at 11:04 PM, Hernan Wilkinson wrote: > In a 1.1 image I have, the class HttpRequest is using that message... > > On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > I would like to deprecate the following method since nobody use it. > What do you think? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > HernÃ¡n Wilkinson > Agile Software Development, Teaching & Coaching > Mobile: +54 - 911 - 4470 - 7207 > email: hernan.wilkinson(a)10Pines.com > site: http://www.10Pines.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 23, 2010

Re: [Pharo-project] Pharo article in linuxMag fr

by GermÃ¡n Arduino

Hi Noury: Thanks by the offer! I will try to be tunned to the next year event. Cheers. 2010/10/23 Noury Bouraqadi <bouraqadi(a)gmail.com>: > > On 22 oct. 2010, at 16:47, GermÃ¡n Arduino wrote: > >> Yes, very interesting. >> >> Here at Argentina we have an annual event about free software, this >> year schedule is: >> >> http://www.jornadasregionales.org/jrsl2010v2/schedule/index >> >> Could be interesting to present Pharo/Seaside/Pier here, may be next year..... >> > Yes. You can get some support for that from ESUG (e.g. travel costs). > > Noury > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 23, 2010

[Pharo-project] [update 1.2] #12205

by Marcus Denker

12205 ----- Issue 2619: ignore vm parameters with nil value in MessageTally, so it can be used in Cog Issue 1885: Disable Scroll Wrapping in PluggableListMorph Issue 3142: Updater package has no repository Issue 2876: setStandardClass: aClass methodSymbol: methodSym (first part) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Oct. 23, 2010

Re: [Pharo-project] Pavel can you check :)

by StÃ©phane Ducasse

When I clicked on a package, it got downloaded to the package cache using the writeDefinitions: method writeDefinitions: aCollection "initStream is an ugly hack until we have proper init defs" initializers := Dictionary new. (MCDependencySorter sortItems: aCollection) do: [:ea | ea accept: self] displayingProgress: 'Writing definitions...'. (Class superclassOrder: (initializers keys collect: [:each | Smalltalk classOrTraitNamed: each])) do: [:class | stream nextPutAll: (initializers at: class name) contents ]. Now it is bugging because initializers keys could contain a class that is not in the image and then put nil in the set The previous version of the method was: writeDefinitions: aCollection "initStream is an ugly hack until we have proper init defs" initStream := String new writeStream. (MCDependencySorter sortItems: aCollection) do: [:ea | ea accept: self] displayingProgress: 'Writing definitions...'. stream nextPutAll: initStream contents. - The previous version did not save initializers or may be different - Now the changes does not take into account classes that are not in the image. And this one should still be saved On Oct 23, 2010, at 12:22 PM, StÃ©phane Ducasse wrote: > Apparently when we browse > Compiler-eem.155 from the squeak trunk (ScriptLoader new addExtraRepositories) > > we get a problem because there is a nil in the set. > > Can you have a look? > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 23, 2010

[Pharo-project] Pavel can you check :)

by StÃ©phane Ducasse

Apparently when we browse Compiler-eem.155 from the squeak trunk (ScriptLoader new addExtraRepositories) we get a problem because there is a nil in the set. Can you have a look? Stef

Oct. 23, 2010

[Pharo-project] [update 1.2] #12204

by Marcus Denker

12204 ----- Issue 2868: allClassesUsingPool: allClassesUsingPoolVariable: for systemNavigation Issue 3046: BUG: LineMorph class>>from:to:color:width: returns a PolygonMorph Issue 3130: MethodReference >> #isLocalSelector should not be part of Monticello package Issue 3095: Character isLiteral is in wrong category Issue 3134: Cleaning uniclasses from smartRefStream -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Oct. 23, 2010

Re: [Pharo-project] Pharo article in linuxMag fr

by Noury Bouraqadi

On 22 oct. 2010, at 16:47, GermÃ¡n Arduino wrote: > Yes, very interesting. > > Here at Argentina we have an annual event about free software, this > year schedule is: > > http://www.jornadasregionales.org/jrsl2010v2/schedule/index > > Could be interesting to present Pharo/Seaside/Pier here, may be next year..... > Yes. You can get some support for that from ESUG (e.g. travel costs). Noury

Oct. 23, 2010

Re: [Pharo-project] some patterns I would like to **kill**

by Schwab,Wilhelm K

Stef, #respondsTo: - no argument. More defensive programming (aka masked bugs). Tests like this have their place, but are over-used in Squeak. Using #submorphs *might* be easier to defend. Morphs were designed to be usable in large numbers, and one might argue (playing Devil's Advocate here) that lookups are cheaper than the additional gc load. An instance variable could also cache stale information. Of course, for something that is accessed frequently, an instance variable avoids the lookup and I agree that it is cleaner and easier to read. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of stephane ducasse [stephane.ducasse(a)free.fr] Sent: Thursday, October 21, 2010 4:47 PM To: Pharo Development Subject: [Pharo-project] some patterns I would like to **kill** Hi I was reading Pluggable and friends I identified some patterns. The respondsTo plague Examples: color := self fillStyle asColor. (self labelMorph respondsTo: #enabled:) ifTrue: [self labelMorph enabled: self enabled]. (self labelMorph respondsTo: #interactionState:) ifTrue: [self labelMorph interactionState: self interactionState] (self labelMorph respondsTo: #enabled:) ifTrue: [ self labelMorph enabled: aBoolean]. (self enabled not and: [self label isMorph and: [(self label respondsTo: #enabled:) not]]) by construction a labelObject should be a morph and it should answer enabled: and the case where this is not the case should be fixed. Using submorphs to avoid one single inst var makes code quite ugly to read: labelMorph "Answer the actual label morph." self hasSubmorphs ifFalse: [^nil]. self firstSubmorph hasSubmorphs ifFalse: [^nil]. ^self firstSubmorph firstSubmorph _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 22, 2010

Re: [Pharo-project] Object>>at:modify:???

by Hernan Wilkinson

In a 1.1 image I have, the class HttpRequest is using that message... On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > I would like to deprecate the following method since nobody use it. > What do you think? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- *HernÃ¡n Wilkinson Agile Software Development, Teaching & Coaching Mobile: +54 - 911 - 4470 - 7207 email: hernan.wilkinson(a)10Pines.com site: http://www.10Pines.com <http://www.10pines.com/>*

Oct. 22, 2010

Re: [Pharo-project] About Object and Model

by Hernan Wilkinson

I like the idea... a lot of methods should be removed from Object and the idea of using traits for that is interesting. I support the motion! :-) On Thu, Oct 21, 2010 at 5:06 PM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > Hi guys > > I'm reading Object and I have the impression that some methods are in > Object while there should be on Model. > > when: anEventSelector > send: aMessageSelector > to: anObject > exclusive: aValueHolder > > okToClose.... > taskbarIcon > taskbarLabel > > May be some of these methods should grouped in traits, then applied to > Model. > Then if the user wants something else than Model to play the game he can > simply apply a trait. > > I think that this hierarchical decomposition is often forcing us to stack > methods in the wrong place > I think that the composition is way stronger and much more flexible than > hierarchical ordering. > tell me what you think. I would like to have a nice Object class. > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- *HernÃ¡n Wilkinson Agile Software Development, Teaching & Coaching Mobile: +54 - 911 - 4470 - 7207 email: hernan.wilkinson(a)10Pines.com site: http://www.10Pines.com <http://www.10pines.com/>*

Oct. 22, 2010