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

Test skip isn't working?

by Vitor Medina Cruz

Hello, someTest self skip: 'some message'. rest of the test Rest of the test is being executed. There is a different woy of skipping tests? Thanks, Vitor.

March 17, 2019

Re: [Pharo-users] [Moose-dev] Re: [ANN] Lan.d.s Alpha: All Along the Language Tower

by Nick Papoylias

On Sun, Mar 17, 2019 at 2:18 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi nick > > I wanted to support your chapters via paypal but it asked me about my visa > and I would like > to pay via my paypal account. Do you know if this is possible? > Thanx Stef ! *Through patreon, this seems to be required for recurrent payments:* https://support.patreon.com/hc/en-us/articles/115001917686-Why-do-I-need-to… There are 2 alternatives through that might not have this requirement: *Alternative 1, through the Paypal button (if you did not try already):* *Step1,* from: https://npapoylias.gitlab.io/lands-project/Support/ Hit the PayPal button. *Step2*: And then in the Paypal screen, hit PayPal pay. *Alternative 2, directly from your PayPal dashboard:* "*Pay for goods or services* No fee for you. The recipient pays a fee." *using my e-mail address:* npapoylias(a)gmail.com <npapoylias(a)gmail.com> Adding in the note a message like: "Lands Support" so that it is distinguishable form other transactions. *Let me know if you encounter any problems, so that I contact them, if necessary.* And update the site, for ways to support without credit-card required. Best, Nick Else can you send me your pp account? > > Stef > > On 17 Mar 2019, at 10:21, Nick Papoylias <npapoylias(a)gmail.com> wrote: > > *Dear friends ! * > > I am quite excited to announce the availability of an alpha version > of my latest work around *Parsing and Programming Languages *at: > > https://npapoylias.gitlab.io/lands-project/ > > Accompanied by *~ 30 min of transcribed eye-candy:* > > https://www.youtube.com/playlist?list=PLIjPQnRzAKVHABG1-oTvwWc3Gj1Z4C91B > > Backed by* a crowdfunding campaign ! *To get the *book and stable release > * > successfully out of the door: > > https://www.patreon.com/lands_project > https://npapoylias.gitlab.io/lands-project/Support/ > > *Click, download, watch, enjoy !* If you like what you see, support the > project ! Tiers > start *from 5 and 10 euros per chapter for individuals.* Companies > supporting > the project can get > *6 to 12 days of consultancy, on-site workshops and other perks.* > ================= > > *What is all about ??* > > *Lan.d.s is a new solution for language design.* From > *general purpose languages *like *Lise* (short for (list (embedding)) to > *Domain-Specific Languages using the MOODs framework*, and everything > else in between. > Lan.d.s is build around the formalism of > *Multi-Ordered Grammars, which are a possible alternative to CFGs and PEGs > in wider use today.* > > Multi-ordered grammars (or simply MOGs) aim for a better exploration of > ambiguity, > recursion, ordering and associativity during language design. They can be > *parsed using the Gray Algorithm. *After parsing in order to ease the > production of executable code > Lan.d.s introduces the *Abstract Syntax Language (ASL)*, which is an OO > solution for compile-time meta-programming. Finally in order to promote > language extension and re-use, Lan.d.s employs > *GrammarTraits, as units of composition for both MOG rules and ASL > actions.* > > ================= > > Some random highlights for the impatient: > > > ** Object subclass: #Prediction uses: Future syntax* > > ** Languages are everywhere, they are all around you, even now in this > very sentence.* > > ** Study SICP with a Xerox flavor, while re-inventing some Bell-labs > utilities.* > > ** TOC-Board, the TOC for your next talk ;)* > > > Enjoy ! > <Theory-and-Applications-Of-Multi-Ordered-Grammars.pdf> > <Lands-Alpha-All-Along-The-Language-Tower.png> > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > http://www.synectique.eu / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev >

March 17, 2019

Re: [Pharo-users] 7.0.2 and the font glitch - seems far worse than 7.0.1

by Tim Mackinnon

