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

[Pharo-project] [update 1.1] #11195
by StÃ©phane Ducasse Feb. 5, 2010

Feb. 5, 2010

- Issue 1910: readOnlyFileNamed:do: much nicer code :) - Issue 1913: ByteArray cleaning using #[] where possible

1 0

[Pharo-project] Lectures at Barcelona 8-12 Feb 2010
by stephane ducasse Feb. 5, 2010

Feb. 5, 2010

Hi guys I will give some lectures at barcelona on advanced OO design. I will also have fun with Smalltalk the wednesday. If you are in the region and want to meet me and exchange code... You are welcome just drop to me or jordi a mail I will be teaching at Polytechnica de Catalunya Jordi knows where :) Stef

2 1

[Pharo-project] [update 1.1] #11194
by StÃ©phane Ducasse Feb. 5, 2010

Feb. 5, 2010

11194 ----- - Issue 1936: background morph for the world that resizes with the main window. - Issue 1919: SystemWindow >> activate, to avoid sending #addPaneSplitters if the window isCollapsed - Issue 1932: UTF8TextConverter ?? Latin1TextConverter initializeLatin1Encodings. MacRomanTextConverter initializeLatin1Encodings.

1 0

[Pharo-project] Fwd: October 2006 Agreement from Apple to VPRI regarding License changes
by Torsten Bergmann Feb. 4, 2010

Feb. 4, 2010

see http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-February/144099… -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

3 2

[Pharo-project] readOnlyFileNamed:do: vs. ...
by StÃ©phane Ducasse Feb. 4, 2010

Feb. 4, 2010

Nicolas I saw that in squeak you changed and use readOnlyFileNamed:do: I like it but I would like to understand what is the key advantage fromFileNamed: aName FileStream readOnlyFileNamed: aName do: [:stream | stream setConverterForCode. self fileInFrom: stream] fromFileNamed: aName | stream | stream := FileStream readOnlyFileNamed: aName. stream setConverterForCode. [self fileInFrom: stream] ensure: [stream close].

6 17

