March 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] [ANN] Cruiser: A Pharo app packager

by Todd Blanchard

That is very cool. Any intentions to do mobile? Inspired by David Buck's post on his mobile VM. https://medium.com/@richardeng/mobile-smalltalk-c6f0cc712909 > On Mar 8, 2018, at 12:00 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > I saw a demo of it two weeks ago. This is really good stuff! > Cruiser is about turning a Pharo app as a stand-alone application, as an .exe file from a user perspective, without knowing there is Pharo underneath. > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Mar 8, 2018, at 4:29 PM, Vincent.Blondeau(a)lamresearch.com <mailto:Vincent.Blondeau@lamresearch.com> wrote: >> >> Hi Pharoers! >> >> I pleased to announce you the first release of Cruiser: a tool to package your Pharo applications. The idea is to quickly convert an application from a development environment to a production one. A production environment means: >> No writing on the disk >> No access to the source code (by the shortcuts, debugger,...) >> No error displaying on the interface >> The only thing accessible is the user application >> >> I let you discover it on: https://github.com/VincentBlondeau/Cruiser <https://github.com/VincentBlondeau/Cruiser> >> >> <image002.png> >> >> Do not hesitate to ask me questions or contribute to improve it! >> >> Cheers, >> >> Vincent Blondeau >> Software Engineer, Software and Controls | Global Product Group >> Desk +1 510.572.7499 >> >> Lam Research Corporation >> 4650 Cushing Pkwy, Fremont, CA 94538 USA | www.lamresearch.com <x-msg://107/www.lamresearch.com> >> Connect with Lam Research: Facebook <https://www.facebook.com/LamResearchCorporation> | Twitter <https://twitter.com/lamresearch> | LinkedIn <https://www.linkedin.com/company/lam-research> >> >> >> NOTICE: This e-mail transmission may contain confidential information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and destroy the original transmission and its attachments without reading them or saving them to disk. Thank you. >

March 8, 2018

Re: [Pharo-dev] [Pharo-users] [ANN] Cruiser: A Pharo app packager

by Alexandre Bergel

I saw a demo of it two weeks ago. This is really good stuff! Cruiser is about turning a Pharo app as a stand-alone application, as an .exe file from a user perspective, without knowing there is Pharo underneath. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 8, 2018, at 4:29 PM, Vincent.Blondeau(a)lamresearch.com wrote: > > Hi Pharoers! > > I pleased to announce you the first release of Cruiser: a tool to package your Pharo applications. The idea is to quickly convert an application from a development environment to a production one. A production environment means: > No writing on the disk > No access to the source code (by the shortcuts, debugger,...) > No error displaying on the interface > The only thing accessible is the user application > > I let you discover it on: https://github.com/VincentBlondeau/Cruiser <https://github.com/VincentBlondeau/Cruiser> > > <image002.png> > > Do not hesitate to ask me questions or contribute to improve it! > > Cheers, > > Vincent Blondeau > Software Engineer, Software and Controls | Global Product Group > Desk +1 510.572.7499 > > Lam Research Corporation > 4650 Cushing Pkwy, Fremont, CA 94538 USA | www.lamresearch.com <x-msg://107/www.lamresearch.com> > Connect with Lam Research: Facebook <https://www.facebook.com/LamResearchCorporation> | Twitter <https://twitter.com/lamresearch> | LinkedIn <https://www.linkedin.com/company/lam-research> > > > NOTICE: This e-mail transmission may contain confidential information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and destroy the original transmission and its attachments without reading them or saving them to disk. Thank you.

March 8, 2018

Re: [Pharo-dev] FileSystem tweaks (was Re: new pharo cheatsheet)

by Nicolas Cellier

