May 2014 - Pharo-dev - lists.pharo.org

GetText deleting Pharo classes

by Usman Bhatti

Hi, When GetText package (http://smalltalkhub.com/#!/~PharoExtras/Gettext) is loaded in Pharo, it overwrites two Pharo classes with its own in System-Localization package: LocalID and NaturalLangaugeTranslator. Although so far I haven't seen any bugs in GetText because of this anomaly, one of the side-effects is that we get a dirty package in Monticello browser. Does anyone who is knowledge about the history of two packages know the reason to create classes with identical names? A solution would be to rename these classes in one of the packages. I have know a bit about the internals of GetText so I would be biased towards renaming its but I would need your suggestions/confirmation on how to proceed/which one to modify. tx. usman

May 19, 2014

Re: [Pharo-dev] Gmail Contact Export and #readStream

by Henrik Johansen

On 17 May 2014, at 12:18 , Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > I wonder... can all this be handled automatically? > When I open either file > in OS X, it seems to just "do the right thingÂ». Sorta, though not 100% reliably. The problem is, if the automatic handling decides wrong, you end up with garbage content, rather than a nice, clean error. (Say, a file gets interpreted as ISO-8859-1 when itâs really ISO-8859-15) You *could* automatically detect BOM-marked files with no errors, but the frequency of such files compared to that of single-byte encoded files, or non-BOMâd UTF is rather low, so the payoff is rather small for the extra effort it takes trying to detect encoding for every stream opened. Which is why the standard choice fell on something that will signal an error if itâs the wrong choice, which means having to make an explicit decision which is the correct one on a case-by-case basis, as you experienced. > I also wonder why gmail > doesn't clearly display the encoding when you're exportingâ¦ Yeah, itâd be nice if they were at least as usable as Notepadâs -> Save asâ¦ dialogue, huh? :) (Though, for some reason this seems hard to do in a usable yet flawless manner, that one allows you to select ASCII as encoding, and still save âÃ¦Ã¸Ã¥â without an errorâ¦) Cheers, Henry

May 19, 2014

Re: [Pharo-dev] Call for co-coders

by phil＠highoctane.be

SystemLogger interests me as well. Phil On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Hi Stef, > > Iâm definitely in for the SystemLogger. But as I am involved in it anyway > a fresh look from another person on that stuff could be benefitial. > > Norbert > > Am 19.05.2014 um 09:10 schrieb stepharo <stepharo(a)free.fr>: > > > Hi guys > > > > This is a call for some of you that committed code and would like to do > it with me :). > > I have some projects that I would like to push further in 4.0 and I'm > thinking that > > he could be much more fun to do it with other people. > > > > Here are some topics > > - integrating the systemLogger > > - integrating/improving the new method categorizer > > - cleaning fonts > > - ... > > > > How this could work? > > We could have > > - some discussions > > - make a little roadmap > > - then we could work on the same slice and do code review > > > > I think that it can be fun and motivating. So let me know because I > would like to have more social > > coding. > > > > Stef > > > > >

May 19, 2014

Re: [Pharo-dev] Call for co-coders

by Norbert Hartl

Hi Stef, Iâm definitely in for the SystemLogger. But as I am involved in it anyway a fresh look from another person on that stuff could be benefitial. Norbert Am 19.05.2014 um 09:10 schrieb stepharo <stepharo(a)free.fr>: > Hi guys > > This is a call for some of you that committed code and would like to do it with me :). > I have some projects that I would like to push further in 4.0 and I'm thinking that > he could be much more fun to do it with other people. > > Here are some topics > - integrating the systemLogger > - integrating/improving the new method categorizer > - cleaning fonts > - ... > > How this could work? > We could have > - some discussions > - make a little roadmap > - then we could work on the same slice and do code review > > I think that it can be fun and motivating. So let me know because I would like to have more social > coding. > > Stef >

May 19, 2014

Re: [Pharo-dev] Smalltalkhub project modification error

by Attila Magyar

Never mind, it is working now. -- View this message in context: http://forum.world.st/Smalltalkhub-project-modification-error-tp4759423p475… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 19, 2014

