- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] [Article] Reddit.st - In 10 Cool Pharo Classes

by Johan Fabry

Whoa, another cool tutorial article of yours. Excellent work! I have a question: I was thinking about giving the HP-35 article and this article to some CS students of mine that have 0 Smalltalk experience, to get them up to speed. But the tutorials are missing the basic explanation of the use of workspaces and browsers, and I donât know where to get some documentation that treats just that. Any pointers to that kind of material? TIA, On Sep 1, 2014, at 5:18 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > I published another introduction/tutorial article > > Reddit.st - In 10 Cool Pharo Classes > > Implementing a Reddit style web application in Pharo using Seaside, Glorp and PostgreSQL > > https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 > > The focus is not so much on the smaller size or the higher developer productivity in Pharo, but more on the fact that we can cover so much ground using such powerful frameworks, as well as the natural development flow from model over tests and persistence to web GUI. This is a more intermediate level article that assumes basic knowledge about Pharo (language and IDE). > > https://ci.inria.fr/pharo-contribution/job/Reddit/ > > http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Reddit > > Enjoy! > > Sven > > PS: This article is actually an update of an article that I wrote in 2010 and that became unavailable/outdated. > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Sept. 2, 2014

Re: [Pharo-dev] [Article] Reddit.st - In 10 Cool Pharo Classes

by garduino

Very interesting article! -- View this message in context: http://forum.world.st/Article-Reddit-st-In-10-Cool-Pharo-Classes-tp4775686p… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 2, 2014

Re: [Pharo-dev] SqNumberParser and PGConnection in Pharo 3

by Esteban A. Maringolo

Oh, Sorry, I didn't see your last question. Thank you. Esteban A. Maringolo 2014-09-02 12:14 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > I merged your branch and declared the result stable for Pharo 3: > > === > Name: Glorp-SvenVanCaekenberghe.89 > Author: SvenVanCaekenberghe > Time: 2 September 2014, 5:08:03.507586 pm > UUID: 5c4bda4a-9395-4015-b388-c8ce00b65e19 > Ancestors: Glorp-MarianoMartinezPeck.88, Glorp-EstebanMaringolo.87 > > Merging with Esteban Maringolo's branch: adding a #dataAndTime PostgreSQL type for Pharo > === > Name: ConfigurationOfGlorp-SvenVanCaekenberghe.38 > Author: SvenVanCaekenberghe > Time: 2 September 2014, 5:12:20.404014 pm > UUID: a8d54504-7a5a-4a43-92cd-3d66b252611e > Ancestors: ConfigurationOfGlorp-EstebanMaringolo.37 > > Moved to #stable 1.7 for Pharo 3+ > === > > On 01 Sep 2014, at 08:06, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 01 Sep 2014, at 00:21, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >>> Yes... it was intentional. >> >> OK, but what about the second part, about it being non-intrusive ? >> >>> Because there is no "official" maintainer of the GLORP package, I >>> didn't want to add stuff to the main codebase. Same story as with the >>> PostgresV2 package. >>> >>> Regards! >>> >>> Esteban A. Maringolo >>> >>> >>> 2014-08-31 19:16 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>> >>>> On 31 Aug 2014, at 12:27, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>>>> ps: There is also other versions of GLORP I didn't bless as #stable. >>>>> >>>>> That seems a bit more complicated: the Glorp ancestry is mixed up, we should merge this carefully: >>>>> >>>>> you made versions 86 & 87 while those already existed, the latest 88 skips your version. >>>>> >>>>> in any case, 88 now works for me, but I fear it skips your code >>>> >>>> Ah, I see, this was an intentional branch, right ? >>>> >>>> Anyway, your addition seems non-intrusive, since it only adds a type, which does not get used unless one specifically asks for it, correct ? >>>> >>>> If so, I can merge this, commit a new version and update the config. >>>> >>>> Sven >>> >> > >

Sept. 2, 2014

NonInteractiveTranscript and Debugging issue in headless image

by phil＠highoctane.be

