March 2013 - Pharo-users - lists.pharo.org

Why are SmallTalk projects/source code hosted on SS3 Gemstone instead of Git?

by Victor Stan

Why are SmallTalk projects/source code hosted on SS3 Gemstone instead of Git/GitHub? I'm coming to SmallTalk from the world of web development with open source software, primarily Rails, and I'm very familiar with the amazing social network/source code repository that is GitHub. It is truly an industry defining entity, so many open source projects have been able to harness the ease of use, features and community around Git and GitHub. At the moment, as I'm trying to learn more about SmallTalk and Pharo especially, (my primary interest in Pharo is to use it as a web development platform), I am a bit shocked, if I may be frank, at the tooling used for source code and open source project management. I see that the popular trend now is to move to SS3/Gemstone, and I appreciate anyone that helps open source development/projects, but I can't see how they can even come close to the functionality of GitHub for source code hosting and OS project management, so I pose the question: is there an effort, why or why not, to start integrating with GitHub and Git for source code management? I know that historical precent and the tools built into Pharo/SmallTalk images, like Monticello are predecessors to GUI source control, but given the leaps that Git has managed to take, in distributed source code management, how does the existing SmallTalk community feel about it's current tooling in this regard? Thanks, Victor Stan Schedule me: http://quicklyschedule.quicklyschedule.me/victor Add me to your address book - it's easy! http://contactmonkey.com/victor

March 20, 2013

Re: [Pharo-users] suggestion for book code snippets

by Sean P. DeNigris

stephane ducasse wrote > normally code snippet in the book that are tagged with a special tag are > extracted and run as unit tests. > This is long time that I did not try but this was working. Is there a Jenkins job? ----- Cheers, Sean -- View this message in context: http://forum.world.st/suggestion-for-book-code-snippets-tp4677338p4677420.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 19, 2013

Re: [Pharo-users] suggestion for book code snippets

by stephane ducasse

> I think it would be a good idea to have the book code snippets > Incorporated into a SUnit regression test suite. normally code snippet in the book that are tagged with a special tag are extracted and run as unit tests. This is long time that I did not try but this was working. > (If doc is not treated as code, then sooner or later it will get out of > sync...)

March 19, 2013

Re: [Pharo-users] Keymappings 101 tutorial

by phil＠highoctane.be

very. Thanks for writing that! Phil 2013/3/19 Guillermo Polito <guillermopolito(a)gmail.com>: > Hi guys, > > I've written a little tutorial on Keymappings for Pharo 2.0. > > http://playingwithobjects.wordpress.com/2013/03/19/keymappings-101-for-phar… > > Hope it's useful :), > Guille

March 19, 2013

Keymappings 101 tutorial

by Guillermo Polito

Hi guys, I've written a little tutorial on Keymappings for Pharo 2.0. http://playingwithobjects.wordpress.com/2013/03/19/keymappings-101-for-phar… Hope it's useful :), Guille

March 19, 2013

Re: [Pharo-users] [Esug-list] [ANN] Pharo 2.0

by Sven Van Caekenberghe

OK, my bad, Robert, I assumed the first part was from the example, and the second was from you. Well, then the code in the help browser is wrong, we'll have to kill whoever wrote that. BTW, I am older than you think, not that it is relevant. On 19 Mar 2013, at 17:24, Robert Shiplett <grshiplett(a)gmail.com> wrote: > "your code" > > Are you sure you read MY mail, Sven ? > > > The snippet in not MINE ! It is in the Pharo 2.0 HelpBrowser ! > > Were you even born when I was first unhappy with Smalltalk Digitalk/ParcPlace fiasco ? > > Do you know anything about MY code over the last decades ? > > Have I EVER troubled you with MY code ? > > > ... me relatives in Appalachia are also friendlie after a fashion ... even those that cain t reed > > > > > On 19 March 2013 13:13, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 19 Mar 2013, at 17:04, Robert Shiplett <grshiplett(a)gmail.com> wrote: > > > "RUN" is the issue ... Sven is sure I was doing INSPECT when I am sure I was using CTRL-D > > Sorry to be persistent but I am unhappy when people don't read correctly what I write ;-) > > I did take the time to run your code, I don't have to do that. > > This was your second example: > > Transcript open. > > | announcer | > World announcer > on: WindowOpened > send: #value > to: [:ea | ea inspect. Transcript show: 'A new window was opened';cr]. > > > Whether you did a 'Do it' or 'Inspect it' is irrelevant, you executed it. > > It has 2 separate problems: > > 1. > > you have to say #value: not #value because your block takes an argument. > > that is a mistake that you introduced yourself and that was not in the original example. > > but as I said, there should not be an emergency evaluator (although it contained the explanation) - so that is something we can try to improve. > > thanks again for reporting that. > > 2. > > ea inspect opens an inspector, which is a window, which triggers your code, which is an infinite loop. > > I can't say this any other way. > > Sven >