2018-03-08 19:44 GMT+01:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Hi Sven, > > On Mar 8, 2018, at 9:55 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > On 8 Mar 2018, at 17:58, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > Hi Stef, > > > following on from Sean, (+1000 for using ordinary quotes) > > > âstringâ collection of characters => âstringâ sequence of characters > > $a, Character space Two ways to create characters => $a, Character space > two ways to denote characters (or two ways to write characters; all other > explanations in this list are not capitalized; this shouldn't be either) > > exp1. exp2 expression separator => expr1. expr2 statement separator > > ; message cascade => expr doThis ; doThat semicolon - message cascade > (c.f. exp1. exp2 expression separator) > > ^ expr caret - returns a result from a method => ^ expr caret - return a > result from a method (or, ParcPlace preference, answer a result from a > method, since we're sending messages here) > > > ... > > A unary message is one with no arguments. => A unary message has no > arguments. (c.f. A binary message takes only one argument ...) > > ... > > Set new add: 4; add: 4 ; yourself ~> aSet => Set new add: 4; add: 4 ; > yourself ~> aSet(4) > > Dictionary new at: #a put: 'Alpha' ; yourself a Dictionary => Dictionary > new at: #a put: 'Alpha' ; yourself a Dictionary(#a->'Alpha' ) > > > and then in the Files and Stream section I would give two more examples of > exactly the same sequence that use the convenience APIs. This is the > existing text: > > > work := FileSystem disk workingDirectory. > > stream := (work / âfoo.txtâ) writeStream. > > stream nextPutAll: âHello Worldâ. > > stream close. > > stream := (work / âfoo.txtâ) readStream. > > stream contents. ~> 'Hello World' > > stream close. > > > I would make it read > > > work := FileSystem disk workingDirectory. > > stream := (work / âfoo.txtâ) writeStream. > > stream nextPutAll: âHello Worldâ. > > stream close. > > stream := (work / âfoo.txtâ) readStream. > > stream contents. ~> 'Hello World' > > stream close. > > > or, more simply > > > work := FileSystem disk workingDirectory. > > (work / âfoo.txtâ) writeStreamDo: [ :fileStream | fileStream > nextPutAll: âHello Worldâ ]. > > (work / âfoo.txtâ) readStreamDo: [ :fileStream | fileStream contents] > ~> 'Hello World' > > > or, more simply still > > > work := FileSystem disk workingDirectory. > > (work / âfoo.txtâ) writeStreamDo: [ :fileStream | fileStream > nextPutAll: âHello Worldâ ]. > > (work / âfoo.txtâ) contents > ~> 'Hello > World' > > > file := FileSystem disk workingDirectory / 'foo' , 'txt'. > file ensureDelete. > file writeStreamDo: [ :fileStream | fileStream nextPutAll: 'Hello World' ]. > file contents. > file delete. > > (to make it re-entrant and a bit more concise) > > > that suggests > > file := FileSystem disk workingDirectory / 'foo' , 'txt'. > file newWriteStreamDo: [ :fileStream | fileStream nextPutAll: 'Hello > World' ]. > file contents. > file delete. > > where newWriteStreamDo: includes the file ensureDelete, or better still a > truncation, which saves the effort of deletion but (I *think*) has the same > effect. > > Hi Eliot, not exactly the same effect wrt file access rights. > > +1e10 for plain single quotes, VERY important. > > or if you can't make it fit, just give the last version > > > Finally, this seems to have fallen off the end: > > A simple, uniform and powerful model > > Pharo has a simple dynamically-typed object model: > > > Perhaps shrink the picture of the browser. You can save three lines by > writing > > OrderedCollection new > > add: 1; > > add: 2; > > add: 3. > > > as OrderedCollection new add: 1; add: 2; add: 3. > > And another by writing 2=2 ifTrue: [ Error signal: âHelpâ ]. on one line. > > > HTH > > > On Fri, Apr 8, 2016 at 12:56 PM, stepharo <stepharo(a)free.fr> wrote: > > new cheatsheet for Pharo syntax. > > Any feedback is welcome > > > Stef > > > > > -- > > _,,,^..^,,,_ > > best, Eliot > > > >

March 8, 2018

[ANN] Cruiser: A Pharo app packager

by Vincent.Blondeau＠lamresearch.com

