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

Re: [Pharo-dev] Soon the LaserGame book for Pharo

by Ben Coman

Hi Steph, That is really great news. I _often_ direct people to the LaserGame tutorial even though its a bit awkward asking them to use an image seven years old (Squeak 3.9). A while ago I asked Steve for permission to update it for Pharo, but was discouraged to get no response at all. Perhaps my mail never made it through. I am interested in helping out, either directly with the conversion or as reviewer. Let me know. cheers -ben stepharo wrote: > Hi guys > > Steve just told me that he is ok that we port his book to Pharo :) > This is a great news. So I will start during my spare time. > > Stef > > Begin forwarded message: > > From: Stephan Wessels <stevewessels(a)me.com> > Subject: Re: [vwnc] Can this idea work > Date: 24 Apr 2014 15:21:27 GMT+2 > To: stephane ducasse <stephane.ducasse(a)gmail.com> > > Hi. Actually I got those requests and replied both times that you > have my permission provided I'm credited or noted as the original > author. Please go forward with it; it can only help the Smalltalk > community. > > Sent from my iPhone > > On Apr 24, 2014, at 8:16 AM, stephane ducasse > <stephane.ducasse(a)gmail.com> wrote: > > Hi steve > > I tried to contact you several times in the past but I got no answer. > I would like to know if we can port the tutorial to Pharo and if we > can turn it into a book to fit in the > open-source book collection we are slowly building (SqueakbyExample, > PharoByExample, Seaside, DeepintoPharo). > Now since there is no license it is not clear that it is worth the > effort. > > Stef > > On 22 Apr 2014, at 01:44, stevewessels <stevewessels(a)me.com> wrote: > > As the author of the tutorial I'm not sure how I feel about my work being > referred to as "old". > > The tutorial is remarkably still in use to this day. I still get emails > from folks thanking me for it or reporting bugs. > > When the tutorial was written my intended audience was Smalltalk > developers > wanting to build Test Driven Development (TDD) skills. It was not > intended > for beginners. But as it turns out lots of beginners have slogged > through > it. The key concepts I tried to demonstrate were how to do TDD and > building > good models that were testable. I also wanted to show you could make > stand-alone apps using Smalltalk/Squeak for the Mac. > > To convert the tutorial to VisualWorks might end up being a challenge, > but > alas, I haven't used VW since the late 90's and I know it's grown a whole > lot since those days. So I cannot recommend how you go about doing it. > > You're welcome to send me questions about it and any design decisions > that > were made. I don't claim that it is a "proper OO design" or anything > like > that. Interestingly, I did port the design to Objective-C for the iPhone > years ago and the basic design held up fine. The GUI was obviously done > differently -- I ended up adopting OpenGL for the GUI. That was > work. But > it turned out well and has been in the App Store ever since. > > So if I can help you, drop me a note. > > > > -- > View this message in context: > http://forum.world.st/Can-this-idea-work-tp4753741p4755668.html > Sent from the VisualWorks mailing list archive at Nabble.com. > _______________________________________________ > vwnc mailing list > vwnc(a)cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > >

May 1, 2014

Re: [Pharo-dev] New Proposal for new Pharo website - About page (with example website)

by Eliot Miranda