Hey Pierce - what font did you use - are you talking about the Bitmap fonts, or did you pick something else? This tip, also reveals a usability annoyance on that font setting panel - the Force All button not only copies the font to all the sub settings - but also the size (making it slightly less useful). Tim > On 17 Mar 2019, at 10:43, Tim Mackinnon <tim(a)testit.works> wrote: > > Ah - I didnât know about using ânative fontsâ - is that in settings? Iâll check it out. > > That said - if the image default is not to have that setting - we really need to understand and fix this as itâs mega confusing for new users when you donât see what you typed or code suddenly changes in front of you. > > So I will also eat the dog food and see if I can help diagnose this . > > Tim > > Sent from my iPhone > > > > Sent from my iPhone >>> On 17 Mar 2019, at 10:18, Pierce Ng <pierce(a)samadhiweb.com> wrote: >>> >>> On Fri, Mar 15, 2019 at 11:04:35PM +0000, Tim Mackinnon wrote: >>> In 7.0.1 (osx - high Sierra - launcher), I was seeing the odd font >>> glitch (where characters suddenly start glyphing in code and menus - >>> see photos) and it seemed to be fixable by saving your image the first >>> time (e.g. after 30+ mins you would see this in a new install). Once >>> the image was saved, this seemed to stick and never be a problem. >>> >>> In 7.0.2 this is now happening to me very 10-60 mins. The save fix >>> still works - the moment you save the glyphs will all just disappear >>> until it happens again. >> >> Worked on my Mojave Mac with fresh 7.0.2 images today. Saw the font >> glitch after a short while. I switched to native fonts and the glitch >> went away. I don't use Launcher. >> >> Pierce >> >> > >

March 17, 2019

Re: [Pharo-users] 7.0.2 and the font glitch - seems far worse than 7.0.1

by Tim Mackinnon

Ah - I didnât know about using ânative fontsâ - is that in settings? Iâll check it out. That said - if the image default is not to have that setting - we really need to understand and fix this as itâs mega confusing for new users when you donât see what you typed or code suddenly changes in front of you. So I will also eat the dog food and see if I can help diagnose this . Tim Sent from my iPhone Sent from my iPhone >> On 17 Mar 2019, at 10:18, Pierce Ng <pierce(a)samadhiweb.com> wrote: >> >> On Fri, Mar 15, 2019 at 11:04:35PM +0000, Tim Mackinnon wrote: >> In 7.0.1 (osx - high Sierra - launcher), I was seeing the odd font >> glitch (where characters suddenly start glyphing in code and menus - >> see photos) and it seemed to be fixable by saving your image the first >> time (e.g. after 30+ mins you would see this in a new install). Once >> the image was saved, this seemed to stick and never be a problem. >> >> In 7.0.2 this is now happening to me very 10-60 mins. The save fix >> still works - the moment you save the glyphs will all just disappear >> until it happens again. > > Worked on my Mojave Mac with fresh 7.0.2 images today. Saw the font > glitch after a short while. I switched to native fonts and the glitch > went away. I don't use Launcher. > > Pierce > >

March 17, 2019

Re: [Pharo-users] 7.0.2 and the font glitch - seems far worse than 7.0.1

by Pierce Ng

On Fri, Mar 15, 2019 at 11:04:35PM +0000, Tim Mackinnon wrote: > In 7.0.1 (osx - high Sierra - launcher), I was seeing the odd font > glitch (where characters suddenly start glyphing in code and menus - > see photos) and it seemed to be fixable by saving your image the first > time (e.g. after 30+ mins you would see this in a new install). Once > the image was saved, this seemed to stick and never be a problem. > > In 7.0.2 this is now happening to me very 10-60 mins. The save fix > still works - the moment you save the glyphs will all just disappear > until it happens again. Worked on my Mojave Mac with fresh 7.0.2 images today. Saw the font glitch after a short while. I switched to native fonts and the glitch went away. I don't use Launcher. Pierce

March 17, 2019

Re: [Pharo-users] Why doesn't collection have #excludes (the mirror of includes)?

by Sven Van Caekenberghe

