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

Re: [Pharo-project] Why do we use Pharo? a.k.a. rethinking Pharo marketing

by Helene Bilbo

StÃ©phane Ducasse wrote > > On Feb 20, 2012, at 2:26 AM, Ben Coman wrote: > >>> Pharo a plastic language to build evolvable and debuggable applications. > >>> Plastic = "(in science and technology) of or relating to the permanent >>> deformation of a solid without fracture by the temporary application of >>> force." > >> "General term for a fake, or in reference to a shallow person." >> http://onlineslangdictionary.com/meaning-definition-of/plastic > > > Yes I looked at that and I was not happy with it. > > resilience may be better > Even the connotation of plastic surgery is perfect: don't like the nose of your program? change it! "Plastic" is disputable. That's exactly what you want to be :) Resilience on the other hand sounds a lot like "coping" and "hardiness". Very gray and motivated from the negative. -- View this message in context: http://forum.world.st/Why-do-we-use-Pharo-a-k-a-rethinking-Pharo-marketing-… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 20, 2012

Re: [Pharo-project] garbage collection

by Milan Mimica

On 20 February 2012 16:47, Milan Mimica <milan.mimica(a)gmail.com> wrote: > > Still, that should be causing major problems in my case. > I am missing a "not" somewhere here. -- Milan Mimica http://sparklet.sf.net

Feb. 20, 2012

Re: [Pharo-project] garbage collection

by Guido Stepken

Am 20.02.2012 17:51 schrieb "Igor Stasenko" <siguctua(a)gmail.com>: ... > so i think we having a side effect of running image stably for quite a > long duration (and this is positive part) , but which uncovering such > bags :) There are a lot more of leaks deep in the core of Pharo that make the machine dog-slow and absolutely unusable for long-term purposes. A resource watchdog would be nice to have, hat keep operators informed. :-) Have fun debugging, Guido Stepken

Feb. 20, 2012

Re: [Pharo-project] garbage collection

by Igor Stasenko

On 20 February 2012 16:47, Milan Mimica <milan.mimica(a)gmail.com> wrote: > On 14 February 2012 23:54, Milan Mimica <milan.mimica(a)gmail.com> wrote: >> >> On 14 February 2012 22:55, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >>> >>> semaphores collect: [:sema | >>> Â Â Â Â sema -> >>> Â Â Â Â Â Â Â Â (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == >>> semaphores ] ] ) ] >>> >>> Can you try invoking it on your image , look for those who has an >>> empty array, which will mean that there is no references to it except >>> semaphore table itself. >> >> >> There is 69 of such semaphores, out ofÂ hundredsÂ in total. Not much :-/ >> On a normal image there is only a few. > > > Should say that the 69 leaked semaphores are probably there because of the > bug that leaks a semaphore on each image save. Still, that should be causing > major problems in my case. > Well, that should not cause problem unless you keep the image running and running and running (so garbage accumulates). And of course, if you restart an image, an external semaphore table wiped out.. so i think we having a side effect of running image stably for quite a long duration (and this is positive part) , but which uncovering such bags :) > > -- > Milan Mimica > http://sparklet.sf.net -- Best regards, Igor Stasenko.

Feb. 20, 2012

Re: [Pharo-project] Why do we use Pharo? a.k.a. rethinking Pharo marketing

by Schwab,Wilhelm K

