July 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Launcher

by Damien Cassou

On Mon, Jul 8, 2013 at 10:35 AM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > a more deeper integration with ZeroConf so we can do use it on the command line. Camillo and Damien P have started looking at that -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 8, 2013

Re: [Pharo-dev] [ANN] Pharo Launcher

by Serge Stinckwich

On Mon, Jul 8, 2013 at 10:11 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Dear list, > > Erwan and I are proud to announce the first release of the Pharo > Launcher, a cross-platform application that > > - lets you manage your Pharo images (launch, rename, copy and delete); > - lets you download image templates (i.e., zip archives) from many > different sources (Jenkins, files.pharo.org, and your local cache); > - lets you create new images from any template. > > A screenshot is attached to this email. > > The idea behind the Pharo Launcher is that you should be able to > access it very rapidly from your OS application launcher. As a result, > launching any image is never more than 3 clicks away. > > Download: https://ci.inria.fr/pharo-contribution/job/PharoLauncher/PHARO=30,VERSION=b… > > Please report bugs on the 'Launcher' project at https://pharo.fogbugz.org > > You can contribute to this project. All classes and most methods are > commented. There are unit tests. Please contribute! > > Source code: http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher > CI: https://ci.inria.fr/pharo-contribution/job/PharoLauncher > > Things you can do to improve the system: > > - check if a template is already downloaded before downloading it > - add a preference mechanism (for, e.g., quit after launch, definition > of your own template groups, location of downloaded templates and > images) > - put the launcher in the Pharo Ubuntu package so that the launcher > becomes a registered appliation of the system > (https://launchpad.net/~pharo/+archive/stable) > - make sure the pharo launcher does not load your personal scripts > (like fonts and MC configuration) > - add a toolbar to enhance the discoverability of the features > (currently everything is in contextual menus) > - make sure rename and copy actions propose default values > - make sure no debugger pops up when a user press cancels or enter an > invalid name > - propose multiple kinds of sorting (last used, most frequently used, > alphabetically on the name) > - give some information about each template (build date, pharo version) Great Job Damien and Erwan ! This will definitively help me to solve the images mess issue on my disk ;-) What could be nice in the future is the possibility to choose the VM also and maybe a more deeper integration with ZeroConf so we can do use it on the command line. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

July 8, 2013

Re: [Pharo-dev] Pharo and scaled decimals

by Marcus Denker

On Jul 8, 2013, at 8:45 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > https://pharo.fogbugz.com/default.asp?11149 There is already https://pharo.fogbugz.com/f/cases/10016 And yes, we need more people to look at the bug tracker (but everyone knows that). Marcus > > On Jul 8, 2013, at 8:43 AM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > >> It seems that we never integrate this change (there was not bug entry :)). >> I will open a bug entry if not. >> >> Stef >> >> Begin forwarded message: >> >>> From: David Gorisek <david.gorisek(a)e-racuni.com> >>> To: pharo-project(a)lists.gforge.inria.fr >>> Cc: >>> Date: Wed, 13 Mar 2013 22:24:04 +0100 >>> Subject: Pharo and scaled decimals >>> Hello all, >>> >>> I am testing Pharo and I have noticed that the Pharo compiler does not treat ScaledDecimals the same way they are treated in other Smalltalk dialects (e.g. VW, VAST, Dolphin, STX, etc.). >>> >>> For example the following is a valid code representing an instance of ScaledDecimal/FixedPoint in all other dialect. >>> >>> 1.0s + 2.0s >>> >>> In Phare the code above wont compile, it has to be written as: >>> >>> 1.0s1 + 2.0s1 >>> >>> So I have made the following quick change to make Pharo compatible with other Smalltalk dialects. Maybe this change could be included in the next version of Pharo? >>> >>> SqNumberParser>>#readScale >>> "read the scale if any (stored in instVar). >>> Answer true if found, answer false if none. >>> If scale letter is not followed by a digit, this is not considered as an error. >>> Scales are always read in base 10, though i do not see why..." >>> >>> scale := 0. >>> sourceStream atEnd >>> ifTrue: [ ^ false ]. >>> (sourceStream peekFor: $s) >>> ifFalse: [ ^ false ]. >>> scale := self nextUnsignedIntegerOrNilBase: 10. >>> scale >>> ifNil: [ >>> scale := 0. >>> (sourceStream peek ifNil: [false] ifNotNil: [ :nextChar | nextChar isLetter]) >>> ifTrue: [ >>> sourceStream skip: -1. "ungobble the s" >>> ^ false ] >>> ifFalse: [ ^ true ] ]. >>> ^ true >> >