I've got this error when the debugger is triggered in a headless image. So, #MNU. I had a look at the NonInteractiveTranscript and it has this method missing indeed in 3.0. I've added a basic one but we could benefit from enhanced debugging abilities on that front. As I am running on a server without any graphics abilities, it would be welcome to have this fixed. I added this to the startup script to patch the thing: Author fullName: 'PhilippeBack'. "Avoid yet another question..." NonInteractiveUIManager compile: 'openDebuggerOn: process context: context label: title contents: contentsStringOrNil fullView: bool ^ self nonInteractiveWarning: ''Opening Debugger''' classified: #'ui-requests'. So far so good, but it turned to: An attempt to use interactive tools detected, while in non-interactive mode Opening Debugger NonInteractiveUIManager>>nonInteractiveWarning: NonInteractiveUIManager>>openDebuggerOn:context:label:contents:fullView: SpecDebugger class>>openOn:context:label:contents:fullView: Process>>debug:title:full: GRPharoPlatform>>openDebuggerOn: in Block: [ process debug: anError signalerContext title: an...etc... And the vm stopped again. Looks like: NonInteractiveUIManager>>nonInteractiveWarning: aWarnMessage ^ ErrorNonInteractive signal: aWarnMessage isn't too friendly. How would one get debugging info shown and just proceed or close the debugger? Closing the image is really hard to swallow here. Ideas? Phil

Sept. 2, 2014

Re: [Pharo-dev] Surrounding text in editors

by Nicolai Hess

Known problem :) http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2014-August/0996… it is realated to hardcoding keyboard layout in TextEditor>>#shiftEnclose there are already open issues on fogbugz and nicolas proposed solution (I think). 2014-09-02 16:53 GMT+02:00 Torsten Bergmann <astares(a)gmx.de>: > Hi, > > 1. When I open a workspace and type > > Hello > > in it. Now I select the whole text and hit the $" key > to make it a comment. This works, the workspace > shows > > "Hello" > > on both sides and I can continue to work with my comment. > > > 2. When I open a workspace and type > > Hello > > in it. Now I select the whole text and hit the $' key > to make it a string. This does not works, the workspace > again shows: > > "Hello" > > on both sides - which is a comment, but I would have expected a string: > > 'Hello' > > Is this a known problem. Is it related to Windows only - can one > check on other platforms? Should we open an issue? > > Seems to work well for brackets and braces by the way: > Selecting Hello with an additional $[ key gives correctly [Hello] > Selecting Hello with an additional $( key gives correctly (Hello) > > Thx > T. > >

Sept. 2, 2014

Re: [Pharo-dev] SqNumberParser and PGConnection in Pharo 3

by Sven Van Caekenberghe

I merged your branch and declared the result stable for Pharo 3: === Name: Glorp-SvenVanCaekenberghe.89 Author: SvenVanCaekenberghe Time: 2 September 2014, 5:08:03.507586 pm UUID: 5c4bda4a-9395-4015-b388-c8ce00b65e19 Ancestors: Glorp-MarianoMartinezPeck.88, Glorp-EstebanMaringolo.87 Merging with Esteban Maringolo's branch: adding a #dataAndTime PostgreSQL type for Pharo === Name: ConfigurationOfGlorp-SvenVanCaekenberghe.38 Author: SvenVanCaekenberghe Time: 2 September 2014, 5:12:20.404014 pm UUID: a8d54504-7a5a-4a43-92cd-3d66b252611e Ancestors: ConfigurationOfGlorp-EstebanMaringolo.37 Moved to #stable 1.7 for Pharo 3+ === On 01 Sep 2014, at 08:06, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 01 Sep 2014, at 00:21, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> Yes... it was intentional. > > OK, but what about the second part, about it being non-intrusive ? > >> Because there is no "official" maintainer of the GLORP package, I >> didn't want to add stuff to the main codebase. Same story as with the >> PostgresV2 package. >> >> Regards! >> >> Esteban A. Maringolo >> >> >> 2014-08-31 19:16 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>> On 31 Aug 2014, at 12:27, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>>>> ps: There is also other versions of GLORP I didn't bless as #stable. >>>> >>>> That seems a bit more complicated: the Glorp ancestry is mixed up, we should merge this carefully: >>>> >>>> you made versions 86 & 87 while those already existed, the latest 88 skips your version. >>>> >>>> in any case, 88 now works for me, but I fear it skips your code >>> >>> Ah, I see, this was an intentional branch, right ? >>> >>> Anyway, your addition seems non-intrusive, since it only adds a type, which does not get used unless one specifically asks for it, correct ? >>> >>> If so, I can merge this, commit a new version and update the config. >>> >>> Sven >> >

