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

Re: [Pharo-dev] One complaint about Pharo

by stepharo

yes you are right too. Because I'm realy efficient with my messy single window desktop :) Stef On 15/5/14 23:18, Esteban Lorenzano wrote: > yesâ¦ we have a version of mars that more or less works. > Never announced because there is a lot of other âsmall detailsâ to fix, but someone could actually do a desktop app with it. > Nowâ¦ there is a difference between making a desktop app and developing with pharo. For desktop apps is most probably that you will want multi windows (even if regularly *you do not use them*, as experience shows: most apps are a single window + dialogs [1][2][3]. Anyway, even if experience says the opposite, you will want many windows). Now, the way pharo is conceived will never work in a multiwindow environment. Just imaging your 10-15 browsers + 5-6 workspaces opened alog with all your other windows (browsers, mails, text editors. terminals, games, whatever). > That just cannot work. I have seen this before. People is so used to have it that they *believe* they need it. Just to realise that pharo workflow has nothing to do with a (for example) java workflow. > > but yesâ¦ we need to support multiwindows. Not for pharo IDE, but for pharo desktop apps. > > cheers, > Esteban > > [1] http://upload.wikimedia.org/wikipedia/commons/f/f2/Giancarlo_Mora_Blender_J… > [2] http://theopensourcery.com/images/javajspEclipse.gif > [3] http://microsoft-news.com/wp-content/uploads/2013/10/Outlook-Mail-App-Windo… > > > On 15 May 2014, at 22:05, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> 2014-05-15 16:57 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> >>> That single screen has its advantages. It's a very cosy place to be :-) >> +1 >> >> Plus... unless we got independent process/queues per window (like >> Smalltalk/X [1]) I don't see the advantage from the development >> standpoint. >> >> >> Regards, >> >> >> [1] In St/X you can kill a window without killing the whole image. >> Pretty useful if you mess up something :) >> > >

May 18, 2014

Re: [Pharo-dev] Meteor inspiration naive ideas (was Pharo talk from a ruby conference)

by CÃ©drick BÃ©ler

> one or two things you mention could be addressed by http://sebastianconcept.github.io/Mapless Cool stuff, will look at soon :-) > > redis might address horizontal scaling even better than meteor > > and you forgot to add the feature detecting mongo changes so reactivity is possible (btw you > probably know but meteor is aiming to support more than mongo also famo.us but that's another story) I'm following famo.us progress and seen some demo coupling meteor and famo.us. Famo.us really is impressive by itself too. Wonder if possible to bridge with Pharo... Anyway, thanks for sharing mapless, I'll give a try ;-) Cheers, Cedrick > > sebastian > > o/ > >> On 17/05/2014, at 10:52, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: >> >> Hi all. Just some raw ideas below. >> >> It several months I haven't coded in pharo. And I really miss it. >> >> Meanwhile I've been lurking in iOS and recently meteor. >> >> I think the latter is great. We might take ideas from it... But it has to be adapted to the smalltalk way. What I find great: >> - reactive data and DDP is great to me >> => we need an equivalent tech. Sure it's a piece of cake for Sven :-) >> => having standard data storage as files/nosql/gemstone working out of the box >> => controled replication of data on client to avoid latency is a very good idea too to me >> - smart package are cool too >> => st and js have already a close relationship, we should enforce and simplify it as with C >> >> One killer app would be to have bridges to meteor BUT I would dream of an inspired version of/for Pharo. >> >> Meteor core language is js + css + mongo + lots of conventions. It's a full stack. Problem of meteor: no live debugging sessions (whereas it seems live!) and whereas it seems damn simple (3 files), it has hundreds of MB hidden for each installed apps ! >> >> I would see mini pharo images (without UI) acting as web client/server interchangabily. A separate data layer (probably an image too) with full access on the server and controlled replication on clients. Then a connection with a classic pharo image to develop/debug the mini images. >> >> Just some cents. I know this is quite naive and not easy to do... But we might take some inspiration: >> -DDP (easy for Sven) :-) >> -grid style client/server easy setup/deployment/control for casual developers >> ... >> >> Cheers, >> >> Cedrick >> >>> Le 17 mai 2014 Ã 13:13, kilon alios <kilon.alios(a)gmail.com> a Ã©crit : >>> >>> 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 17, 2014

Re: [Pharo-dev] Meteor inspiration naive ideas (was Pharo talk from a ruby conference)

by Sebastian Sastre