> On 17 Mar 2019, at 07:56, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > (1) As it happens, my Smalltalk library *does* have "my mystery Smalltalk" ;-) > #excludes: and #identityExcludes: > (2) The definitions are trivial. > excludes: item > ^(self includes: item) not > identityExcludes: item > ^(self identityIncludes: item) not > > If you want to execute aBlock when aString is not all zeros > and ones, just do > (aString allSatisfy: [:each | each = $0 or: [each = $1]]) > ifFalse: [aBlock value]. > or > (aString anySatisfy: [:each | each ~= $0 and: [each ~= $1]]) > ifTrue: [aBlock value]. > or > ('01' includesAll: aString) ifFalse: [aBlock value]. That last expression wins hands down ! Thank you for bringing that up, I learned something new. > On Sat, 16 Mar 2019 at 11:33, Tim Mackinnon <tim(a)testit.works> wrote: > Hi - in my quest to understand the edgier details of Pharo (and Smalltalk) - and driven by fresh thoughts of completing exercism exercises - I was surprised to find that there is no #excludes: operation on collection to mirror the #includes: operation? > > I was curious about this - its seems a strange omission? > > Of course I can inverse it with not, or do things a different way - but we have ifTrue: mirrored with ifFalse, empty/notEmpty so am I missing something? > > I wanted to write something like > > > aString detect: [:c | ($0 to: $1) excludes: c] ifFound: aBlock. (Evaluate a block if the string isnât all 0 and 1âs) > > > Of course I can write this as: > > (aString reject: [:c | c = $0 | c = $1)) ifNotEmpty: aBlock > > But as recent messages in this vein have shown me (and taught me lots - thanks to those answering), the answer is often not what I thought. > > Tim > >

March 17, 2019

[ANN] Lan.d.s Alpha: All Along the Language Tower

by Nick Papoylias

*Dear friends ! * I am quite excited to announce the availability of an alpha version of my latest work around *Parsing and Programming Languages *at: https://npapoylias.gitlab.io/lands-project/ Accompanied by *~ 30 min of transcribed eye-candy:* https://www.youtube.com/playlist?list=PLIjPQnRzAKVHABG1-oTvwWc3Gj1Z4C91B Backed by* a crowdfunding campaign ! *To get the *book and stable release * successfully out of the door: https://www.patreon.com/lands_project https://npapoylias.gitlab.io/lands-project/Support/ *Click, download, watch, enjoy !* If you like what you see, support the project ! Tiers start *from 5 and 10 euros per chapter for individuals.* Companies supporting the project can get *6 to 12 days of consultancy, on-site workshops and other perks.* ================= *What is all about ??* *Lan.d.s is a new solution for language design.* From *general purpose languages *like *Lise* (short for (list (embedding)) to *Domain-Specific Languages using the MOODs framework*, and everything else in between. Lan.d.s is build around the formalism of *Multi-Ordered Grammars, which are a possible alternative to CFGs and PEGs in wider use today.* Multi-ordered grammars (or simply MOGs) aim for a better exploration of ambiguity, recursion, ordering and associativity during language design. They can be *parsed using the Gray Algorithm. *After parsing in order to ease the production of executable code Lan.d.s introduces the *Abstract Syntax Language (ASL)*, which is an OO solution for compile-time meta-programming. Finally in order to promote language extension and re-use, Lan.d.s employs *GrammarTraits, as units of composition for both MOG rules and ASL actions.* ================= Some random highlights for the impatient: ** Object subclass: #Prediction uses: Future syntax* ** Languages are everywhere, they are all around you, even now in this very sentence.* ** Study SICP with a Xerox flavor, while re-inventing some Bell-labs utilities.* ** TOC-Board, the TOC for your next talk ;)* Enjoy !

March 17, 2019

Re: [Pharo-users] Why doesn't collection have #excludes (the mirror of includes)?

by Richard O'Keefe

(1) As it happens, my Smalltalk library *does* have #excludes: and #identityExcludes: (2) The definitions are trivial. excludes: item ^(self includes: item) not identityExcludes: item ^(self identityIncludes: item) not If you want to execute aBlock when aString is not all zeros and ones, just do (aString allSatisfy: [:each | each = $0 or: [each = $1]]) ifFalse: [aBlock value]. or (aString anySatisfy: [:each | each ~= $0 and: [each ~= $1]]) ifTrue: [aBlock value]. or ('01' includesAll: aString) ifFalse: [aBlock value]. On Sat, 16 Mar 2019 at 11:33, Tim Mackinnon <tim(a)testit.works> wrote: > Hi - in my quest to understand the edgier details of Pharo (and Smalltalk) > - and driven by fresh thoughts of completing exercism exercises - I was > surprised to find that there is no #excludes: operation on collection to > mirror the #includes: operation? > > I was curious about this - its seems a strange omission? > > Of course I can inverse it with not, or do things a different way - but we > have ifTrue: mirrored with ifFalse, empty/notEmpty so am I missing > something? > > I wanted to write something like > > > aString detect: [:c | ($0 to: $1) excludes: c] ifFound: aBlock. (Evaluate > a block if the string isnât all 0 and 1âs) > > > Of course I can write this as: > > (aString reject: [:c | c = $0 | c = $1)) ifNotEmpty: aBlock > > But as recent messages in this vein have shown me (and taught me lots - > thanks to those answering), the answer is often not what I thought. > > Tim > > >