Hmmmm. I was thinking about Pharo as a cross-platform Smalltalk, but that pretty much says the same thing :) You are missing the cross-platform part though, or so it seems. Also, Smalltalk's malleability does not rule out the use of number crunching and other libraries, which can be very nicely adapted into the system, one might say, in a malleable way :) Details aside, I like where you are going. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Fernando Olivero [fernando.olivero(a)usi.ch] Sent: Monday, February 20, 2012 7:56 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Why do we use Pharo? a.k.a. rethinking Pharo marketing What about: Pharo a MALEABLE language to build evolvable and debuggable applications. Fernando On Mon, Feb 20, 2012 at 11:03 AM, Guido Stepken <gstepken(a)googlemail.com> wrote: > http://en.m.wikipedia.org/wiki/Plasticity > > Am 20.02.2012 09:24 schrieb "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr<mailto:stephane.ducasse@inria.fr>>: > > On Feb 20, 2012, at 2:26 AM, Ben Coman wrote: > >> StÃ©phane Ducasse wrote: >>> I would like to get from you why you use Pharo? >>> >>> >>> >>> After thinking a lot about that recently I think that I would like to have something like that: >>> >>> Pharo a plastic language to build evolvable and debuggable applications. With Pharo and its ecosystem you can build powerful tools (web application, data management, business processesâ¦). Pharo philosophy is driven by domain driven design. Modeling is agile. Pharo is an executable modeling language. Pharo is not only a language but an infrastructure with powerful tools like Moose. >>> Plastic = "(in science and technology) of or relating to the permanent deformation of a solid without fracture by the temporary application of force." >>> >> I agree with your usage of "plastic", but there are some unfortunate english slang associations that you might want to stay away from... >> "General term for a fake, or in reference to a shallow person." >> http://onlineslangdictionary.com/meaning-definition-of/plastic > > > Yes I looked at that and I was not happy with it. > > resilience may be better > > >> >> Perhaps "ductile" would suit the same purpose. >> "able to undergo change of form without breaking" >> http://dictionary.reference.com/browse/ductile >> >> There is also "malleable" (but I think the shorter syllables of ductile is nicer to read) >> http://www.thefreedictionary.com/malleable >> >> cheers, -ben >> >>> Pharo: ease of modeling, essence of agile, close to objects all the time. >>> Stef >>> >>> >> >> > >

Feb. 20, 2012

Re: [Pharo-project] error trying to upload to ss3

by Camillo Bruni

yeah this is the annoying FSStream question... use FSReference >> #fileStreamWritable:do: for now... On 2012-02-20, at 16:53, StÃ©phane Ducasse wrote: > camillo > > I'm trying your script with the latest image. > > > | f files| > f := FSFilesystem disk workingDirectory / 'www.squeaksource.com' / 'Kozen'. > files := f glob: [ :each| each basename endsWith: '.mcz']. > > files do: [ :file ||entity stream| > stream := file readStream. > (entity := ZnStreamingEntity type: ZnMimeType applicationOctetStream) > stream: stream; > contentLength: stream size. > Transcript show: file; cr. > "upload the version to gemstone" > ZnClient new > systemPolicy; > beOneShot; > signalProgress: true; > ifFail: [ :exception | Transcript show: file basename; show: ' '; print: exception ]; > username: 'sd' password: 'sn00py_'; > entity: entity; > url: ( 'http://ss3.gemstone.com/ss/Kozen/', file basename); > put ] > displayingProgress: 'Uploading mcz' > > > apparently FSReadStream does not know isBinary > > > > streamFrom: inputStream to: outputStream size: totalSize > | bufferSize buffer leftToRead | > bufferSize := 4096 min: totalSize. > buffer := (inputStream isBinary ifTrue: [ ByteArray ] ifFalse: [ String ]) new: bufferSize. > ^^^^^^^^^^ > leftToRead := totalSize. > [ leftToRead > 0 ] > whileTrue: [ | readCount | > readCount := bufferSize min: leftToRead. > inputStream next: readCount into: buffer. > leftToRead := leftToRead - readCount. > outputStream next: readCount putAll: buffer startingAt: 1 ]

Feb. 20, 2012

Re: [Pharo-project] error trying to upload to ss3

by Sven Van Caekenberghe

This is silly, because Zinc also only works with or needs binary streams. But I have to know what kind of stream comes in, so I think it would not hurt to implement isBinary "I am always binary" ^ true Sven On 20 Feb 2012, at 16:53, StÃ©phane Ducasse wrote: > camillo > > I'm trying your script with the latest image. > > > | f files| > f := FSFilesystem disk workingDirectory / 'www.squeaksource.com' / 'Kozen'. > files := f glob: [ :each| each basename endsWith: '.mcz']. > > files do: [ :file ||entity stream| > stream := file readStream. > (entity := ZnStreamingEntity type: ZnMimeType applicationOctetStream) > stream: stream; > contentLength: stream size. > Transcript show: file; cr. > "upload the version to gemstone" > ZnClient new > systemPolicy; > beOneShot; > signalProgress: true; > ifFail: [ :exception | Transcript show: file basename; show: ' '; print: exception ]; > username: 'sd' password: 'sn00py_'; > entity: entity; > url: ( 'http://ss3.gemstone.com/ss/Kozen/', file basename); > put ] > displayingProgress: 'Uploading mcz' > > > apparently FSReadStream does not know isBinary > > > > streamFrom: inputStream to: outputStream size: totalSize > | bufferSize buffer leftToRead | > bufferSize := 4096 min: totalSize. > buffer := (inputStream isBinary ifTrue: [ ByteArray ] ifFalse: [ String ]) new: bufferSize. > ^^^^^^^^^^ > leftToRead := totalSize. > [ leftToRead > 0 ] > whileTrue: [ | readCount | > readCount := bufferSize min: leftToRead. > inputStream next: readCount into: buffer. > leftToRead := leftToRead - readCount. > outputStream next: readCount putAll: buffer startingAt: 1 ]