one or two things you mention could be addressed by http://sebastianconcept.github.io/Mapless redis might address horizontal scaling even better than meteor and you forgot to add the feature detecting mongo changes so reactivity is possible (btw you probably know but meteor is aiming to support more than mongo also famo.us but that's another story) sebastian o/ > On 17/05/2014, at 10:52, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > > Hi all. Just some raw ideas below. > > It several months I haven't coded in pharo. And I really miss it. > > Meanwhile I've been lurking in iOS and recently meteor. > > I think the latter is great. We might take ideas from it... But it has to be adapted to the smalltalk way. What I find great: > - reactive data and DDP is great to me > => we need an equivalent tech. Sure it's a piece of cake for Sven :-) > => having standard data storage as files/nosql/gemstone working out of the box > => controled replication of data on client to avoid latency is a very good idea too to me > - smart package are cool too > => st and js have already a close relationship, we should enforce and simplify it as with C > > One killer app would be to have bridges to meteor BUT I would dream of an inspired version of/for Pharo. > > Meteor core language is js + css + mongo + lots of conventions. It's a full stack. Problem of meteor: no live debugging sessions (whereas it seems live!) and whereas it seems damn simple (3 files), it has hundreds of MB hidden for each installed apps ! > > I would see mini pharo images (without UI) acting as web client/server interchangabily. A separate data layer (probably an image too) with full access on the server and controlled replication on clients. Then a connection with a classic pharo image to develop/debug the mini images. > > Just some cents. I know this is quite naive and not easy to do... But we might take some inspiration: > -DDP (easy for Sven) :-) > -grid style client/server easy setup/deployment/control for casual developers > ... > > Cheers, > > Cedrick > >> Le 17 mai 2014 Ã 13:13, kilon alios <kilon.alios(a)gmail.com> a Ã©crit : >> >> 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 17, 2014

Re: [Pharo-dev] One complaint about Pharo

by stepharo

We fully agree. We will work on - real headless - move to the image the windowing logic (because right now it is encoded in the VM) But this is work. Igor and Ronie did already a good experience and they got it working on Linux. You can play with it and give us feedback. Then we will probably interface with SDL2. On 15/5/14 20:21, David Astels wrote: > One of the big issues I have with Pharo is that Iâm stuck on a single screen, unlike Cincom Smalltalk that uses separate OS windows that I can spread over multiple screens. Iâm assuming this is a hard limit in OSX, but itâs a bit annoying. Yes, Self has the same issue, and itâs just as annoying. > > Dave > > >

May 17, 2014

Meteor inspiration naive ideas (was Pharo talk from a ruby conference)

by CÃ©drick BÃ©ler

Hi all. Just some raw ideas below. It several months I haven't coded in pharo. And I really miss it. Meanwhile I've been lurking in iOS and recently meteor. I think the latter is great. We might take ideas from it... But it has to be adapted to the smalltalk way. What I find great: - reactive data and DDP is great to me => we need an equivalent tech. Sure it's a piece of cake for Sven :-) => having standard data storage as files/nosql/gemstone working out of the box => controled replication of data on client to avoid latency is a very good idea too to me - smart package are cool too => st and js have already a close relationship, we should enforce and simplify it as with C One killer app would be to have bridges to meteor BUT I would dream of an inspired version of/for Pharo. Meteor core language is js + css + mongo + lots of conventions. It's a full stack. Problem of meteor: no live debugging sessions (whereas it seems live!) and whereas it seems damn simple (3 files), it has hundreds of MB hidden for each installed apps ! I would see mini pharo images (without UI) acting as web client/server interchangabily. A separate data layer (probably an image too) with full access on the server and controlled replication on clients. Then a connection with a classic pharo image to develop/debug the mini images. Just some cents. I know this is quite naive and not easy to do... But we might take some inspiration: -DDP (easy for Sven) :-) -grid style client/server easy setup/deployment/control for casual developers ... Cheers, Cedrick > Le 17 mai 2014 Ã 13:13, kilon alios <kilon.alios(a)gmail.com> a Ã©crit : > > 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 17, 2014

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

by kilon alios

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 <http://www.rubyist.net/~matz/>, 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 17, 2014

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

by Andreas Wacknitz

