- Pharo-dev - lists.pharo.org

Experiments in Code Typography

by Alexandre Bergel

Hi! Iâve found this interesting illustrated short article by Sean McDirmid: http://research.microsoft.com/en-us/projects/liveprogramming/typography.aspx Some may find it interesting. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 31, 2014

Contributions about Pharo and Moose

by Alain Rastoul

Hi all, This afternoon, my bike didn't start (the battery got weaker every day this week, no surprise), so I've put it in charge and decided to take a ride on the latest Pharo and Moose versions instead :) First I downloaded the latest Pharo 4 image, opened a Workspace and got an error clicking on the right arrow of the window to display the menu. I searched opened cases and saw issue 13865 (cleaning MenuMorph) and added a comment about the fix I am not a contributor to Pharo right now though I'm willing to, I believe I could do some minor cases like that one (I might have to check first with my employer about some intellectual property agreement I've signed in the past, but I guess no problem here). BTW I took a look at the video and slides 'how to contribute', opened and account on SmalltalkHub but didn't get the mail to confirm my registration right now. My first question is just a confirmation: I saw in the slides that to commit slices, one has to be given write access by asking in this mailing list ? (In this case, I will when everything is ok). Second question is about Moose : I tried to load the Moose development configuration in this Pharo4 image (I like to play Candid) and got small errors (big ones too, I guess Moose is on the way to move to Pharo4 and there is still some hard work) I'm wondering if fogbugz is the place to report Moose bugs ? And what about other packages like for example (two of the errors I had) ConfigurationOfPetitSQLParser or Hashtable-simon_denier.31 ? Most of the Moose related issues on fogbugz seems to be related to integration into Pharo, not to Moose development or to other packages ? Is there a fogbugz or other site for Moose or do we report Moose bugs in this list ? What about external packages ? What is the process in that case ? Thanks in advance for your answers Regards, Alain

Aug. 31, 2014

Having some trouble on the Pharo Contributions CI

by Sven Van Caekenberghe

Hi, I seem to be having some trouble on the Pharo Contributions CI. I successfully created some projects before, but this time something strange is happening. It seems as if a win7 slave is doing the build instead of the linux slaves that I am used to. Has something changed ? I want to detect that I am running on the CI so that I can skip some tests that require resources not available there, but I fear the following won't work on Windows: runningOnInriaCI | platform ci | ^ [ platform := OSPlatform current. ci := platform environment at: #CI ifAbsent: [ '' ]. ci = 'ci.inria.fr' ] on: MessageNotUnderstood do: [ false ] What is the recommended way to use linux-only slaves ? Any other ideas ? Thanks, Sven

Aug. 31, 2014

Re: [Pharo-dev] Glorp Login>>#encodingStrategy

by Sven Van Caekenberghe

OK, it seems that setting the encoding to #utf8 is needed when talking to a PG DB that has UTF8 encoding as well for non ASCII to work. Good. On 28 Aug 2014, at 23:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 27 Aug 2014, at 18:20, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> 2014-08-27 12:38 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>> It seems that Glorp Login>>#encodingStrategy is not used by the NativePostgresDriver yet it is required to set it to a non nil value to get things working. This feels like a hack or something unfinished. >> >> How so? >> >> PGConnection>>#clientEncoding: sets instance variables >> sqlStringConverter and receivingTextConverter, which are used to >> convert text back and forth from Pharo to the socket (see >> PGConnection>>#execute:) >> >> It is really convoluted, but I guess this has to do with the pass of >> time, and also with the half-backed (IMO) driver independence and >> dialect compatibility. >> >> Regards! >> >> Esteban A. Maringolo > > Thanks for your answer. > > I was confused by the name change between encodingStrategy and clientEncoding. You are right it is used. But my point remains that unless you set encodingStrategy on Login to something you get an error when nil in converted to a Symbol (in #connectionArgsFromCurrentLogin:). Now, I set it to #default which does not exist as encoding and leads to no encoding at all. That seems to indicate that it is not needed, but I am not sure. > > Sven > > The before last line of #connectionArgsFromCurrentLogin: could be changed to > > aLogin encodingStrategy ifNotNil: [ :enc | connectionArgs clientEncoding: enc asSymbol ]. > >

Aug. 31, 2014

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

by Sven Van Caekenberghe

On 30 Aug 2014, at 01:40, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > It could be #stable, I just was afraid of breaking somebody else > stuff. I'm a champion at f*king up third parties repositories. :) I'll take the risk for you then: === Name: ConfigurationOfPostgresV2-SvenVanCaekenberghe.11 Author: SvenVanCaekenberghe Time: 31 August 2014, 12:04:35.32701 pm UUID: eaf9ae38-654b-43c9-8312-2a3ce8d1d26d Ancestors: ConfigurationOfPostgresV2-EstebanMaringolo.10 Updated #stable to version 2.3 to ensure pharo 3 compatibility === > Regards! > > Esteban A. Maringolo > > 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 Sven

Aug. 31, 2014

Re: [Pharo-dev] Please add me to the PharoExtras team

by Sven Van Caekenberghe

Thank you. On 31 Aug 2014, at 12:20, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > done > > On 31 Aug 2014, at 12:09, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Can somebody please add me to the PharoExtras team ? >> >> http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe >> >> > >

Aug. 31, 2014

Re: [Pharo-dev] Please add me to the PharoExtras team

by Esteban Lorenzano

done On 31 Aug 2014, at 12:09, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Can somebody please add me to the PharoExtras team ? > > http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe > >

Aug. 31, 2014

Please add me to the PharoExtras team

by Sven Van Caekenberghe

Can somebody please add me to the PharoExtras team ? http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe

Aug. 31, 2014

Re: [Pharo-dev] about to integrate GTools, there is a command conflict who needs attention

by Tim Mackinnon

Anything that starts to rationalise keystrokes is definitely appreciated. Particularly with thought to similar operations using the same keystrokes in different browsers. While it's taken some effort to get used to the newer multi-key shortcuts, the fact that it allows more more-reasonably grouped keys is a win. I really want more keystrokes for refactorings and other code operations - that multi-keys makes room for. So please keep pushing on this. Tim Sent from my iPhone > On 29 Aug 2014, at 07:30 pm, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Cmd+o cannot be mapped on Cmd+s because when you are in the code editor of the inspector, you want to both be able to accept the code and open the result of a selection. > > In the moose image we remove the global bindings altogether, so I would be certainly fine with rebinding them. That is until we find a better solution :) > > Cheers, > Doru > > >> On Fri, Aug 29, 2014 at 10:54 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi guys, >> >> We are on our way to integrate (finally) GTools into Pharo. >> For now it will be the Playground and the Inspector, since the Debugger is still not ready. >> >> Now, Iâm facing a problem. The new command for playground (cmd+o) conflicts with some menyu commands: (cmd+o+[w|t|etc]). Since we cannot handle both, we need to choose one. >> I do not have a clear idea, so I want your opinions. >> So far, I think this: >> >> 1) cmd+o in playground is not so clear, maybe we could map thet to an âacceptâ (cmd+s) or an âexecureâ (cmd+e)â¦ >> 2) we could map cmd+o+etc. to something else. But I do not know to what. >> >> So, I hear opinions :) >> >> Esteban > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Aug. 31, 2014

Re: [Pharo-dev] Future of Spec

by Martin Saurer

It's already planned ;-) Martin > as far as I understand J is an APL like language so I was wondering > with you do not have J binding inside pharo :) ? > and script J from there? > > Stef

Aug. 31, 2014