- Pharo-users - lists.pharo.org

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

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

by Ramon Leon

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. > 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. > Are you interested by a "PharoCasts with experts" ? Ha, no, I'm no expert, just another Smalltalk'er. -- Ramon Leon http://onsmalltalk.com

April 27, 2011

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

by Ted F.A. van Gaalen

Hi Stef I was not really comparing on a language level Smalltalk and Cobol, but more about systems in general. Those legacy systems are around for many years: people have learned the hard way about compatibility, reliability etc. on the other hand, legacy is often a chaotic [some words removed] mess.. I have worked on programs modified over a period of 20 years by 10 or more programmers.. This is also no fun, on the contrary, often a nightmare. I did those ancient languages (Cobol Fortran, and more) for many years and still will do with these procedural languages, because I have to make a living. But don't worry: to me, it sometimes gives the same fun as e.g. a technician who likes working on old steam locomotives in a railway museum :o) The whole environment is however painstakingly difficult (not the language) and needs discipline. I could give you a sightseeing on a mainframe site, but it would make you weep :o) btw. May I introduce myself? look at my CV at : http://tedvg.seasidehosting.st/seaside/TGCVSite (very beta, my first Smalltalk/Seaside app. my picture is a bit formal even wearing a tie:o) I tried in the last 15 years or so to get work with more modern OOP systems e.g. Smalltalk, Java C#. even Delphi. mostly I dindn't succeed. I studied all of this intensively in my free time. I would (if I could) rather have written all these past software in Smalltalk.. Would have saved me a lot of headaches But back then systems were too slow, it was all "too academic" and Smalltalk had just being invented. In those years me, and many others too, had almost no notion of what object technology really is.. Now, today, I see my long existing dreams actually getting fulfilled! I can use Smalltalk because now it works and is fast enough too. I like it very much and hope to get work with it if get more proficient with it. Pharo looks good, is stable and a please to work with. I really hope Pharo / Smalltalk establishes itself, because it is clean, pure, fun and I can concentrate on fast application building instead of many nitty gritty language details. I am still a rookie on Smalltalk steroids, will contribute if I get better with it. Thanks all for all the work. Perhaps it is comforting to know that even people like me, coming from totally different IT fields believe in Smalltalk, maybe it is exactly because we can compare to what we already know. Ted Jikes! too much text. Too much time. I need to get a job soon. On Wed, Apr 27, 2011 at 7:42 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> 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

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

by laurent laffont

Thanks a lot Ramon. I put your answer on PharoCasts. Indeed the SandstoneDb screencast is one of the most seen on PharoCasts. I should update it I think. Maybe you have ideas of what to show ? Are you interested by a "PharoCasts with experts" ? Laurent On Wed, Apr 27, 2011 at 9:52 PM, Ramon Leon <ramon.leon(a)allresnet.com>wrote: > On 04/27/2011 11:43 AM, laurent laffont wrote: > >> Please, could someone check and answer ? >> >> Laurent >> > > It should be working now if you grab the latest version, I updated the > config this morning. The last version got broken because another package > stole the #startUp: method with an override in SandstoneDb causing me to > publish a version without it; it'd cause the symptoms he's describing. > > -- > Ramon Leon > http://onsmalltalk.com > >

April 27, 2011

Re: [Pharo-users] Backward compatibility [WAS] Re: [ANN] PharoDev-1.3-13173

by Sven Van Caekenberghe

On 27 Apr 2011, at 19:19, StÃ©phane Ducasse wrote: >> It's the trade-off between *having a future* or *having the past*. > > ***excellent** we should twitter this one!!! >> "Doing nothing is not an option". > > Another excellent quote to twitter. You are in good form today. > > Stef Indeed, very cool quotes! Put them on the home page or at least somewhere on the website. Sven

April 27, 2011

Re: [Pharo-users] Backward compatibility [WAS] Re: [ANN] PharoDev-1.3-13173

by Marcus Denker

On Apr 27, 2011, at 10:00 PM, StÃ©phane Ducasse wrote: >> It's the trade-off between *having a future* or *having the past*. > > ***excellent** we should twitter this one!!! > > >> >> "Doing nothing is not an option". > > Another excellent quote to twitter. You are in good form today. > I am on holidays ;-) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 27, 2011