Am 17.05.2014 um 11:30 schrieb Hilaire Fernandes <hilaire.fernandes(a)gmail.com>: > > > 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. You could also argue the other way around: Without being a Smalltalk Pharo is nothing. New languages come and go. Nowadays almost everybody feels competent enough to create his own language. Most of them start enthusiastic and will be abandoned after some time. Sourceforge has so many dead examples. Smalltalk has a tradition we should be proud of. I am not reluctant to tell people about Smalltalk and its advantages (and disadvantages). In my experience there are two three kinds of developers: 1. those who know one or a few languages and are happy with it 2. those who know one or a few languages and permanently seek for a better one that is a direct relative. (Many C# and Java developers are looking for better C#âs and Javaâs. That makes it easy to sell them new versions of it.) 3. those who know some languages and want to learn more; always seeking for a wow-effect; open-minded; know about different paradigms and want to learn about it. The third is the smallest group I guess. You have a hard time to convince anybody from 1 or 2 however you are marketing Pharoâ¦ Andreas

May 17, 2014

Re: [Pharo-dev] Pharo 3.0 / Roassal2 / Ubuntu

by Alexandre Bergel

I have left this email for long. We will work in this next week. But yes, it is possible that some example only works in the moose image Alexandre > Le 05-05-2014 Ã 4:01, Nicolai Hess <nicolaihess(a)web.de> a Ã©crit : > > 2014-05-01 13:07 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: >> > Yes yes yes ... it works. I quickly jumped through some examples. Roassal2 looks so nice. Thank you. >> >> Let me know how it goes. Documentation is missing, but we have many many examplesâ¦ >> The chapter in Deep into Pharo (www.deepintopharo.com) contains a documentation about Roassal1 and the Mondrian builder, written on top of the core of Roassal. >> >> Roassal2 is largely compatible with Roassal1. When it is not, then small changes have to be made. >> >> Alexandre >> >> > >> > >> > >> > Am 01.05.2014 03:31, schrieb Alexandre Bergel: >> >> Hi Volkert, >> >> >> >> You need to install the true type font. Unfortunately, Pharo3 does not do it for you. I guess this will be fixed in the next release of Pharo. >> >> >> >> I have made a very short video on how to install Roassal2 from scratch: >> >> https://dl.dropboxusercontent.com/u/31543901/TMP/InstallingTrueTypeFont.mov >> >> >> >> Let us know how it goes. >> >> >> >> Alexandre >> >> >> >> >> >> On Apr 30, 2014, at 2:53 PM, volkert(a)nivoba.de wrote: >> >> >> >>> Dear all, >> >>> >> >>> i just downloaded Pharo 3.0 and installed Roassal2 via Configuration Manager (Stable Version). >> >>> When trying the "Roassal examples" (from Tool-Menu) i got an red screen. >> >>> >> >>> Platform Ubuntu 14.04LTS >> >>> Pharo3.0 Latest update: #30846 >> >>> >> >>> Need some help :-) >> >>> >> >>> BW, >> >>> Volkert >> >>> >> > >> > >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > Is there a way to provide a stable version of Roassal2 for Pharo without forcing the user > to change the font? > > I tested all examples from Roassal Examples menu. > > 1. > They are great! > > 2. > Not all are working: > RTGraphBuilderExample > exampleTreeMapAndNormalizeColor > exampleColorPalette2 > exampleNormalizeColor > exampleSystemComplexity > exampleConnectFromAndSelectiveColor > exampleColorPalette1 > exampleColorPalette4 > exampleColorPalette3 > > RTMondrianExample > exampleClasses > exampleSystemComplexity > > mostly because of missing "metrics-messages" on (numberOfVariables numberOfLinesOfCode ...) > > 3. > Suggestions/Questions > Is there a common gesture (mousewheel/key shortcut) for scaling the view? > Larger Icons for the "Animated scatter plot" and "Mondrian builder" examples. > > Roassal Examples opens a menu with: > > Animated scatter plot > Graph builder > Geographic .... > > > but after selecing one entry, there is no way to go back. Suggestion: make a "back" button on every > demo page, or open every demo page in its own window. > > > > regards > Nicolai > > >

May 17, 2014

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

by Hilaire Fernandes

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 17, 2014

Re: [Pharo-dev] Pharo 3.0 / Roassal2 / Ubuntu

by Esteban Lorenzano

yeah, but where? looks like a roassal problem, not a pharo one. Redirecting to moose list :) Esteban On 17 May 2014, at 10:24, volkert(a)nivoba.de wrote: > > Am 01.05.2014 13:07, schrieb Alexandre Bergel: >>> Yes yes yes ... it works. I quickly jumped through some examples. Roassal2 looks so nice. Thank you. >> Let me know how it goes. Documentation is missing, but we have many many examplesâ¦ >> The chapter in Deep into Pharo (www.deepintopharo.com) contains a documentation about Roassal1 and the Mondrian builder, written on top of the core of Roassal. >> >> Roassal2 is largely compatible with Roassal1. When it is not, then small changes have to be made. >> >> Alexandre >> > today i started with a fresh pharo 3.0 image (#30848) und loaded roassal2 (following the video tutorial). But when > selecting the example and evalution menu i got a "MessageNotUnderstood: ByteString>>replaceAllRegex:with:". > Something is broken here. > > BW, > Volkert >

May 17, 2014