Hi Kilon, On Thu, May 1, 2014 at 8:01 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > I have further refined the About page but not I have also created > additional pages for "language" and "ide" > you can click on the main page on those words because they are links to > send to you to the corresponding page or you can access these pages from > here > > "The Language" > > http://thekilon.wix.com/pharo-about#!language/cee5 > This is really good. My criticism is that "invented in 1969" implies it hasn't changed that much since then. It has, and one of the biggest changes was from Smalltalk-72 to Smalltalk-76. You might instead say something like "conceived in 1969, and stabilizing as Smalltalk-80 in the 1980's". One of the things I missed on first visit was the "fast moving forward" section. I suggest you eliminate it and put the information in the first section. But there are significant language developments since then: - traits - namespaces - closures - ByteArray literals - method pragmas/method tags and more to come: - slots I would replace the third section with something on the class library, that it is large (numbers, collections, graphics, multi-media, etc, the more the better) and mature. > > "The IDE" > > http://thekilon.wix.com/pharo-about#!ide/cfvg > You don't say anything about the debugger. The debugger is of course excellent and one of the few that allows programming in the debugger. That deserves a sentence or two surely. > > > > Again these are drafts WIP , with many mistake and still with room for a > lot of improvement. > > The good news is that I tried the website on my mobile phone and it seems > it works well for mobile devices too > > > On Thu, May 1, 2014 at 12:36 PM, kilon alios <kilon.alios(a)gmail.com>wrote: > >> I don't like the about page. Its still unclear what Pharo is and I have >> to agree with the complains we are getting at reddit. >> >> So instead of starting a long conversation about how I would want it done >> , I sat my ass down and made a draft of it so you can see it directly. >> >> Please bare in mind this is draft , I just wanted to show you my idea for >> an About page. You can find the draft here >> >> http://thekilon.wix.com/pharo-about >> >> I think contributors should go to a seperate page called "Credit" >> >> I am open to comments and suggestions. >> > > -- best, Eliot

May 1, 2014

Re: [Pharo-dev] Usage of should: in tests

by stepharo

Hi nicolas just because people do not know. I'm going over the tutorial of Steven Wessels and converting all the should: by assert: too. So I would just change everything and commit. Stef On 1/5/14 00:52, Nicolas Cellier wrote: > Hi, > I see many usage of #should: in SciSmalltalk tests that could simply > be turned into #assert: or eventually #assert:equals: > Why wanting to use a block? > Other than #should:raise: and #shouldnt:raise:, I don't really see the > point of #should: alone anyway... > IMO should: should be deprecated, less is more. > I'm possibly the author of several of these #should: sends, so don't > take it personnally ;) > > P.S. or is it easier to restart the block in the Debugger? > I cross post to pharo-dev because it's a generic question, and there > are a few #should: sends in Pharo-3.0 too.

May 1, 2014

Re: [Pharo-dev] Pharo renamed to "MuchTalk"

by stepharo

> Holy smoley! > > 117 emails since I checked a few hours ago? Maybe we should rename Pharo âProlixâ? > > :-) Hi oscar Would match well with axterix :) Stef > > on > > >

May 1, 2014

Re: [Pharo-dev] Pharo 3.0 Released!

by stepharo

Hi eliot > Thanks you all. I love this page > > http://www.pharo.org/about > especially the contributors list :) > > > Indeed. But > "Pharo's goal is to deliver a clean, innovative, free open-source > environment." > is an environment for what? Not merely development, for deployment > too, for a dynamic language? > > Why not "Pharo's goal is to deliver a clean, innovative, free > open-source dynamic application development platform."? Indeed. I was on vacation when all the bus rmoders were pushing the web/release/.... and my network was so slow that I could not even get the log button on the web-site :). Stef

May 1, 2014

Re: [Pharo-dev] Pharo 3.0 Released!

by Mariano Martinez Peck

Thank you so much guys. I am already using it :) Loving it already. On Thu, May 1, 2014 at 1:03 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > Hi StÃ©ph, > > > On Thu, May 1, 2014 at 1:35 AM, stepharo <stepharo(a)free.fr> wrote: > >> Thanks you all. I love this page >> >> http://www.pharo.org/about >> especially the contributors list :) >> > > Indeed. But > "Pharo's goal is to deliver a clean, innovative, free open-source > environment." > is an environment for what? Not merely development, for deployment too, > for a dynamic language? > > Why not "Pharo's goal is to deliver a clean, innovative, free open-source > dynamic application development platform."? > > > -- > best, > Eliot > -- Mariano http://marianopeck.wordpress.com

May 1, 2014

Re: [Pharo-dev] Pharo 3.0 Released!

by Eliot Miranda