[Pharo-project] Bug in PharoCore1.1ALPHA [Latest update: #11192]
by Yanni Chiu Feb. 4, 2010

Feb. 4, 2010

When attempting to load Seaside-2.8, with the image updated to 11192, I got: UndefinedObject(Object)>>doesNotUnderstand: #do: WriteStream(Stream)>>nextPutAll: WriteStream>>nextPutAll: WriteStream(Stream)>>basicNextPutAll: UTF8TextConverter(TextConverter)>>nextPutAll:toStream: ByteString(String)>>convertToWithConverter: WAKomEncoded39 class>>setUpConversionTables WAKomEncoded39 class>>initialize It actually gave me an emergency evaluator, and failed to save the entire stack trace to PharoDebug.log - maybe due to UTF8 issues. I had to use the send bug report feature to capture the stack trace. I think the problem is that WAKomEncoded39 is setting things up for codepoints 0..255, but the newly optimized UTF8TextConverter has nil entries for codepoints less than 128. -- Yanni VM: Mac OS - intel - 1058 - Squeak3.8.1 of '28 Aug 2006' [latest update: #6747] Squeak VM 4.2.1b1 Image: PharoCore1.1ALPHA [Latest update: #11192] --- The full stack --- UndefinedObject(Object)>>doesNotUnderstand: #do: WriteStream(Stream)>>nextPutAll: WriteStream>>nextPutAll: WriteStream(Stream)>>basicNextPutAll: UTF8TextConverter(TextConverter)>>nextPutAll:toStream: ByteString(String)>>convertToWithConverter: WAKomEncoded39 class>>setUpConversionTables WAKomEncoded39 class>>initialize MCMethodDefinition>>postloadOver: [] in [] in [] in MCPackageLoader>>basicLoad [] in [] in OrderedCollection(SequenceableCollection)>>do:displayingProgress: OrderedCollection(SequenceableCollection)>>withIndexDo: [] in OrderedCollection(SequenceableCollection)>>do:displayingProgress: [] in ProgressInitiationException>>defaultAction BlockClosure>>ensure: ProgressInitiationException>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: ProgressInitiationException(Exception)>>signal ProgressInitiationException>>display:at:from:to:during: ProgressInitiationException class>>display:at:from:to:during: ByteString(String)>>displayProgressAt:from:to:during: OrderedCollection(SequenceableCollection)>>do:displayingProgress: [] in [] in MCPackageLoader>>basicLoad BlockClosure>>on:do: [] in MCPackageLoader>>basicLoad BlockClosure>>ensure: MCPackageLoader>>basicLoad [] in MCPackageLoader>>loadWithNameLike: [] in MCPackageLoader>>useChangeSetNamed:during: BlockClosure>>ensure: MCPackageLoader>>useChangeSetNamed:during: MCPackageLoader>>useNewChangeSetNamedLike:during: MCPackageLoader>>loadWithNameLike: MCVersionLoader>>loadWithNameLike: MCVersionLoader>>load - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - GoferLoad>>execute Gofer>>execute:do: Gofer>>execute: Gofer>>load [] in UndefinedObject>>DoIt [] in BlockClosure>>valueSupplyingAnswers: BlockClosure>>on:do: BlockClosure>>valueSupplyingAnswers: UndefinedObject>>DoIt Compiler>>evaluate:in:to:notifying:ifFail:logged: Compiler class>>evaluate:for:notifying:logged: Compiler class>>evaluate:for:logged: Compiler class>>evaluate:logged: [] in [] in MultiByteFileStream(PositionableStream)>>fileInAnnouncing: BlockClosure>>on:do: [] in MultiByteFileStream(PositionableStream)>>fileInAnnouncing: [] in ProgressInitiationException>>defaultAction BlockClosure>>ensure: ProgressInitiationException>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: ProgressInitiationException(Exception)>>signal ProgressInitiationException>>display:at:from:to:during: ProgressInitiationException class>>display:at:from:to:during: ByteString(String)>>displayProgressAt:from:to:during: MultiByteFileStream(PositionableStream)>>fileInAnnouncing: MultiByteFileStream(FileStream)>>fileIn MultiByteFileStream>>fileIn FileStream class>>fileIn: SimpleServiceEntry>>performServiceFor: [] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: BlockClosure>>ensure: CursorWithMask(Cursor)>>showWhile: ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: ToggleMenuItemMorph(MenuItemMorph)>>mouseUp: ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp: MouseButtonEvent>>sentTo: ToggleMenuItemMorph(Morph)>>handleEvent: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>dispatchEvent:with: ToggleMenuItemMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>dispatchEvent:with: MenuMorph(Morph)>>processEvent:using: MenuMorph(Morph)>>processEvent: MenuMorph>>handleFocusEvent: [] in HandMorph>>sendFocusEvent:to:clear: [] in PasteUpMorph>>becomeActiveDuring: BlockClosure>>on:do: PasteUpMorph>>becomeActiveDuring: HandMorph>>sendFocusEvent:to:clear: HandMorph>>sendEvent:focus:clear: HandMorph>>sendMouseEvent: HandMorph>>handleEvent: HandMorph>>processEvents [] in WorldState>>doOneCycleNowFor: Array(SequenceableCollection)>>do: WorldState>>handsDo: WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: PasteUpMorph>>doOneCycle [] in Project class>>spawnNewProcess [] in BlockClosure>>newProcess

4 9

[Pharo-project] downloading Pharo by Example
by Ralph Boland Feb. 4, 2010

Feb. 4, 2010

When I attempted to download the Pharo By Example book at: http://www.pharobyexample.org/ I got the download error: /tmp/PBE1-2009-10-28-2.pdf could not be opened because the associated helper application does not exist. Change the association in your preferences. Can anyone suggest what the problem is? I am running Ubuntu 9.10 and downloading using the version of Firefox coming with 9.10. Regards, Ralph Boland -- Had a wife and kids in Florida, Jack (Nicklaus) Went out for a "ride" but I couldn't get back As a ten timer being hunted down OR When the wife found out who I was knowing (biblically) I hit a hydrant and I just kept going. ...

3 2

[Pharo-project] Do you want to discuss about papers?
by Mariano Martinez Peck Feb. 4, 2010

Feb. 4, 2010

Hi folks. Before sending this email to all smalltalk mailing lists, I first wanted to ask you what do you think. I am new in the world of the research and about reading and discussing about papers. If what I propose already exist, forget this mail and please tell me where is it. I was thinking to have a place, an environment (mailing list), where we can freely discuss about Smalltalk or OO in general papers. At the beginning I though to put this inside the Pharo mailing list but then I though it is better to do a new mailing list where all smalltalkers of all flavors can join and discuss. The main purpose about that list is: - be able to FREELY discuss about papers about Smalltalk or OO in general. I say freely because maybe someone gives an opinion of a paper that the person who wrote it is also in this place. We are all professional and I think we can discuss with respect. - LEARN. Other uses: - Don't reinvent the wheel. Maybe I wanted to do something and I read that XXX person did YYY. So, I can look at it. - Be aware of what other people is doing, working, writing and learning - Have different opinions of a certain topic / paper. - A little step to join all the Smalltalk community in one place. We can meet people, join forces, etc. - Help in the preparation, ANN, collaborate, etc in Workshops, conferences, and so on - Ask for help on review. Several times someone has several papers to review for a certain conference. This can be a place to ask for that help. - Publish papers that were rejected from someone. How many times some papers where rejected but do you still read it and find it useful ? - Ask for feedback for a paper before submitting it in a conference/workshop - Educate people and being educated - Share latex template, commands, or tricks related to smalltalk code for example - Discuss about research in general - Ask for a certain topic. Suppose I want to start to work in XXX topic, I can ask to see if someone knows related papers or work. - others I will give you an example: this week I have been reading a paper about LOOM - Large Object Oriented Memory. This paper is from ECOOP 1986 (the only thing an Argentinian can think about that year is Maradona's goals to England in Mexico ;) ). I was one year old at that time. LOOM was based in Smalltalk 80. I had no idea about that. I had to read some chapters of the blue book first in order to then understand LOOM. I have ever seen LOOM code, I don't know what happened with it, etc. So, maybe there is someone who even saw LOOM in live, he saw the code, he knows what happened, if it worked really or not, the advantages and drawbacks, the repercussion it had, etc. That information, those opinions, you cannot get it from other place. So, what do you think? Do you like the idea or has no sense ? If you like and has sense, I will create the mailing list and send it to all Smalltalk mailing lists I know. In two words: DISCUSS AND LEARN. Cheers Mariano

9 18

Feb. 4, 2010

Hi pharoers I'm happy that pharo is used to create wealth and I wanted to share that with you ;) Stef >>> We're only using it for an internal application right now, so the details wouldn't be very interesting. I suppose you can call it a "medical case management system". It uses Seaside, a bit of Magritte and Magma. >>> The application replaces a Ruby on Rails application that I built for them 4 years ago. I switched to Squeak Smalltalk last summer and I waited until you guys got Pharo to beta status, then I switched the server to Pharo in October. >>> Thanks for all of the hard work you guys are doing! I really appreciate it and enjoy using Pharo and following your work.

1 0

[Pharo-project] Newbie question deploying smalltalk applications
by Nathan Tuttle Feb. 4, 2010

Feb. 4, 2010

I created a CRC calculating algorithm and I want to be able to deploy my application for other people to use. I am not sure how to package an image so that it is user friendly. Any help would be nice. Thanks

6 17