April 2011 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] PharoDev-1.3-13173

by StÃ©phane Ducasse

On Apr 27, 2011, at 11:41 PM, Jon Hancock wrote: > Stef, > I'm with you!! Keep hacking away at Pharo and make it the cleanest, nicest Smalltalk environment. Backwards compat talk this early in Pharo's life is premature. Besides, one of Smalltalk's best features is discovery and refactoring. This makes it much easier to migrate and rewrite when things break. > > Thanks for all your work!! I'm only "playing" with pharo these days but keep looking for U.S. clients where I can plug it in. Excellent I cross my finger. Stef > ~Jon > > On 04/27/2011 01:42 PM, StÃ©phane Ducasse wrote: >> Mike and other >> >> How many engineers are payed to deliver freeBSD? >> How many active committers and packages responsible are actively commiting and taking >> responsibility for packages? >> >> We need also stability but right now not changing is just been dead. >> I think that lot of people do not read the code of pharo else they would see why we are >> changing. We do not change for the fun. THIS IS NOT FUN TO write boring code >> to fix ugly situation. We would prefer to write hyper cool sexy app and be fancy to >> impress girls but this is not like that. Network is bad, compiler is bad, file is ugly.... >> Once this will be fixed then we will not change for the sake of it. >> >> Now comparing Smalltalk to cobol is silly (sorry but it is). Right we are fighting >> with python, ruby, javascript (in fact we are not fighting since we do not even exist in the radar). >> If we want to get a chance, we should move way faster and be really aggressive to make sure >> that you can write hyper cool application. >> >> Now why would you need to upgrade all the time to new versions if your system >> is working. >> >> Metacello and versioning systems are your friends: maintain difference streams >> and versions if you want to share between different versions. >> >> Stef > >

April 28, 2011

Re: [Pharo-users] Fwd: [Pharocasts] New comment on SandstoneDb, simple ActiveRecord style persistence....

by Davorin Rusevljan

On Thu, Apr 28, 2011 at 8:24 AM, laurent laffont <laurent.laffont(a)gmail.com> wrote: >> Are you interested by a "PharoCasts with experts" ? > >> Ha, no, I'm no expert, just another Smalltalk'er. > > Hey ! Are you not the one who knows the mostÂ SandstoneDb ? I am interested to see PharoCasts with experts featuring Ramon and SandstoneDb :) Davorin Rusevljan http://www.cloud208.com/

April 28, 2011

Re: [Pharo-users] Fwd: [Pharocasts] New comment on SandstoneDb, simple ActiveRecord style persistence....

by laurent laffont

On Wed, Apr 27, 2011 at 11:35 PM, Ramon Leon <ramon.leon(a)allresnet.com>wrote: > On 04/27/2011 01:19 PM, laurent laffont wrote: > >> Thanks a lot Ramon. I put your answer on PharoCasts. >> > > No prob. > > > Indeed the SandstoneDb screencast is one of the most seen on PharoCasts. >> > > Heh, that's surprising. May be because it looks easy (it is) and that ActiveRecord is a known pattern. I should update it I think. Maybe you have ideas of what to show ? > I'd probably move the content of comment showing how to load it with the > Metacello config up into the post itself since that should be the easiest > and preferred way to load it. I have been and will continue to keep it up > to date with released versions. > > OK Are you interested by a "PharoCasts with experts" ? > Ha, no, I'm no expert, just another Smalltalk'er. Hey ! Are you not the one who knows the most SandstoneDb ? Laurent. > > > -- > Ramon Leon > http://onsmalltalk.com > >

April 28, 2011

Re: [Pharo-users] Problem dealing with UTF8 characters in pathnames

by StÃ©phane Ducasse

enter a bug entry. stef On Apr 28, 2011, at 12:29 AM, Casimiro de Almeida Barreto wrote: > In FilePath an error is raised when UTF-8 is found in pathname. > > FilePath>>pathName: isEncoded: > ByteString>>convertFromWithConverter: > UTF8TextConverter>>nextFromStream: > > Best regards, > > Casimiro >

April 28, 2011

Re: [Pharo-users] [ANN] PharoDev-1.3-13173

by laurent laffont