Hi StÃ©ph, On Thu, May 1, 2014 at 1:35 AM, stepharo <stepharo(a)free.fr> wrote: > Thanks you all. I love this page > > http://www.pharo.org/about > especially the contributors list :) > Indeed. But "Pharo's goal is to deliver a clean, innovative, free open-source environment." is an environment for what? Not merely development, for deployment too, for a dynamic language? Why not "Pharo's goal is to deliver a clean, innovative, free open-source dynamic application development platform."? -- best, Eliot

May 1, 2014

Re: [Pharo-dev] New Proposal for new Pharo website - About page (with example website)

by kilon alios

I have further refined the About page but not I have also created additional pages for "language" and "ide" you can click on the main page on those words because they are links to send to you to the corresponding page or you can access these pages from here "The Language" http://thekilon.wix.com/pharo-about#!language/cee5 "The IDE" http://thekilon.wix.com/pharo-about#!ide/cfvg Again these are drafts WIP , with many mistake and still with room for a lot of improvement. The good news is that I tried the website on my mobile phone and it seems it works well for mobile devices too On Thu, May 1, 2014 at 12:36 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > I don't like the about page. Its still unclear what Pharo is and I have to > agree with the complains we are getting at reddit. > > So instead of starting a long conversation about how I would want it done > , I sat my ass down and made a draft of it so you can see it directly. > > Please bare in mind this is draft , I just wanted to show you my idea for > an About page. You can find the draft here > > http://thekilon.wix.com/pharo-about > > I think contributors should go to a seperate page called "Credit" > > I am open to comments and suggestions. >

May 1, 2014

Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available

by Clara Allende

Ahora si! Esteban, my sight thanks you (having astigmatism is not cool). Really, this made my day as well :) On 1 May 2014 10:17, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: > Awesome! > > Thanks. > > > On 05/01/2014 06:24 AM, Esteban Lorenzano wrote: > > Dark Theme for Pharo 3 > ================== > > So, I finally took some time and hacked a Dark Theme for Pharo 3: > > > How you install it? You need to execute this script: > > â1. You need this because otherwise Gofer merge becomes dumb :P" > MCRepositoryGroup default > addRepository: (MCSmalltalkhubRepository > owner: 'estebanlm' > project: 'Pharo3DarkTheme'). > â2. Now we can actually MERGE the project" > Gofer it > smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > package: 'Pharo3DarkTheme'; > merge. > â3. And then install it" > Pharo3DarkTheme installFullTheme. > > > *WARNING 1:* You need to do a merge (notice the script) > *WARNING 2:* Yes, this is a HACK (also: an ugly hack). See below for > details. > *WARNING 3:* This changes something in the Pharo3Theme too... so you can > go back after installing, but not completely :) > > Considerations > -------------- > > It can look like an easy task, to make a theme over a non native GUI > like Pharo, but let me tell you: It is not. There are a lot of glitches and > errors of design you have to overcome to get a working version of a theme. > This is a pitty because we claim that our system is clean (or should be > clean) and easy to understand. > > But all the Morphic implementation is a hack over a hack, with > preconcepts and hardcodes everywhere, up to a point that to make the > smallest change is an incredibly annoying task. > > Then... I added ""yet another hack"" to this infinite list. I made it > because we need something like this, even if not a good solution. And I > also made it to start a debate into our community. I truly believe that > Morphic was a great idea, but I also believe that current implementation is > doomed. I would like to discuss a new implementation, with a good design > (for example I believe it should be a clear separation between a morph and > it's skin, making easy the actual-hard task of changing a colorset). > I also believe there will be a clear separation between what is a Morph (a > graphical unit) and a Widget (who at the time should use morphs, but that's > another story). > Etc., etc., etc. > > So, will we start the longtime postponed effort of effectively replace > current Morphic? > > In the mean time, enjoy the theme. Is so cool that I'm considering > making it my default theme :P > > Esteban > > >

May 1, 2014

Sound input does not work

by jannik laval

Hello Pharoers, I am trying to play with sound in Pharo v3.0, and the sound input does not work. I tried: SpectrumAnalyzerMorph new openInWorld Cheers, -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://car.mines-douai.fr/

May 1, 2014