Sept. 2, 2014

Re: [Pharo-dev] Surrounding text in editors

by Esteban A. Maringolo

That works for me, however I have issues with selecting text and trying to enclose it in square brackets, It always encloses the text between regular brackets { } Open bracket, open square bracket and caret share the same key in Spanish LA keyboard, square requires shift modifier, caret requires Alt Gr. Regards! Esteban A. Maringolo 2014-09-02 11:53 GMT-03:00 Torsten Bergmann <astares(a)gmx.de>: > Hi, > > 1. When I open a workspace and type > > Hello > > in it. Now I select the whole text and hit the $" key > to make it a comment. This works, the workspace > shows > > "Hello" > > on both sides and I can continue to work with my comment. > > > 2. When I open a workspace and type > > Hello > > in it. Now I select the whole text and hit the $' key > to make it a string. This does not works, the workspace > again shows: > > "Hello" > > on both sides - which is a comment, but I would have expected a string: > > 'Hello' > > Is this a known problem. Is it related to Windows only - can one > check on other platforms? Should we open an issue? > > Seems to work well for brackets and braces by the way: > Selecting Hello with an additional $[ key gives correctly [Hello] > Selecting Hello with an additional $( key gives correctly (Hello) > > Thx > T. >

Sept. 2, 2014

Re: [Pharo-dev] Surrounding text in editors

by Sven Van Caekenberghe

I believe this is related to your German keyboard, as has been discussed on the list recently. In any case it works for me. On 02 Sep 2014, at 16:53, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > 1. When I open a workspace and type > > Hello > > in it. Now I select the whole text and hit the $" key > to make it a comment. This works, the workspace > shows > > "Hello" > > on both sides and I can continue to work with my comment. > > > 2. When I open a workspace and type > > Hello > > in it. Now I select the whole text and hit the $' key > to make it a string. This does not works, the workspace > again shows: > > "Hello" > > on both sides - which is a comment, but I would have expected a string: > > 'Hello' > > Is this a known problem. Is it related to Windows only - can one > check on other platforms? Should we open an issue? > > Seems to work well for brackets and braces by the way: > Selecting Hello with an additional $[ key gives correctly [Hello] > Selecting Hello with an additional $( key gives correctly (Hello) > > Thx > T. >

Sept. 2, 2014

Surrounding text in editors

by Torsten Bergmann

Hi, 1. When I open a workspace and type Hello in it. Now I select the whole text and hit the $" key to make it a comment. This works, the workspace shows "Hello" on both sides and I can continue to work with my comment. 2. When I open a workspace and type Hello in it. Now I select the whole text and hit the $' key to make it a string. This does not works, the workspace again shows: "Hello" on both sides - which is a comment, but I would have expected a string: 'Hello' Is this a known problem. Is it related to Windows only - can one check on other platforms? Should we open an issue? Seems to work well for brackets and braces by the way: Selecting Hello with an additional $[ key gives correctly [Hello] Selecting Hello with an additional $( key gives correctly (Hello) Thx T.

Sept. 2, 2014

Re: [Pharo-dev] #literals in RBSmalllintContext

by Yuriy Tymchuk

Yes, Iâm wandering if I can reimplement #uses: in some other wayâ¦ Uko On 02 Sep 2014, at 16:44, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > On 2 sept. 2014, at 16:21, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> Hi, does anybody know what #literals in RBSmalllintContext stand for? Because itâs calculated in a very weird way with the use of literalSemaphore and literalProcess variables. > > No, it's weird indeed. Apparently it stores all symbols and bindings founds in the literal arrays of all methods in the system... > A kind of cache maybe, but only used by two methods #uses: and #isAbstract (no senders for the latter BTW) > >> Uko > >

Sept. 2, 2014