+1000 for the future. Backward bug and bad design compatibility is a pain. Laurent On Wed, Apr 27, 2011 at 11:59 PM, Casimiro de Almeida Barreto < casimiro.barreto(a)gmail.com> wrote: > Em 27-04-2011 18:41, Jon Hancock escreveu: > > Stef, > > I'm with you!! Keep hacking away at Pharo and make it the cleanest, > > nicest Smalltalk environment. Backwards compat talk this early in > > Pharo's life is premature. Besides, one of Smalltalk's best features > > is discovery and refactoring. This makes it much easier to migrate > > and rewrite when things break. > > > > Thanks for all your work!! I'm only "playing" with pharo these days > > but keep looking for U.S. clients where I can plug it in. > > ~Jon > +1 here. > > Backwards compatibility would make sense only if there were widespread > use applications. Except for seaside I cannot mention (I'm not being > rude, neither willing to hurt feelings) other pharo/squeak artifact > that's used in a scale enough to demand back compat. Small scale > applications or stand alone solutions don't require updates/upgrades. > > I agree with Stef & others: the important thing at the moment is having > a platform. Pharo isn't it yet. At current pace it will be soon. When it > happens and people see the value to deliver mass solutions, then a > requirement for back compat will appear. > > It's interesting but many complaints about compatibility are done > regarding to packages that aren't even maintained anymore. And that > happens in part because of platform deficiencies pointed by Stef. > > My 0,99c here... > > CdAB > >

April 28, 2011

PluggableTextMorph>>appendText:aTextOrString

by DougEdmunds

Is there a limit to the amount of text (size of the string) that can be accumulated in PluggableTextMorph>>appendText:aTextOrString ? If so, what's the limit? If so, how do you test the size? Does the performance of 'appendText:' degrade as the string lengthens? -- View this message in context: http://forum.world.st/PluggableTextMorph-appendText-aTextOrString-tp3479980… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 28, 2011

Problem dealing with UTF8 characters in pathnames

by Casimiro de Almeida Barreto

In FilePath an error is raised when UTF-8 is found in pathname. FilePath>>pathName: isEncoded: ByteString>>convertFromWithConverter: UTF8TextConverter>>nextFromStream: Best regards, Casimiro

April 27, 2011

Re: [Pharo-users] [ANN] PharoDev-1.3-13173

by Casimiro de Almeida Barreto

I've noticed a funny behavior of Transcript. Sometimes it is loosing it's "window" attributes (borders, etc). Sometimes it's "waking by itself" (meaning, it's minimized & when something is output to it it appears on World but without borders, etc). I'll investigate more & inform. CdAB

April 27, 2011

Re: [Pharo-users] [ANN] PharoDev-1.3-13173

by Casimiro de Almeida Barreto

Em 27-04-2011 18:41, Jon Hancock escreveu: > Stef, > I'm with you!! Keep hacking away at Pharo and make it the cleanest, > nicest Smalltalk environment. Backwards compat talk this early in > Pharo's life is premature. Besides, one of Smalltalk's best features > is discovery and refactoring. This makes it much easier to migrate > and rewrite when things break. > > Thanks for all your work!! I'm only "playing" with pharo these days > but keep looking for U.S. clients where I can plug it in. > ~Jon +1 here. Backwards compatibility would make sense only if there were widespread use applications. Except for seaside I cannot mention (I'm not being rude, neither willing to hurt feelings) other pharo/squeak artifact that's used in a scale enough to demand back compat. Small scale applications or stand alone solutions don't require updates/upgrades. I agree with Stef & others: the important thing at the moment is having a platform. Pharo isn't it yet. At current pace it will be soon. When it happens and people see the value to deliver mass solutions, then a requirement for back compat will appear. It's interesting but many complaints about compatibility are done regarding to packages that aren't even maintained anymore. And that happens in part because of platform deficiencies pointed by Stef. My 0,99c here... CdAB

April 27, 2011

Re: [Pharo-users] [ANN] PharoDev-1.3-13173

by Jon Hancock

Stef, I'm with you!! Keep hacking away at Pharo and make it the cleanest, nicest Smalltalk environment. Backwards compat talk this early in Pharo's life is premature. Besides, one of Smalltalk's best features is discovery and refactoring. This makes it much easier to migrate and rewrite when things break. Thanks for all your work!! I'm only "playing" with pharo these days but keep looking for U.S. clients where I can plug it in. ~Jon On 04/27/2011 01:42 PM, StÃ©phane Ducasse wrote: > Mike and other > > How many engineers are payed to deliver freeBSD? > How many active committers and packages responsible are actively commiting and taking > responsibility for packages? > > We need also stability but right now not changing is just been dead. > I think that lot of people do not read the code of pharo else they would see why we are > changing. We do not change for the fun. THIS IS NOT FUN TO write boring code > to fix ugly situation. We would prefer to write hyper cool sexy app and be fancy to > impress girls but this is not like that. Network is bad, compiler is bad, file is ugly.... > Once this will be fixed then we will not change for the sake of it. > > Now comparing Smalltalk to cobol is silly (sorry but it is). Right we are fighting > with python, ruby, javascript (in fact we are not fighting since we do not even exist in the radar). > If we want to get a chance, we should move way faster and be really aggressive to make sure > that you can write hyper cool application. > > Now why would you need to upgrade all the time to new versions if your system > is working. > > Metacello and versioning systems are your friends: maintain difference streams > and versions if you want to share between different versions. > > Stef

April 27, 2011