March 19, 2013

Re: [Pharo-users] [Esug-list] [ANN] Pharo 2.0

by Robert Shiplett

thanks for noticing that ... I miss alot these daes By 2030 there will be more old folks than young ... will we use Clojure or Smalltalk ? Well, the quality of the postLISP Curl debugger means that I am still able to use Curl in old IDE for now ... but Smalltalk should be their fallback enviro --- On 19 March 2013 12:42, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-03-19, at 16:41, Robert Shiplett <grshiplett(a)gmail.com> wrote: > > > You are not allowed to post to this mailing list, and your message has > > been automatically rejected. If you think that your messages are > > being rejected in error, contact the mailing list owner at > > pharo-project-owner(a)lists.gforge.inria.fr. > > > > > > I get this today ... but I can Post by REPLY here in my email ... > > not the same mailing list: > > pharo-project: dev mailing list > pharo-users: user mailing list > >

March 19, 2013

Re: [Pharo-users] [Esug-list] [ANN] Pharo 2.0

by Robert Shiplett

"your code" Are you sure you read MY mail, Sven ? The snippet in not MINE ! It is in the Pharo 2.0 HelpBrowser ! Were you even born when I was first unhappy with Smalltalk Digitalk/ParcPlace fiasco ? Do you know anything about MY code over the last decades ? Have I EVER troubled you with MY code ? ... me relatives in Appalachia are also friendlie after a fashion ... even those that cain t reed On 19 March 2013 13:13, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 19 Mar 2013, at 17:04, Robert Shiplett <grshiplett(a)gmail.com> wrote: > > > "RUN" is the issue ... Sven is sure I was doing INSPECT when I am sure I > was using CTRL-D > > Sorry to be persistent but I am unhappy when people don't read correctly > what I write ;-) > > I did take the time to run your code, I don't have to do that. > > This was your second example: > > Transcript open. > > | announcer | > World announcer > on: WindowOpened > send: #value > to: [:ea | ea inspect. Transcript show: 'A new window was > opened';cr]. > > > Whether you did a 'Do it' or 'Inspect it' is irrelevant, you executed it. > > It has 2 separate problems: > > 1. > > you have to say #value: not #value because your block takes an argument. > > that is a mistake that you introduced yourself and that was not in the > original example. > > but as I said, there should not be an emergency evaluator (although it > contained the explanation) - so that is something we can try to improve. > > thanks again for reporting that. > > 2. > > ea inspect opens an inspector, which is a window, which triggers your > code, which is an infinite loop. > > I can't say this any other way. > > Sven >

March 19, 2013

Re: [Pharo-users] [Esug-list] [ANN] Pharo 2.0

by Sven Van Caekenberghe

On 19 Mar 2013, at 17:04, Robert Shiplett <grshiplett(a)gmail.com> wrote: > "RUN" is the issue ... Sven is sure I was doing INSPECT when I am sure I was using CTRL-D Sorry to be persistent but I am unhappy when people don't read correctly what I write ;-) I did take the time to run your code, I don't have to do that. This was your second example: Transcript open. | announcer | World announcer on: WindowOpened send: #value to: [:ea | ea inspect. Transcript show: 'A new window was opened';cr]. Whether you did a 'Do it' or 'Inspect it' is irrelevant, you executed it. It has 2 separate problems: 1. you have to say #value: not #value because your block takes an argument. that is a mistake that you introduced yourself and that was not in the original example. but as I said, there should not be an emergency evaluator (although it contained the explanation) - so that is something we can try to improve. thanks again for reporting that. 2. ea inspect opens an inspector, which is a window, which triggers your code, which is an infinite loop. I can't say this any other way. Sven

March 19, 2013

Re: [Pharo-users] [Esug-list] [ANN] Pharo 2.0

by Camillo Bruni

>> > World announcer > on: WindowOpened > send: #value > to: [ :announcement | > Transcript show: 'A new window was opened ', announcement printString; cr ]. > > (different selector). thanks, I wasn't sure about that :), still strange though that the on:fork: is not used directly. I'll open an issue for that.

March 19, 2013