March 17, 2019

Re: [Pharo-users] A strange iceberg/Monticello loading issue that has appeared in 7.0.2?

by Tim Mackinnon

Reported as https://github.com/pharo-project/pharo/issues/2854 <https://github.com/pharo-project/pharo/issues/2854> (although there was a similar issue already from P6, but I donât think it made it clear enough the seriousness of this problem). > On 16 Mar 2019, at 22:08, Tim Mackinnon <tim(a)testit.works> wrote: > > Hmmm - hang on a second, something very weird is going on - looking at how to track where files get written on OSX and using: > touch ~/timestamp > find -x / -newer ~/timestamp >~/changedfiles.txt > > The result is that when I do my zero conf install - my files now seem to be going to the 7.0.2 install that I did on Thursday, and not to the local directory where I am running. I think Is it possible that this new release has change something. > > - WTF? How can this happen? > > > /Users/macta/Dev/Smalltalk/Pharo/Pharo 7.0 - 64bit (7.0.2)/pharo-local/iceberg/exercism/pharo-smalltalk/.git > /Users/macta/Dev/Smalltalk/Pharo/Pharo 7.0 - 64bit (7.0.2)/pharo-local/iceberg/exercism/pharo-smalltalk/.git/refs/heads > /Users/macta/Dev/Smalltalk/Pharo/Pharo 7.0 - 64bit (7.0.2)/pharo-local/iceberg/exercism/pharo-smalltalk/.git/index > /Users/macta/Dev/Smalltalk/Pharo/Pharo 7.0 - 64bit (7.0.2)/pharo-local/iceberg/exercism/pharo-smalltalk/.git/FETCH_HEAD > /Users/macta/Dev/Exercism/pharo7e3 > /Users/macta/Dev/Exercism/pharo7e3/Pharo.changes > /Users/macta/Dev/Exercism/pharo7e3/pharo-local > /Users/macta/Dev/Exercism/pharo7e3/pharo-local/iceberg > /Users/macta/Dev/Exercism/pharo7e3/pharo-local/iceberg/credentials.fuel > /Users/macta/Dev/Exercism/pharo7e3/pharo-local/ombu-sessions > /Users/macta/Dev/Exercism/pharo7e3/pharo-local/ombu-sessions/Pharo7.0.2-0-32bit-890f474.c1wfkijoa7470az0raz1zczo0.ombu > /Users/macta/Dev/Exercism/pharo7e3/icon-packs > /Users/macta/Dev/Exercism/pharo7e3/icon-packs/idea11.zip > > Tim > >> On 16 Mar 2019, at 21:50, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> Hi Sean - thanks for chipping in: >> >> Yes - the correct packages are loading, the baseline is fine (and its a baseline Iâve been using without issues for a while) - its simply just not loading the same source as if I do a clone by hand via git in a separate directory? >> >> Itâs like iceberg just doesnât want to load the lates stuff and wants me to do a manual âpullâ in the image to catch up? >> >> Thinking that maybe my master branch was weird - I did a hard reset in a separate copy, and update the readme.md and committed that, and pushed it. >> >> Now when I go back to my pharo zero, conf - and clear out the iceberg directory, and run my command line/or playground script again - it now loads and says I need to pull 5 new commits (prior to this, it said 4 commits). >> >> The is what Iâm not understanding - why isnât it just pulling in all of those commits in a fresh load? Iâve never seen this before, and am at a loss why this is suddenly happening? >> >> If I open the settings, and check software config management - the share repoâs setting is unchecked. However - the weird thing is that I donât see anything in the pharo-local/iceberg directory (making me think that something must have got flipped - but Iâve not knowingly done anything in the few hours between when it last worked and suddenly stopped). >> >> Grrrrâ¦ just as I was starting to get the hang of things, its all fallen apart again. >> >> Tim >> >>> On 16 Mar 2019, at 17:34, Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: >>> >>> Tim Mackinnon wrote >>>> Can anyone think of what might cause this? Iâm really confused. >>> >>> Am I understanding correctly that your load script is loading the correct >>> packages, but not the latest versions? >>> >>> If so, just a few initial thoughts: >>> - What does the local clone look like after the load (i.e. does it show the >>> missing commit(s)? >>> - It is possible that shared repo location is enabled? >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> >>> >> >> >

March 17, 2019

