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

Re: [Pharo-project] A new GUI visual designer

by Richard Durr

Just a comment: :) The Interface Builder of Nextstep and Mac OS X â a closely Smalltalk-related and inspired system â creates the objects making up the user interface (it instantiates them) and then saves the state of everything into a nib/xib file (binary/xml) using the general object-persistency mechanism of Cocoa (NSKeyedArchiver). This file is then loaded when the application in question starts, all the freeze-dried objects in the UI-file are revived (awakened â not created) and then loaded into the object space of the app. This reminds me of the way, the Smalltalk Image works â except that the image stores the whole application object space where the nib/xib only stores the objects the interface is composed of. With Morphic there even exists an easy way to compose an interface with using original objects directly like or better than Interface Builder. But instead of using the image as a storage mechanism for the instantiated objects of a morphic-designed interface we are stuck with the textual distribution mechanism and discussing how we can for example use xml to do that. That is ironic, I think ^^ -- Sent from my DynaBook.

Feb. 13, 2011

Re: [Pharo-project] how to serialize Text?

by Schwab,Wilhelm K

Object readFrom:( Text fromString:'Hello' ) storeString You might also have a look at SIXX. I have not used it for anything big or for a long period of time, but no complaints so far, other than the output being more verbose than I might like. Still, it seems to be a good serializer. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Hilaire Fernandes [hilaire.fernandes(a)gmail.com] Sent: Sunday, February 13, 2011 10:53 AM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] how to serialize Text? I don't understand much the protocole with Text and if it is possible to serialize it. I can save a Text in a stream: |stream| stream := ReadWriteStream on: String new. myText storeOn: stream. But how to use the stream to create a new Text instance: The stream contents looks like: Text string: ''absd Hello with me c'' runs: (RunArray runs: #(5 5 6 2 2 ) values: ((Array new: 5)... I guess it is a trivial situation but I don't know how to do it Any clue? Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

Feb. 13, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by Ricardo Moran

Of course discussion is good. But turning your position into a religion and blaming other parties ignorance is bad. That's what the discussion seemed to be heading (at least to me) and I just tried to avoid that. Maybe I'm just too new in this community (and smalltalk in general, for that matter) and this is how you solve your discussions, but I just don't like arguments such: "I don't like it and everyone using it should die" :) Now that more voices have joined the thread I think we are actually getting somewhere :) Cheers Richo On Sun, Feb 13, 2011 at 7:58 AM, Alain Plantec <alain.plantec(a)yahoo.com>wrote: > Le 13/02/2011 04:05, Ricardo Moran a Ã©crit : > > Ok, guys... I'm sorry to interrupt this polite discussion, but this is >> taking nowhere. >> > no, it allows people to make their own opinion. > interesting thread. > > Now I can say that I would be more for getting rid of case of. > > thanks > Alain > > > >

Feb. 13, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #55 on issue 3583 by tudor.gi...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Ok, I think I see where the confusion came from. If you load the slice of Benjamin in the Pharo 1.2, everything works fine. If you load it in **Pharo-Core** then it does not work. So, I tracked a bit the errors in Pharo-Core. The reason the Workspace does not work is that apparently after the loading of the slice, somehow Workspace class does not understand open anymore. If I add this method, everything works fine. The code browser works fine, but when trying to browse a class, we get an error because a textMorph is not initialized. I do not know why this happens. Can anyone take a look and confirm?

Feb. 13, 2011

[Pharo-project] [update 1.3] #13054

by laurent laffont

13054 ----- COTDC - 7. CodeAnnotationMorph - A.Plantec - 8. WikiStyleHelpBuilder - L.Laffont my first integration alone, hope I've done it right :) Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Feb. 13, 2011

[Pharo-project] how to serialize Text?

by Hilaire Fernandes

I don't understand much the protocole with Text and if it is possible to serialize it. I can save a Text in a stream: |stream| stream := ReadWriteStream on: String new. myText storeOn: stream. But how to use the stream to create a new Text instance: The stream contents looks like: Text string: ''absd Hello with me c'' runs: (RunArray runs: #(5 5 6 2 2 ) values: ((Array new: 5)... I guess it is a trivial situation but I don't know how to do it Any clue? Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

Feb. 13, 2011

Re: [Pharo-project] [COTDC] 9 - HTTPDownloadRequest

by laurent laffont

On Sat, Feb 12, 2011 at 5:44 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Today: HTTPDownloadRequest > It seems to me that all classes in category System-Download can be removed. They are not referenced outside this category. If not, the comment I propose: I encapsulate an HTTP request which can be queued in an HTTPLoader instance. Laurent. > > > 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 > >

Feb. 13, 2011

[Pharo-project] writing to the transcript stream

by Hilaire Fernandes

I try the following Text fromUser storeOn: Transcript It failed, as ThreadTranscript is not a Stream, but according to PBE, Transcript is a Stream. Should I fill a bug ticket or is it a misuse? Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

Feb. 13, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by Benoit St-Jean

