February 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [SPAM] Re: INRIA-CEA-EDF Deep into Smalltalk School registration open

by Sven Van Caekenberghe

On 09 Feb 2011, at 19:02, StÃ©phane Ducasse wrote: > Yes! > I do not know when but a guy will come and record everything :) +1

Feb. 9, 2011

Re: [Pharo-project] what is the goal of warpImage: aForm transform: aTransform

by Igor Stasenko

i guess it is related to warpBlt engine, which can zoom/rotate forms when blitting and do other distortions.. On 9 February 2011 17:03, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > there are no sender in Pharo 1.3? > SMx does not have them. > > Stef > > > -- Best regards, Igor Stasenko AKA sig.

Feb. 9, 2011

Re: [Pharo-project] INRIA-CEA-EDF Deep into Smalltalk School registration open

by Esteban Lorenzano

That would be really cool. I was hoping to go and I can't, so at least having the videos to see, is a consolation :D El 09/02/2011, a las 3:02p.m., StÃ©phane Ducasse escribiÃ³: > Yes! > I do not know when but a guy will come and record everything :) > > > On Feb 9, 2011, at 3:26 PM, Sean P. DeNigris wrote: > >> >> Will you post videos? I'll be heading to Smalltalk Solutions, but I'm always >> hungry to learn more, more, more!!! >> >> Sean >> -- >> View this message in context: http://forum.world.st/INRIA-CEA-EDF-Deep-into-Smalltalk-School-registration… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > >

Feb. 9, 2011

Re: [Pharo-project] [COTDC] 6 - StandardFonts

by Sven Van Caekenberghe

On 09 Feb 2011, at 17:55, Laurent Laffont wrote: > Today: StandardFonts > > (really at random this time :) > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent I am a facade and a global reference to actual fonts to be used system wide in a number of predefined categories. I also provide methods to interactively choose these fonts, to reset all fonts to some default value, to set larger demo fonts, to construct a font menu and to manipulate the current settings as an external specification. The font categories that I know of are: ButtonFont, CodeFont, HaloFont, ListFont, MenuFont and WindowTitleFont

Feb. 9, 2011

Re: [Pharo-project] Issue 3688 in pharo: Network primitives missing in the image

by pharo＠googlecode.com

Updates: Status: Fixed Comment #1 on issue 3688 by stephane...(a)gmail.com: Network primitives missing in the image http://code.google.com/p/pharo/issues/detail?id=3688 jannik gimme a cs :)

Feb. 9, 2011

Re: [Pharo-project] about FS: a roadmap

by StÃ©phane Ducasse

I was bored in the train so ... I did that and now I will do it regularly. - I added trace to gather the exact type of arguments.... and - moved FSLocator out of core and in resolver. - added comments to FSFileSystem>>fileExist: and friends. - changed category name error handling -> error raising - better argument name for createDirectory - added comment to createDirectory - added comment to copy and friends - added comment to ensureDirectory: - added comment to isDirectory: - added comment to isFile: - added comment to open: aStringOrPath writable: aBoolean - added comment to readStreamOn: aStringOrPath Next step - should probably rename FileExists as FileAlreadyExistsError Stef

Feb. 9, 2011

Re: [Pharo-project] about FS: a roadmap

by StÃ©phane Ducasse

Excellnt colin >> > I've published my changes to the SqueakSource FS repository. However, > I think we should abandon them, for several reasons: > > They're based on a quite old version of FS, and they touch a *lot* of > methods. So there are a ton of conflicts, and merging them into the > latest versions that are on SqueakSource is really difficult to do > correctly. > > Also, I think they're ultimately going in the wrong direction, and we > should try to come up with a better solution to the Path/Reference > naming problem. Ok I guess that with good comment and a bit of package reorganization as I did it we can leave with FSPath. > >> I will integrate the fixes of damien. >> I would like to have >> - a better help (already there). >> - Rename workingDirectory as workingDirectoryPath >> - add workingDirectory returning a FSReference > > Agreed. > >> - Every method with an adequate comment. The idea is that the comment should describe what the method does when we do not see its >> body: let us try to think a bit in JavaDoc or Ruby Yard fashion for once. > > Also agreed, at least for the public API. Comments should be more > sparse for the private stuff. > >> - Use rename primitives >> - Have the possibility to create empty file >> - Clean identification of implementation tests and black box tests >> - Integrate Gemstone fixes > > Agreed. > >> - Stream usage clearly identified to support Gemstone migration) >> - Onion like structure so that we can have one or two packages that are really the core >> (yes I still want a minimal kernel). > > I'd like to see FS split into separate packages: > > - Core (basic, API, resolvers, enumeration and exceptions) > - MemoryFS > - DiskFS > - ZipFS > - GitFS > - CurlFS > - FileStream compatibility > - ANSI streams > - Xtreams integration > > This will make it easier to have a minimal installation (just Core and > DiskFS) as well as port to platforms like VW and Gemstone > >> - Check the file API creation: >> old, new, exist.... > > Sure, but that stuff is actually much simpler when you have read-only > and write-only streams. > >> - Prepare a migration path for 1.3 >> - Fix filesystem workingDirectory isWorkingDirectory returns false. >> - rename fileDoesNotExist: and friends do convey that its goal is mainly to raise en exception >> raiseFileDoesNotExistsFor: > > Sure. > >> Of course I would like to avoid to throw away all that good energy so I hope to collaborate with colin. >> We will see what will happen. I can understand that he has another agenda/time frame but we should >> move on this front. So all my code will be publicly available in the SqueakSource/fs repository. > > Cool! > > Colin

Feb. 9, 2011

Re: [Pharo-project] INRIA-CEA-EDF Deep into Smalltalk School registration open

by StÃ©phane Ducasse

Yes! I do not know when but a guy will come and record everything :) On Feb 9, 2011, at 3:26 PM, Sean P. DeNigris wrote: > > Will you post videos? I'll be heading to Smalltalk Solutions, but I'm always > hungry to learn more, more, more!!! > > Sean > -- > View this message in context: http://forum.world.st/INRIA-CEA-EDF-Deep-into-Smalltalk-School-registration… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Feb. 9, 2011

[Pharo-project] handlerForBlueButtonDown: anEvent

by stephane ducasse

Gary I was wondering if "anEvent handler ifNil:[^self]." should not be uncommented in. Now if it works like that this is better since it means that are not hanging around with a nil. Stef handlerForBlueButtonDown: anEvent "Return the (prospective) handler for a mouse down event. The handler is temporarily installed and can be used for morphs further down the hierarchy to negotiate whether the inner or the outer morph should finally handle the event. Note: Halos handle blue button events themselves so we will only be asked if there is currently no halo on top of us. Check whtehr halods are enabled (for deployment)." self wantsHaloFromClick ifFalse:[^nil]. "anEvent handler ifNil:[^self]." (anEvent shiftPressed) ifFalse:[^nil] "let outer guy have it" ifTrue:[^self] "let me have it"

Feb. 9, 2011

[Pharo-project] deleteAllHalos

by stephane ducasse

PasteUpMorph>>abandonAllHalos self flag: #arNote. "Remove the method" ^self deleteAllHalos PasteUpMorph>>deleteAllHalos self halt. self haloMorphs do: [:each | (each target isKindOf: SelectionMorph) ifTrue: [each target delete]]. self hands do: [:each | each removeHalo] it looks to me that this is totally useless :). self haloMorphs always returns #() now even when I completely comment the method deleteAllHalos destroying a morph or a selectionMorph destroy all the halos and the selected morph. Does anybody has experience with that? stef

Feb. 9, 2011