July 8, 2013

[ANN] Pharo Launcher

by Damien Cassou

Dear list, Erwan and I are proud to announce the first release of the Pharo Launcher, a cross-platform application that - lets you manage your Pharo images (launch, rename, copy and delete); - lets you download image templates (i.e., zip archives) from many different sources (Jenkins, files.pharo.org, and your local cache); - lets you create new images from any template. A screenshot is attached to this email. The idea behind the Pharo Launcher is that you should be able to access it very rapidly from your OS application launcher. As a result, launching any image is never more than 3 clicks away. Download: https://ci.inria.fr/pharo-contribution/job/PharoLauncher/PHARO=30,VERSION=b… Please report bugs on the 'Launcher' project at https://pharo.fogbugz.org You can contribute to this project. All classes and most methods are commented. There are unit tests. Please contribute! Source code: http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher CI: https://ci.inria.fr/pharo-contribution/job/PharoLauncher Things you can do to improve the system: - check if a template is already downloaded before downloading it - add a preference mechanism (for, e.g., quit after launch, definition of your own template groups, location of downloaded templates and images) - put the launcher in the Pharo Ubuntu package so that the launcher becomes a registered appliation of the system (https://launchpad.net/~pharo/+archive/stable) - make sure the pharo launcher does not load your personal scripts (like fonts and MC configuration) - add a toolbar to enhance the discoverability of the features (currently everything is in contextual menus) - make sure rename and copy actions propose default values - make sure no debugger pops up when a user press cancels or enter an invalid name - propose multiple kinds of sorting (last used, most frequently used, alphabetically on the name) - give some information about each template (build date, pharo version) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 8, 2013

Re: [Pharo-dev] YAML Parser?

by Sven Van Caekenberghe

On 08 Jul 2013, at 08:47, Tobias Pape <Das.Linux(a)gmx.de> wrote: > Am 07.07.2013 um 22:27 schrieb Stefan Marr <smalltalk(a)stefan-marr.de>: > >> Hi: >> >> Is anyone aware of a YAML parser that's compatible with Pharo 1.4 and 2.0? (http://yaml.org/) >> >> I am using only the most basic features, so, it wouldn't need to be feature complete. > > > To my knowledge, there is none. > I almost started one myself. > > Best > -Tobias These things are always fun to write. Clear spec, lots of implementations. Ideal project to get deeper in Pharo and into contributing a well documented library to benefit the rest of the community ;-) Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

July 8, 2013

Re: [Pharo-dev] NeoCSV doc is now on Gutenberg :)

by StÃ©phane Ducasse

Sean if you read it and get some ideas for the missing examples please edit the file or send them to me Stef On Jul 8, 2013, at 2:27 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > StÃ©phane Ducasse wrote >> I love reading documentation :) > > Yes, and the NeoCSV doc is really good :) It felt like having an expert > mentor me... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Pharo-dev-NeoCSV-doc-is-now-on-Gutenberg-tp4697733p46… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

July 8, 2013

Re: [Pharo-dev] filetree jenkins job

by Frank Shearar

On 7 July 2013 23:11, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I will change SUnit first produce proper error messages for the #shouldnt:raise: methods since I cannot properly debug them. > Additionally at the point where the #:assert: happens the wrong exception is not in the context which means it does not get properly serialized by our test framework. All in all, with a little effort we could debug much easier. I found this a big improvement: TestCase >> shouldnt: aBlock raise: anExceptionalEvent ^ [ aBlock value ] on: anExceptionalEvent do: [:e | self fail: 'Block raised ', e className, ': ', e messageText]. TestCase >> fail: aString ^self assert: false description: aString. frank > BTW: There are so many strange methods on TAssertable that I do not understand > - #shouldFix: > - #executeShould:inScopeOf: > > and some that I honestly think they hurt more than they help: > - #shouldnt:raise:whoseDescriptionIncludes:description: and friends? > > On 2013-07-07, at 23:47, "Dale K. Henrichs" <dale.henrichs(a)gemtalksystems.com> wrote: > >> Cami, >> >> I've been having trouble with getting any useful information from Pharo3.0 failures on travis-ci[1] for a week or so now ... Christophe will be looking into this for me... >> >> Dale >> >> [1] https://github.com/dalehenrich/filetree/issues/80#issuecomment-20162125 >> ----- Original Message ----- >> | From: "Camillo Bruni" <camillobruni(a)gmail.com> >> | To: pharo-dev(a)lists.pharo.org >> | Sent: Sunday, July 7, 2013 2:00:10 PM >> | Subject: [Pharo-dev] filetree jenkins job >> | >> | after I tried to get filetree with the tests installed and I didn't >> | get it >> | the first time I decided to create a jenkins job. >> | >> | https://ci.inria.fr/pharo-contribution/job/FileTree/ >> | >> | >> > >