Hi Pharoers! I pleased to announce you the first release of Cruiser: a tool to package your Pharo applications. The idea is to quickly convert an application from a development environment to a production one. A production environment means: * No writing on the disk * No access to the source code (by the shortcuts, debugger,...) * No error displaying on the interface * The only thing accessible is the user application I let you discover it on: https://github.com/VincentBlondeau/Cruiser [cid:image002.png@01D3B6D0.B0BAA0B0] Do not hesitate to ask me questions or contribute to improve it! Cheers, Vincent Blondeau Software Engineer, Software and Controls | Global Product Group Desk +1 510.572.7499 Lam Research Corporation 4650 Cushing Pkwy, Fremont, CA 94538 USA | www.lamresearch.com Connect with Lam Research: Facebook<https://www.facebook.com/LamResearchCorporation> | Twitter<https://twitter.com/lamresearch> | LinkedIn<https://www.linkedin.com/company/lam-research> ________________________________ NOTICE: This e-mail transmission may contain confidential information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and destroy the original transmission and its attachments without reading them or saving them to disk. Thank you.

March 8, 2018

FileSystem tweaks (was Re: new pharo cheatsheet)

by Eliot Miranda

Hi Sven, > On Mar 8, 2018, at 9:55 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 8 Mar 2018, at 17:58, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi Stef, >> >> following on from Sean, (+1000 for using ordinary quotes) >> >> âstringâ collection of characters => âstringâ sequence of characters >> $a, Character space Two ways to create characters => $a, Character space two ways to denote characters (or two ways to write characters; all other explanations in this list are not capitalized; this shouldn't be either) >> exp1. exp2 expression separator => expr1. expr2 statement separator >> ; message cascade => expr doThis ; doThat semicolon - message cascade (c.f. exp1. exp2 expression separator) >> ^ expr caret - returns a result from a method => ^ expr caret - return a result from a method (or, ParcPlace preference, answer a result from a method, since we're sending messages here) >> >> ... >> A unary message is one with no arguments. => A unary message has no arguments. (c.f. A binary message takes only one argument ...) >> ... >> Set new add: 4; add: 4 ; yourself ~> aSet => Set new add: 4; add: 4 ; yourself ~> aSet(4) >> Dictionary new at: #a put: 'Alpha' ; yourself a Dictionary => Dictionary new at: #a put: 'Alpha' ; yourself a Dictionary(#a->'Alpha' ) >> >> and then in the Files and Stream section I would give two more examples of exactly the same sequence that use the convenience APIs. This is the existing text: >> >> work := FileSystem disk workingDirectory. >> stream := (work / âfoo.txtâ) writeStream. >> stream nextPutAll: âHello Worldâ. >> stream close. >> stream := (work / âfoo.txtâ) readStream. >> stream contents. ~> 'Hello World' >> stream close. >> >> I would make it read >> >> work := FileSystem disk workingDirectory. >> stream := (work / âfoo.txtâ) writeStream. >> stream nextPutAll: âHello Worldâ. >> stream close. >> stream := (work / âfoo.txtâ) readStream. >> stream contents. ~> 'Hello World' >> stream close. >> >> or, more simply >> >> work := FileSystem disk workingDirectory. >> (work / âfoo.txtâ) writeStreamDo: [ :fileStream | fileStream nextPutAll: âHello Worldâ ]. >> (work / âfoo.txtâ) readStreamDo: [ :fileStream | fileStream contents] ~> 'Hello World' >> >> or, more simply still >> >> work := FileSystem disk workingDirectory. >> (work / âfoo.txtâ) writeStreamDo: [ :fileStream | fileStream nextPutAll: âHello Worldâ ]. >> (work / âfoo.txtâ) contents ~> 'Hello World' > > file := FileSystem disk workingDirectory / 'foo' , 'txt'. > file ensureDelete. > file writeStreamDo: [ :fileStream | fileStream nextPutAll: 'Hello World' ]. > file contents. > file delete. > > (to make it re-entrant and a bit more concise) that suggests file := FileSystem disk workingDirectory / 'foo' , 'txt'. file newWriteStreamDo: [ :fileStream | fileStream nextPutAll: 'Hello World' ]. file contents. file delete. where newWriteStreamDo: includes the file ensureDelete, or better still a truncation, which saves the effort of deletion but (I *think*) has the same effect. > > +1e10 for plain single quotes, VERY important. > >> or if you can't make it fit, just give the last version >> >> Finally, this seems to have fallen off the end: >> A simple, uniform and powerful model >> Pharo has a simple dynamically-typed object model: >> >> Perhaps shrink the picture of the browser. You can save three lines by writing >> OrderedCollection new >> add: 1; >> add: 2; >> add: 3. >> >> as OrderedCollection new add: 1; add: 2; add: 3. >> And another by writing 2=2 ifTrue: [ Error signal: âHelpâ ]. on one line. >> >> HTH >> >> On Fri, Apr 8, 2016 at 12:56 PM, stepharo <stepharo(a)free.fr> wrote: >> new cheatsheet for Pharo syntax. >> Any feedback is welcome >> >> Stef >> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot > >

March 8, 2018

Re: [Pharo-dev] [Pharo-users] Bootstrap how to

by Alistair Grant

Hi Hilaire, Moving this to pharo-dev... On Thu, Mar 08, 2018 at 11:34:55AM +0100, Hilaire wrote: > I give again a try to bootstrap (after my last summer fail). Here how far I > went: > > Do people really like git or pretend to because > everyone is using it. Maybe there's a better source management system out there, but for me git is much better than any of the alternatives I've used (rcs, svn, vcs and a couple I've forgotten (cms?)). > 1. Fetched the repo https://github.com/pharo-project/pharo. I have to fetch > a fresh one as updating my repo failed with the git command > pull/fetch/merge/reset hard does not work. Incredible how simple thinks does > not work simply with git. I consider myself far from a git expert, so take the following with a grain of salt... You haven't given much detail, but when you have a clone think of the branches that are upstream as being "read only" (typically master and development). They should only ever be modified by merging in the branch from upstream. If you're writing (committing) to your clone, it should always be in a separate branch. When updating, e.g. master, from upstream, get in to the habit of enforcing fast-foward only e.g.: git checkout master git fetch --prune upstream git merge --ff-only upstream/master git push It's more steps, but will ensure you don't get in to the problem you describe above. git pull will do a merge if necessary, making future updates hard / impossible. > 2. Followed instructions to build a bootstrap. > > BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 sh ./bootstrap/scripts/bootstrap.sh The script I've been using is: #!/bin/bash export JOB=bootstrap export BOOTSTRAP_ARCH=32 export PHARO_VERSION=60 export BUILD_NUMBER=$(date "+%m%d") ./bootstrap/scripts/bootstrap.sh It would be good to have a readme in the bootstrap directory that provides basic instructions on what the key variables are and how to run the bootstrap. > The resulting image bootstrap-cache/bootstrap.image is built after 1 or 2 > hours. Its size is 3,4MB, when started there is only blank screen, I guess > it is the expected outcome. My 4 year old Dell XPS-13 (i7) takes about 30-40 minutes to do the build. > 3. Followed instructions to load pharo environment: > > ??BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 ./bootstrap/scripts/build.sh This is called by bootstrap.sh, so it shouldn't be necessary for you to call it directly. > Several attempts were needed and the build.sh script is fragile and fail > when at the repeated attempts, some cleaning were needed. > > I suggest two things : > > 1. you add -p to your mkdir commands (in build.sh and get-vm.sh > scripts) as it make your script less fragile ! > 2. Also checking for the existence of the Pharo.source will avoid to > have duplicted uncessary downloaded source file version. > (Pharo.source1, Pharo.source2): > > if test ! -e PharoV60.sources > ???? then > ???????????? wget http://files.pharo.org/sources/PharoV60.sources > fi > > Now the image is building, will see next. I agree that it would be nice if it was possible to avoid downloading the files each time, and also possible separate the process in to a number of stages, and restart from a nominated stage. Maybe the stages could be: 1. Download all requirements (stable vm (6.0), target vm (7.0), bootstrapImage.zip and anything else I've forgotten). 2. The build steps in bootstrap.sh. 3. The build steps in build.sh There could be a "clean" option that would be called as part of the CI process to ensure that everything is always up to date. Esteban and co.: How open are you to refactoring the scripts to support this? Or is there something I don't understand that means it doesn't make sense? Cheers, Alistair

March 8, 2018

Re: [Pharo-dev] new pharo cheatsheet

by Sven Van Caekenberghe

> On 8 Mar 2018, at 17:58, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Stef, > > following on from Sean, (+1000 for using ordinary quotes) > > âstringâ collection of characters => âstringâ sequence of characters > $a, Character space Two ways to create characters => $a, Character space two ways to denote characters (or two ways to write characters; all other explanations in this list are not capitalized; this shouldn't be either) > exp1. exp2 expression separator => expr1. expr2 statement separator > ; message cascade => expr doThis ; doThat semicolon - message cascade (c.f. exp1. exp2 expression separator) > ^ expr caret - returns a result from a method => ^ expr caret - return a result from a method (or, ParcPlace preference, answer a result from a method, since we're sending messages here) > > ... > A unary message is one with no arguments. => A unary message has no arguments. (c.f. A binary message takes only one argument ...) > ... > Set new add: 4; add: 4 ; yourself ~> aSet => Set new add: 4; add: 4 ; yourself ~> aSet(4) > Dictionary new at: #a put: 'Alpha' ; yourself a Dictionary => Dictionary new at: #a put: 'Alpha' ; yourself a Dictionary(#a->'Alpha' ) > > and then in the Files and Stream section I would give two more examples of exactly the same sequence that use the convenience APIs. This is the existing text: > > work := FileSystem disk workingDirectory. > stream := (work / âfoo.txtâ) writeStream. > stream nextPutAll: âHello Worldâ. > stream close. > stream := (work / âfoo.txtâ) readStream. > stream contents. ~> 'Hello World' > stream close. > > I would make it read > > work := FileSystem disk workingDirectory. > stream := (work / âfoo.txtâ) writeStream. > stream nextPutAll: âHello Worldâ. > stream close. > stream := (work / âfoo.txtâ) readStream. > stream contents. ~> 'Hello World' > stream close. > > or, more simply > > work := FileSystem disk workingDirectory. > (work / âfoo.txtâ) writeStreamDo: [ :fileStream | fileStream nextPutAll: âHello Worldâ ]. > (work / âfoo.txtâ) readStreamDo: [ :fileStream | fileStream contents] ~> 'Hello World' > > or, more simply still > > work := FileSystem disk workingDirectory. > (work / âfoo.txtâ) writeStreamDo: [ :fileStream | fileStream nextPutAll: âHello Worldâ ]. > (work / âfoo.txtâ) contents ~> 'Hello World' file := FileSystem disk workingDirectory / 'foo' , 'txt'. file ensureDelete. file writeStreamDo: [ :fileStream | fileStream nextPutAll: 'Hello World' ]. file contents. file delete. (to make it re-entrant and a bit more concise) +1e10 for plain single quotes, VERY important. > or if you can't make it fit, just give the last version > > Finally, this seems to have fallen off the end: > A simple, uniform and powerful model > Pharo has a simple dynamically-typed object model: > > Perhaps shrink the picture of the browser. You can save three lines by writing > OrderedCollection new > add: 1; > add: 2; > add: 3. > > as OrderedCollection new add: 1; add: 2; add: 3. > And another by writing 2=2 ifTrue: [ Error signal: âHelpâ ]. on one line. > > HTH > > On Fri, Apr 8, 2016 at 12:56 PM, stepharo <stepharo(a)free.fr> wrote: > new cheatsheet for Pharo syntax. > Any feedback is welcome > > Stef > > > > -- > _,,,^..^,,,_ > best, Eliot

March 8, 2018

Re: [Pharo-dev] new pharo cheatsheet

by Eliot Miranda

Hi Stef, following on from Sean, (+1000 for using ordinary quotes) âstringâ collection of characters => âstringâ sequence of characters $a, Character space Two ways to create characters => $a, Character space two ways to denote characters (or two ways to write characters; all other explanations in this list are not capitalized; this shouldn't be either) exp1. exp2 expression separator => expr1. expr2 statement separator ; message cascade => expr doThis ; doThat semicolon - message cascade (c.f. exp1. exp2 expression separator) ^ expr caret - returns a result from a method => ^ expr caret - return a result from a method (or, ParcPlace preference, answer a result from a method, since we're sending messages here) ... A unary message is one with no arguments. => A unary message has no arguments. (c.f. A binary message takes only one argument ...) ... Set new add: 4; add: 4 ; yourself ~> aSet => Set new add: 4; add: 4 ; yourself ~> aSet(4) Dictionary new at: #a put: 'Alpha' ; yourself a Dictionary => Dictionary new at: #a put: 'Alpha' ; yourself a Dictionary(#a->'Alpha' ) and then in the Files and Stream section I would give two more examples of exactly the same sequence that use the convenience APIs. This is the existing text: work := FileSystem disk workingDirectory. stream := (work / âfoo.txtâ) writeStream. stream nextPutAll: âHello Worldâ. stream close. stream := (work / âfoo.txtâ) readStream. stream contents. ~> 'Hello World' stream close. I would make it read work := FileSystem disk workingDirectory. stream := (work / âfoo.txtâ) writeStream. stream nextPutAll: âHello Worldâ. stream close. stream := (work / âfoo.txtâ) readStream. stream contents. ~> 'Hello World' stream close. or, more simply work := FileSystem disk workingDirectory. (work / âfoo.txtâ) writeStreamDo: [ :fileStream | fileStream nextPutAll: âHello Worldâ ]. (work / âfoo.txtâ) readStreamDo: [ :fileStream | fileStream contents] ~> 'Hello World' or, more simply still work := FileSystem disk workingDirectory. (work / âfoo.txtâ) writeStreamDo: [ :fileStream | fileStream nextPutAll: âHello Worldâ ]. (work / âfoo.txtâ) contents ~> 'Hello World' or if you can't make it fit, just give the last version Finally, this seems to have fallen off the end: A simple, uniform and powerful model Pharo has a simple dynamically-typed object model: Perhaps shrink the picture of the browser. You can save three lines by writing OrderedCollection new add: 1; add: 2; add: 3. as OrderedCollection new add: 1; add: 2; add: 3. And another by writing 2=2 ifTrue: [ Error signal: âHelpâ ]. on one line. HTH On Fri, Apr 8, 2016 at 12:56 PM, stepharo <stepharo(a)free.fr> wrote: > new cheatsheet for Pharo syntax. > Any feedback is welcome > > Stef > -- _,,,^..^,,,_ best, Eliot

March 8, 2018

[Pharo 7.0-dev] Build #668: 21513-Slots-should-distinguish-between-slot-owner-and-defining-class-

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #668 was: SUCCESS. The Pull Request #1041 was integrated: "21513-Slots-should-distinguish-between-slot-owner-and-defining-class-" Pull request url: https://github.com/pharo-project/pharo/pull/1041 Issue Url: https://pharo.fogbugz.com/f/cases/21513 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 8, 2018

Re: [Pharo-dev] new pharo cheatsheet

by Sean P. DeNigris

stepharo wrote > new cheatsheet for Pharo syntax. > Any feedback is welcome Looks great! (and surprise, it covers much more than just syntax). A few observations: 1. The code examples have smart quotes. This can create confusion. If it's not too much trouble, copy/pasteable-into-Pharo single quotes would be better. 2. Under "Pharo: a Live Programming Environment" ends with "â¦ program is executing. All". I guess that sentence is continued on the other side? If so, it might be clearer to end with (over) and move the All to the other side with the rest of the sentence. 3. The following example reminded me of the joy of Pharo's uniformity and expressivity vs. e.g. Java or C++ - #1:`d.put("1", "Chocolate");` vs. #2: `d at: '1' put: 'Chocolate'`. Experience of #1 - what was the order of the parameters? Do I need a dot or arrow? [but then I get to sit back and feel superior that I am one of the few "gurus" to have mastered an incomprehensible system] vs. Experience of #2 - "hey, d. please at 1 put Chocolate. Thanks" 4. Maybe too much detail, but where it says: "Counter >> initialize is a notation to indicate that the following text is the content of the method initialize in the class Counter." I personally find it pretty cool that adding $# i.e. `Counter >> #initialize` makes it executable code, especially now that we have GT tools which will open up a handful of domain views on the method! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 8, 2018