In Smalltalk you define points with '@' so you could do... drawRectOrigin: 50@50 extent: 10@21. drawRectOrigin: 50@50 corner: 60@71. If you really wanted, on class Point you could define method ',' with parameter…
Further down some asked "is anything from the Smalltalk OO model that hadn't made its way into Ruby?" Well I don't know about OO model, but to extend my example above, at step 5 when the debugger appears, <Save & Quit>…
Slides 85-95. http://www.pharo-project.org/about/success-stories
The second Gofer is not needed. The XML Support is all installed with the #load message. I don't think you can live-patch a DoIt from Workspace. What you can try is create a test class and method. However you can demo…
I started using Pharo a year ago and its been a pleasure to work with. Great community. I really like the Syntax comparison (slides 46-49). And being able to serialize the debugging context of a running program to a…
In Smalltalk you define points with '@' so you could do... drawRectOrigin: 50@50 extent: 10@21. drawRectOrigin: 50@50 corner: 60@71. If you really wanted, on class Point you could define method ',' with parameter…
Further down some asked "is anything from the Smalltalk OO model that hadn't made its way into Ruby?" Well I don't know about OO model, but to extend my example above, at step 5 when the debugger appears, <Save & Quit>…
Slides 85-95. http://www.pharo-project.org/about/success-stories
The second Gofer is not needed. The XML Support is all installed with the #load message. I don't think you can live-patch a DoIt from Workspace. What you can try is create a test class and method. However you can demo…
I started using Pharo a year ago and its been a pleasure to work with. Great community. I really like the Syntax comparison (slides 46-49). And being able to serialize the debugging context of a running program to a…