Let's get to the point here... Most people will tell you it's an awful "beast" that doesn't belong to the OO and Smalltalk world. If I *love* case statements and I absolutely need them, I can code in C. If I *love* case statements and I absolutely need them, nothing prevents me from adding them to the image as my own-superoptimized extension. You'll always find something, someone, somewhere who could argue about the need for such a thing but in reality, I guess this method has always bugged most Smalltalkers... It's ugly, not OO, not good style and good practice, not essential and not needed by 99% of the people here (and if it's sooooooooooo needed, how do you explain that all other Smalltalk vendors haven't implement it as part of their core libraries ?). So let's vote (you won't argue against democracy, won't you?!) for the removal of #caseOf:otherwise: and let's move forward onto more important business. On a less serious note, let's all remember what Spock said: "Were I to invoke logic, however, logic clearly dictates that the needs of the many outweigh the needs of the few" Let's remove this thing! +1 P.S. Performance-wise, if you always need "optimized" code, you can always rely on primitives & plugins... Let's not go performance-frenzy here! We don't want to end up in an environment where all the code is unreadable... Clarity & simplicity are good, not evil in Smalltalk! ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein) ________________________________ From: Levente Uzonyi <leves(a)elte.hu> To: Pharo-project(a)lists.gforge.inria.fr Sent: Sun, February 13, 2011 8:50:53 AM Subject: Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise: On Sun, 13 Feb 2011, Sven Van Caekenberghe wrote: > > On 12 Feb 2011, at 18:41, Levente Uzonyi wrote: > >> ~27x slowdown in this case. > > I personally never heard of #caseOf:otherwise ! > > It feels like a hack that is not often needed. You don't need it often, but it's sometimes useful. > > If after writing correct code you need to optimize integer/byte handling, there >are many solutions, check any book on algorithms, most of them are using table >dispatch. The blocks of #caseOf: are not just boilerplate code, you can evaluate any expression there. It's cumbersome to do that with table based dispatch. > > Another problem in your benchmark is that you keep the creation of the dynamic >array inside the code to measure, while in the compiler primitive case it is of >course compiled away, that alone makes a huge difference: It's not a problem, it's intentional. See the mail that I replied to. Levente > > (timings on my machine) > > [ 1 to: 10 do: [ :each | > each > caseOf: { > [ 1 ] -> [ $a ]. > [ 2 ] -> [ $b ]. > [ 3 ] -> [ $c ]. > [ 4 ] -> [ $d ]. > [ 5 ] -> [ $e ] } > otherwise: [ $x ] ] ] bench. > '8,920,000 per second.' > > [ 1 to: 10 do: [ :each | > ({ > [ 1 ] -> [ $a ]. > [ 2 ] -> [ $b ]. > [ 3 ] -> [ $c ]. > [ 4 ] -> [ $d ]. > [ 5 ] -> [ $e ] } > detect: [ :ea | ea key value = each ] > ifNone: [ [ $x ] ]) value ] ] bench. > '70,600 per second.' > > | actions | > actions := { [ $a ]. [ $b ]. [ $c ]. [ $d ]. [ $e ]. [ $x ]. [ $x ]. [ $x ]. [ >$x ]. [ $x ]. }. > [ 1 to: 10 do: [ :each | > (actions at: each) value ] ] bench. > '3,230,000 per second.' > > | letters | > letters := 'abcdexxxxx'. > [ 1 to: 10 do: [ :each | > letters at: each ] ] bench. > '8,930,000 per second.' > > If other Smalltalks can live without it, so can we. > > Sven > > >

Feb. 13, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by Levente Uzonyi

On Sun, 13 Feb 2011, Sven Van Caekenberghe wrote: > > On 12 Feb 2011, at 18:41, Levente Uzonyi wrote: > >> ~27x slowdown in this case. > > I personally never heard of #caseOf:otherwise ! > > It feels like a hack that is not often needed. You don't need it often, but it's sometimes useful. > > If after writing correct code you need to optimize integer/byte handling, there are many solutions, check any book on algorithms, most of them are using table dispatch. The blocks of #caseOf: are not just boilerplate code, you can evaluate any expression there. It's cumbersome to do that with table based dispatch. > > Another problem in your benchmark is that you keep the creation of the dynamic array inside the code to measure, while in the compiler primitive case it is of course compiled away, that alone makes a huge difference: It's not a problem, it's intentional. See the mail that I replied to. Levente > > (timings on my machine) > > [ 1 to: 10 do: [ :each | > each > caseOf: { > [ 1 ] -> [ $a ]. > [ 2 ] -> [ $b ]. > [ 3 ] -> [ $c ]. > [ 4 ] -> [ $d ]. > [ 5 ] -> [ $e ] } > otherwise: [ $x ] ] ] bench. > '8,920,000 per second.' > > [ 1 to: 10 do: [ :each | > ({ > [ 1 ] -> [ $a ]. > [ 2 ] -> [ $b ]. > [ 3 ] -> [ $c ]. > [ 4 ] -> [ $d ]. > [ 5 ] -> [ $e ] } > detect: [ :ea | ea key value = each ] > ifNone: [ [ $x ] ]) value ] ] bench. > '70,600 per second.' > > | actions | > actions := { [ $a ]. [ $b ]. [ $c ]. [ $d ]. [ $e ]. [ $x ]. [ $x ]. [ $x ]. [ $x ]. [ $x ]. }. > [ 1 to: 10 do: [ :each | > (actions at: each) value ] ] bench. > '3,230,000 per second.' > > | letters | > letters := 'abcdexxxxx'. > [ 1 to: 10 do: [ :each | > letters at: each ] ] bench. > '8,930,000 per second.' > > If other Smalltalks can live without it, so can we. > > Sven > > >

Feb. 13, 2011