July 8, 2013

Re: [Pharo-dev] YAML Parser?

by Tobias Pape

Am 07.07.2013 um 22:27 schrieb Stefan Marr <smalltalk(a)stefan-marr.de>: > Hi: > > Is anyone aware of a YAML parser that's compatible with Pharo 1.4 and 2.0? (http://yaml.org/) > > I am using only the most basic features, so, it wouldn't need to be feature complete. To my knowledge, there is none. I almost started one myself. Best -Tobias

July 8, 2013

Re: [Pharo-dev] Pharo and scaled decimals

by StÃ©phane Ducasse

https://pharo.fogbugz.com/default.asp?11149 On Jul 8, 2013, at 8:43 AM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > It seems that we never integrate this change (there was not bug entry :)). > I will open a bug entry if not. > > Stef > > Begin forwarded message: > >> From: David Gorisek <david.gorisek(a)e-racuni.com> >> To: pharo-project(a)lists.gforge.inria.fr >> Cc: >> Date: Wed, 13 Mar 2013 22:24:04 +0100 >> Subject: Pharo and scaled decimals >> Hello all, >> >> I am testing Pharo and I have noticed that the Pharo compiler does not treat ScaledDecimals the same way they are treated in other Smalltalk dialects (e.g. VW, VAST, Dolphin, STX, etc.). >> >> For example the following is a valid code representing an instance of ScaledDecimal/FixedPoint in all other dialect. >> >> 1.0s + 2.0s >> >> In Phare the code above wont compile, it has to be written as: >> >> 1.0s1 + 2.0s1 >> >> So I have made the following quick change to make Pharo compatible with other Smalltalk dialects. Maybe this change could be included in the next version of Pharo? >> >> SqNumberParser>>#readScale >> "read the scale if any (stored in instVar). >> Answer true if found, answer false if none. >> If scale letter is not followed by a digit, this is not considered as an error. >> Scales are always read in base 10, though i do not see why..." >> >> scale := 0. >> sourceStream atEnd >> ifTrue: [ ^ false ]. >> (sourceStream peekFor: $s) >> ifFalse: [ ^ false ]. >> scale := self nextUnsignedIntegerOrNilBase: 10. >> scale >> ifNil: [ >> scale := 0. >> (sourceStream peek ifNil: [false] ifNotNil: [ :nextChar | nextChar isLetter]) >> ifTrue: [ >> sourceStream skip: -1. "ungobble the s" >> ^ false ] >> ifFalse: [ ^ true ] ]. >> ^ true >

July 8, 2013

Fwd: Pharo and scaled decimals

by StÃ©phane Ducasse

It seems that we never integrate this change (there was not bug entry :)). I will open a bug entry if not. Stef Begin forwarded message: > From: David Gorisek <david.gorisek(a)e-racuni.com> > To: pharo-project(a)lists.gforge.inria.fr > Cc: > Date: Wed, 13 Mar 2013 22:24:04 +0100 > Subject: Pharo and scaled decimals > Hello all, > > I am testing Pharo and I have noticed that the Pharo compiler does not treat ScaledDecimals the same way they are treated in other Smalltalk dialects (e.g. VW, VAST, Dolphin, STX, etc.). > > For example the following is a valid code representing an instance of ScaledDecimal/FixedPoint in all other dialect. > > 1.0s + 2.0s > > In Phare the code above wont compile, it has to be written as: > > 1.0s1 + 2.0s1 > > So I have made the following quick change to make Pharo compatible with other Smalltalk dialects. Maybe this change could be included in the next version of Pharo? > > SqNumberParser>>#readScale > "read the scale if any (stored in instVar). > Answer true if found, answer false if none. > If scale letter is not followed by a digit, this is not considered as an error. > Scales are always read in base 10, though i do not see why..." > > scale := 0. > sourceStream atEnd > ifTrue: [ ^ false ]. > (sourceStream peekFor: $s) > ifFalse: [ ^ false ]. > scale := self nextUnsignedIntegerOrNilBase: 10. > scale > ifNil: [ > scale := 0. > (sourceStream peek ifNil: [false] ifNotNil: [ :nextChar | nextChar isLetter]) > ifTrue: [ > sourceStream skip: -1. "ungobble the s" > ^ false ] > ifFalse: [ ^ true ] ]. > ^ true

July 8, 2013