Re: [Pharo-users] A strange iceberg/Monticello loading issue that has appeared in 7.0.2?

by Tim Mackinnon

ARRRGGGGGG - its the damn settings file! I recall now, I changed some of the code formatter settings in the 7.0.2, and was using the blue-ink preview in settings, and must have pressed save. Even thought, it was only formatter settings that I changed - the damn file causes iceberg to break (even though there is not reference to using a shared repo, and loading the settings in any of my images doesnât show this). What a hideous bugâ¦. I will report it, or try and raise its priority if its not reported as this is confusing as hell. Tim > On 16 Mar 2019, at 22:08, Tim Mackinnon <tim(a)testit.works> wrote: > > Hmmm - hang on a second, something very weird is going on - looking at how to track where files get written on OSX and using: > touch ~/timestamp > find -x / -newer ~/timestamp >~/changedfiles.txt > > The result is that when I do my zero conf install - my files now seem to be going to the 7.0.2 install that I did on Thursday, and not to the local directory where I am running. I think Is it possible that this new release has change something. > > - WTF? How can this happen? > > > /Users/macta/Dev/Smalltalk/Pharo/Pharo 7.0 - 64bit (7.0.2)/pharo-local/iceberg/exercism/pharo-smalltalk/.git > /Users/macta/Dev/Smalltalk/Pharo/Pharo 7.0 - 64bit (7.0.2)/pharo-local/iceberg/exercism/pharo-smalltalk/.git/refs/heads > /Users/macta/Dev/Smalltalk/Pharo/Pharo 7.0 - 64bit (7.0.2)/pharo-local/iceberg/exercism/pharo-smalltalk/.git/index > /Users/macta/Dev/Smalltalk/Pharo/Pharo 7.0 - 64bit (7.0.2)/pharo-local/iceberg/exercism/pharo-smalltalk/.git/FETCH_HEAD > /Users/macta/Dev/Exercism/pharo7e3 > /Users/macta/Dev/Exercism/pharo7e3/Pharo.changes > /Users/macta/Dev/Exercism/pharo7e3/pharo-local > /Users/macta/Dev/Exercism/pharo7e3/pharo-local/iceberg > /Users/macta/Dev/Exercism/pharo7e3/pharo-local/iceberg/credentials.fuel > /Users/macta/Dev/Exercism/pharo7e3/pharo-local/ombu-sessions > /Users/macta/Dev/Exercism/pharo7e3/pharo-local/ombu-sessions/Pharo7.0.2-0-32bit-890f474.c1wfkijoa7470az0raz1zczo0.ombu > /Users/macta/Dev/Exercism/pharo7e3/icon-packs > /Users/macta/Dev/Exercism/pharo7e3/icon-packs/idea11.zip > > Tim > >> On 16 Mar 2019, at 21:50, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> Hi Sean - thanks for chipping in: >> >> Yes - the correct packages are loading, the baseline is fine (and its a baseline Iâve been using without issues for a while) - its simply just not loading the same source as if I do a clone by hand via git in a separate directory? >> >> Itâs like iceberg just doesnât want to load the lates stuff and wants me to do a manual âpullâ in the image to catch up? >> >> Thinking that maybe my master branch was weird - I did a hard reset in a separate copy, and update the readme.md and committed that, and pushed it. >> >> Now when I go back to my pharo zero, conf - and clear out the iceberg directory, and run my command line/or playground script again - it now loads and says I need to pull 5 new commits (prior to this, it said 4 commits). >> >> The is what Iâm not understanding - why isnât it just pulling in all of those commits in a fresh load? Iâve never seen this before, and am at a loss why this is suddenly happening? >> >> If I open the settings, and check software config management - the share repoâs setting is unchecked. However - the weird thing is that I donât see anything in the pharo-local/iceberg directory (making me think that something must have got flipped - but Iâve not knowingly done anything in the few hours between when it last worked and suddenly stopped). >> >> Grrrrâ¦ just as I was starting to get the hang of things, its all fallen apart again. >> >> Tim >> >>> On 16 Mar 2019, at 17:34, Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: >>> >>> Tim Mackinnon wrote >>>> Can anyone think of what might cause this? Iâm really confused. >>> >>> Am I understanding correctly that your load script is loading the correct >>> packages, but not the latest versions? >>> >>> If so, just a few initial thoughts: >>> - What does the local clone look like after the load (i.e. does it show the >>> missing commit(s)? >>> - It is possible that shared repo location is enabled? >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> >>> >> >> >

March 17, 2019