Feb. 20, 2012

Re: [Pharo-project] error trying to upload to ss3

by Mariano Martinez Peck

On Mon, Feb 20, 2012 at 4:53 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > camillo > > I'm trying your script with the latest image. > > > | f files| > f := FSFilesystem disk workingDirectory / 'www.squeaksource.com' / > 'Kozen'. > files := f glob: [ :each| each basename endsWith: '.mcz']. > > files do: [ :file ||entity stream| > stream := file readStream. > (entity := ZnStreamingEntity type: ZnMimeType > applicationOctetStream) > stream: stream; > contentLength: stream size. > Transcript show: file; cr. > "upload the version to gemstone" > ZnClient new > systemPolicy; > beOneShot; > signalProgress: true; > ifFail: [ :exception | Transcript show: file basename; > show: ' '; print: exception ]; > username: 'sd' password: 'sn00py_'; > entity: entity; > url: ( 'http://ss3.gemstone.com/ss/Kozen/', file basename); > put ] > displayingProgress: 'Uploading mcz' > > > apparently FSReadStream does not know isBinary > > All FS streams do not understand #isBinary nor #binary since they are always binary. > > > streamFrom: inputStream to: outputStream size: totalSize > | bufferSize buffer leftToRead | > bufferSize := 4096 min: totalSize. > buffer := (inputStream isBinary ifTrue: [ ByteArray ] ifFalse: [ > String ]) new: bufferSize. > ^^^^^^^^^^ > leftToRead := totalSize. > [ leftToRead > 0 ] > whileTrue: [ | readCount | > readCount := bufferSize min: leftToRead. > inputStream next: readCount into: buffer. > leftToRead := leftToRead - readCount. > outputStream next: readCount putAll: buffer > startingAt: 1 ] > -- Mariano http://marianopeck.wordpress.com

Feb. 20, 2012

[Pharo-project] error trying to upload to ss3

by StÃ©phane Ducasse

camillo I'm trying your script with the latest image. | f files| f := FSFilesystem disk workingDirectory / 'www.squeaksource.com' / 'Kozen'. files := f glob: [ :each| each basename endsWith: '.mcz']. files do: [ :file ||entity stream| stream := file readStream. (entity := ZnStreamingEntity type: ZnMimeType applicationOctetStream) stream: stream; contentLength: stream size. Transcript show: file; cr. "upload the version to gemstone" ZnClient new systemPolicy; beOneShot; signalProgress: true; ifFail: [ :exception | Transcript show: file basename; show: ' '; print: exception ]; username: 'sd' password: 'sn00py_'; entity: entity; url: ( 'http://ss3.gemstone.com/ss/Kozen/', file basename); put ] displayingProgress: 'Uploading mcz' apparently FSReadStream does not know isBinary streamFrom: inputStream to: outputStream size: totalSize | bufferSize buffer leftToRead | bufferSize := 4096 min: totalSize. buffer := (inputStream isBinary ifTrue: [ ByteArray ] ifFalse: [ String ]) new: bufferSize. ^^^^^^^^^^ leftToRead := totalSize. [ leftToRead > 0 ] whileTrue: [ | readCount | readCount := bufferSize min: leftToRead. inputStream next: readCount into: buffer. leftToRead := leftToRead - readCount. outputStream next: readCount putAll: buffer startingAt: 1 ]

Feb. 20, 2012

Re: [Pharo-project] Nautilus Refactorings

by Benjamin

Ok, it's the first time I click on this button :) Let's fix that ;) Thanks again, Ben On Feb 20, 2012, at 4:40 PM, Sven Van Caekenberghe wrote: > > On 20 Feb 2012, at 16:01, Benjamin wrote: > >>> Also, the window about menu displays the class comment of NautilusUI, maybe you can make it a bit more sexy. >> >> I do not get it, sorry > > OK ;-) > > <Screen Shot 2012-02-20 at 16.31.00.png> > > > Now gives: > > <Screen Shot 2012-02-20 at 16.31.22.png> > > > While it should be more like: > > <Screen Shot 2012-02-20 at 16.38.08.png> > > ;-) >

Feb. 20, 2012