Call for co-coders

by stepharo

Hi guys This is a call for some of you that committed code and would like to do it with me :). I have some projects that I would like to push further in 4.0 and I'm thinking that he could be much more fun to do it with other people. Here are some topics - integrating the systemLogger - integrating/improving the new method categorizer - cleaning fonts - ... How this could work? We could have - some discussions - make a little roadmap - then we could work on the same slice and do code review I think that it can be fun and motivating. So let me know because I would like to have more social coding. Stef

May 19, 2014

Re: [Pharo-dev] WhatsUp from: 2014-05-19 until: 2014-05-31

by stepharo

> Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > > ### What's next, until 2014-05-31 (*) > - continue to work on laser book tutorial - continue to analyze font mess. - sync for 40

May 19, 2014

WhatsUp from: 2014-05-19 until: 2014-05-31

by seaside＠rmod.lille.inria.fr

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2014-05-31 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

May 19, 2014

Re: [Pharo-dev] a Pharo talk from a ruby conference

by Sebastian Sastre

that article lost me when it wrote then instead of than sebastian o/ > On 18/05/2014, at 17:09, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > > Just to add some fuel to this fire... this is a quote from the summary > of the latest LightTable's blog post <http://goo.gl/fTYpJX>: > > "a smooth interface to the old world so we don't end up sharing a > grave with smalltalk" > > I agree with many things in the post. But they're taking credit for > old ideas disguised as the latest innovation. > > > Regards, > > > Esteban A. Maringolo > > > 2014-05-17 8:13 GMT-03:00 kilon alios <kilon.alios(a)gmail.com>: >> I don't get why C is not old / deprecated / obsolete . Afterall its as old >> as Smalltalk >> >> Who really uses modern languages ? >> >> C - 1972 >> >> Python - 1991 >> >> C++ - 1983 >> >> Pascal - 1970 >> >> .NET - 2002 >> >> Lisp - 1958 >> >> Java - 1995 >> >> Ruby - 1995 >> >> Perl - 1987 >> >> Visual Basic - 1991 >> >> Javascript - 1995 >> >> Objective C- 1983 >> >> PHP - 1995 >> >> >> The vast majority of all popular languages out there are at least 20 years >> old. Thats ancient history. They are not old, they are dinosaurs. Even >> Clojure is 7 years old. >> >> The problem I see here is that the vast majority of things people are going >> to like in Pharo on a basic level are Smalltalk features. Implementation >> wise Pharo has improved a lot of things, added new stuff etc etc. But if you >> take a look at for example Python back in 1991 and you compare it with a >> recent version of Python you will find tons of diffirences. Yet its still >> Python. >> >> Actually its impossible to run a hello world of an old python (anything >> previous to version 3) that will run in the recent Python. Cause they >> changed print "hello World" to print( "hello World") , we are talking here >> about fundamental changes. >> >> Personally I don't see how Pharo being 100% Smalltalk makes it unable or >> difficult to implement super modern and efficient new features. Languages >> and Software is not written in stone, it continuously evolves and improves >> or else people stop using it. Vim was created back in 1991 people still find >> awesome, modern, extremely powerful. >> >> this is from Ruby's website -> "Ruby is a language of careful balance. Its >> creator, Yukihiro âMatzâ Matsumoto, blended parts of his favorite languages >> (Perl, Smalltalk, Eiffel, Ada, and Lisp) to form a new language that >> balanced functional programming with imperative programming." Ruby has the >> right to be called Smalltalk-inspired. because thats what it is. >> >> You got every right to describe Pharo any way you like but for me Pharo is >> "a modern implementation of Smalltalk. A visual environment for easy direct >> live coding" . >> >> >> On Sat, May 17, 2014 at 12:30 PM, Hilaire Fernandes >> <hilaire.fernandes(a)gmail.com> wrote: >>> >>> >>> >>> Le 16/05/2014 20:18, phil(a)highoctane.be a Ã©crit : >>>> >>>> Back to the future after 30 years of spinning your wheels >>>> ------------------------------------------------------------------- >>>> >>>> Wanting to code at the speed of tought? >>>> Wishing the machine was your friend and not a roadblock? >>>> Want to burn cash as slow as possible while maximizing your output? >>>> >>>> If so, get a copy of Pharo! It is not your (grand) daddy's Smalltalk! >>> >>> That's why I understand this argument about not advertising Smalltalk in >>> Pharo. >>> >>> Whatever we do or say, this huge mass of followers, once they heard >>> Smalltalk they fill their head with red light warning, Smalltalk = >>> old/deprecated/obsolete. >>> >>> For Pharo willing to socially scale = need to take this in consideration. >>> >>> Hilaire >>> -- >>> Dr. Geo http://drgeo.eu >

May 18, 2014

Re: [Pharo-dev] a Pharo talk from a ruby conference

by Esteban A. Maringolo

Just to add some fuel to this fire... this is a quote from the summary of the latest LightTable's blog post <http://goo.gl/fTYpJX>: "a smooth interface to the old world so we don't end up sharing a grave with smalltalk" I agree with many things in the post. But they're taking credit for old ideas disguised as the latest innovation. Regards, Esteban A. Maringolo 2014-05-17 8:13 GMT-03:00 kilon alios <kilon.alios(a)gmail.com>: > I don't get why C is not old / deprecated / obsolete . Afterall its as old > as Smalltalk > > Who really uses modern languages ? > > C - 1972 > > Python - 1991 > > C++ - 1983 > > Pascal - 1970 > > .NET - 2002 > > Lisp - 1958 > > Java - 1995 > > Ruby - 1995 > > Perl - 1987 > > Visual Basic - 1991 > > Javascript - 1995 > > Objective C- 1983 > > PHP - 1995 > > > The vast majority of all popular languages out there are at least 20 years > old. Thats ancient history. They are not old, they are dinosaurs. Even > Clojure is 7 years old. > > The problem I see here is that the vast majority of things people are going > to like in Pharo on a basic level are Smalltalk features. Implementation > wise Pharo has improved a lot of things, added new stuff etc etc. But if you > take a look at for example Python back in 1991 and you compare it with a > recent version of Python you will find tons of diffirences. Yet its still > Python. > > Actually its impossible to run a hello world of an old python (anything > previous to version 3) that will run in the recent Python. Cause they > changed print "hello World" to print( "hello World") , we are talking here > about fundamental changes. > > Personally I don't see how Pharo being 100% Smalltalk makes it unable or > difficult to implement super modern and efficient new features. Languages > and Software is not written in stone, it continuously evolves and improves > or else people stop using it. Vim was created back in 1991 people still find > awesome, modern, extremely powerful. > > this is from Ruby's website -> "Ruby is a language of careful balance. Its > creator, Yukihiro âMatzâ Matsumoto, blended parts of his favorite languages > (Perl, Smalltalk, Eiffel, Ada, and Lisp) to form a new language that > balanced functional programming with imperative programming." Ruby has the > right to be called Smalltalk-inspired. because thats what it is. > > You got every right to describe Pharo any way you like but for me Pharo is > "a modern implementation of Smalltalk. A visual environment for easy direct > live coding" . > > > On Sat, May 17, 2014 at 12:30 PM, Hilaire Fernandes > <hilaire.fernandes(a)gmail.com> wrote: >> >> >> >> Le 16/05/2014 20:18, phil(a)highoctane.be a Ã©crit : >> > >> > Back to the future after 30 years of spinning your wheels >> > ------------------------------------------------------------------- >> > >> > Wanting to code at the speed of tought? >> > Wishing the machine was your friend and not a roadblock? >> > Want to burn cash as slow as possible while maximizing your output? >> > >> > If so, get a copy of Pharo! It is not your (grand) daddy's Smalltalk! >> >> That's why I understand this argument about not advertising Smalltalk in >> Pharo. >> >> Whatever we do or say, this huge mass of followers, once they heard >> Smalltalk they fill their head with red light warning, Smalltalk = >> old/deprecated/obsolete. >> >> For Pharo willing to socially scale = need to take this in consideration. >> >> Hilaire >> -- >> Dr. Geo http://drgeo.eu >> >> >

May 18, 2014