- Pharo-users - lists.pharo.org

QCMagritte question- does it have undo?

by PAUL DEBRUICKER

I've never used magritte or QC magritte and was wondering whether with the momento it qas also possible to get multi step undo cheaply if it didn't already exist. Thanks Paul

Nov. 11, 2016

Re: [Pharo-users] Little challenges for a friday evening

by Ben Coman

First I've heard of an isogram. Wikipedia [1] is ambiguous. Are you considering only single occurrence of letters, or also equal occurrence of letters. I like Sven's answer best, but just as an exercise I thought of an alternative. String>>#isIsogram | letters | letters := Dictionary new. self do: [ :x | letters at: x ifAbsent: [] ifPresent: [ ^false ]. On Fri, Nov 11, 2016 at 6:19 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > you're right, should probably be case insensitive. Or maybe that is overly restrictive. A case sensitive #isogram would have the flexibility to used both ways... 'Pharop' isogram 'Pharop' asLowercase isogram Now a philosophical question (not that its practical to change anything), but intuitively I tried using #lowercase before searching and finding #asLowercase, so I am wondering... I feel #asXXX methods are there to change the 'type' of an object, while #asLowercase isn't changing the type, but returning a transformation much like... 'Pharop' sorted We don't say 'Pharop' asSorted cheers -ben > >> On 10 Nov 2016, at 23:14, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >> >> Le 10/11/2016 Ã 23:09, Sven Van Caekenberghe a Ã©crit : >>> [ :string | string size = string asSet size ] value: 'Pharo'. >>> >>>>>> true >>> >>> [ :string | string size = string asSet size ] value: 'Pharoo'. >>> >>>>>> false >>> >>> String>>#isIsogram >>> ^ self size = self asSet size >>> >>> ? >>> >> >> 'Pharop' size = 'Pharop' asSet size >> >>>>> true >> >> Does it count? If upper-case counts you will need to do `^ self size = >> self asLowercase asSet size` :)

Nov. 11, 2016

Re: [Pharo-users] Little challenges for a friday evening

by Henrik Nergaard

String>>isIsogram 1 to: self size -1 do: [ :ix | (self findString: (self at: ix) asString startingAt: ix +1 caseSensitive: false ) ~~ 0 ifTrue: [ ^ false ] ]. ^ true -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Sven Van Caekenberghe Sent: Thursday, November 10, 2016 11:10 PM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] Little challenges for a friday evening [ :string | string size = string asSet size ] value: 'Pharo'. >>> true [ :string | string size = string asSet size ] value: 'Pharoo'. >>> false String>>#isIsogram ^ self size = self asSet size ? > On 10 Nov 2016, at 22:19, stepharo <stepharo(a)free.fr> wrote: > > Hi > > I'm checking how I would implement an isogram checker > > 'Pharo' isogram > > >>> true > > because it contains only single letter. > > I got a stupid bag drivent implementation but I will do another better and faster. > > Stef > > PS: after I will do anagram and pangram to have the family of gram checks (this is for a book). > >

Nov. 11, 2016

Re: [Pharo-users] [ALERT] Pharo by Example version 5 is about to be released

by Nicolai Hess

2016-10-27 13:32 GMT+02:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > In case someone missed it I will be doing a release for version 5 (pharo > version = pbe version) this weekend , since we had Pharo 7 initiated few > days ago. > > Essentially that means that the repo will be tagged for version 5, which > means a git commit is associated as a last commit for that version and > there will be a frozen release - download for Pharo by Example version 5. > After that we move to Pharo By Example version 6 or PBE6 for short > > The repo wont change otherwise and the process of submitting commits, pull > requests and issues remains the same. > > If you have found a flaw of any sort in the documentation , please open an > issue in the github issue tracker that can be found here > > https://github.com/SquareBracketAssociates/UpdatedPharoByExample/issues > > I will try to fix any problem reported but if I cannot , the fix will have > to move to version 6 > > As always thanks to all people contributing into the impossible .... > making Pharo more amazing > > If you want to contribute feel free to do so with a pull request. > > Does not matter if you are beginner because even minor corrections like > correcting mistakes in the grammar or content of the text, updated > pictures, or just a few lines of extra info are more than enough and more > than welcomed. Many Pharo beginners have already done so . > > -Salute to fellow Guardians of The Light > Morphic-Chapter: https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/183 use the class definition with package instead of category we used different method declaration, just the method name, class>>#method or class>>>method in the FirstApplication chapter, we noted the class >> method syntax and told we will use this in the book, so I adopted this scheme. remove note about PopUpMenu and FillInTheBlankMorphs, because they aren't in the image anymore. checked the code, all examples in this chapter are working.

Nov. 10, 2016

Re: [Pharo-users] Little challenges for a friday evening

by Sven Van Caekenberghe

you're right, should probably be case insensitive. > On 10 Nov 2016, at 23:14, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Le 10/11/2016 Ã 23:09, Sven Van Caekenberghe a Ã©crit : >> [ :string | string size = string asSet size ] value: 'Pharo'. >> >>>>> true >> >> [ :string | string size = string asSet size ] value: 'Pharoo'. >> >>>>> false >> >> String>>#isIsogram >> ^ self size = self asSet size >> >> ? >> > > 'Pharop' size = 'Pharop' asSet size > >>>> true > > Does it count? If upper-case counts you will need to do `^ self size = > self asLowercase asSet size` :) > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France

Nov. 10, 2016

Re: [Pharo-users] Little challenges for a friday evening

by Cyril Ferlicot D.

Le 10/11/2016 Ã 23:09, Sven Van Caekenberghe a Ã©crit : > [ :string | string size = string asSet size ] value: 'Pharo'. > >>>> true > > [ :string | string size = string asSet size ] value: 'Pharoo'. > >>>> false > > String>>#isIsogram > ^ self size = self asSet size > > ? > 'Pharop' size = 'Pharop' asSet size >>> true Does it count? If upper-case counts you will need to do `^ self size = self asLowercase asSet size` :) -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Nov. 10, 2016

Re: [Pharo-users] Little challenges for a friday evening

by Sven Van Caekenberghe

[ :string | string size = string asSet size ] value: 'Pharo'. >>> true [ :string | string size = string asSet size ] value: 'Pharoo'. >>> false String>>#isIsogram ^ self size = self asSet size ? > On 10 Nov 2016, at 22:19, stepharo <stepharo(a)free.fr> wrote: > > Hi > > I'm checking how I would implement an isogram checker > > 'Pharo' isogram > > >>> true > > because it contains only single letter. > > I got a stupid bag drivent implementation but I will do another better and faster. > > Stef > > PS: after I will do anagram and pangram to have the family of gram checks (this is for a book). > >

Nov. 10, 2016

Re: [Pharo-users] connecting to remote pharo 5 image on server.

by itayy

thx :D will do it once there is a fix or a workaround for the image saved on windows cant run on linux in pharo5 :/ -- View this message in context: http://forum.world.st/connecting-to-remote-pharo-5-image-on-server-tp492237… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 10, 2016

Re: [Pharo-users] Image freezes on Linux if it was previously saved on Windows

by itayy

having the same issue with pharo5 stable (saving in windows break pharo once i load it on linux), anyone know if if there will be a fix to pharo5 soon? -- View this message in context: http://forum.world.st/Image-freezes-on-Linux-if-it-was-previously-saved-on-… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 10, 2016

Pier3 with latest Pillar?

by Peter H. Meadows

What needs to be done to get Pier3 to use the latest Pillar code? I think I've got it partly working with a few small changes. (an isEmbedded method was missing, and PRFigure needed some changes). Relevant slack discussion below. Peter Meadows [6:45 AM] I was trying to run Pier3 Max Leske [6:45 AM] I assume that didnât work as you had expected :slightly_smiling_face: Peter Meadows [6:45 AM] It half works [6:46] I can read pier pages but not edit them Max Leske [6:47 AM] Do you see a debugger? Peter Meadows [6:47 AM] when? Max Leske [6:48 AM] When you try to edit a page. Or does it just silently refuse to work? Peter Meadows [6:49 AM] it's silent Max Leske [6:49 AM] Hm. [6:50] Did you load Pier3 through the catalog as well? Peter Meadows [6:51 AM] but i had to change some things, and i might not have done it in the best way. Because the newest pillar seems to make PRFigures when it should used to make PRLinks .. or something. I don't really understand it. [6:52] no. custom [6:52] the catalog uses an old version of pillar [6:52] i think [6:55] I had to change PRDocumentParser to PRPillarParser Peter Meadows [7:00 AM] and why does Magritte need seaside? I thought they made it completely independent? Max Leske [7:02 AM] It doesnât. As far as I can tell, the problem is somewhere between Pier and Seaside. [7:03] When I try to load Pier I get exactly the same error as you but I can load Seaside3 by itself without problems. This may possibly be a Metacello bug. [7:05] Concerning pillar, you probably best ask Cyril Ferlicot. And for trouble with Seaside / Pier itâs best to ask on the seaside mailing list Peter Meadows [7:08 AM] ahh. well that might explain why it has been confusing/confounding me! Peter Meadows [7:20 AM] does Metacello not have a very verbose setting? Stephan Eggermont [7:48 AM] @anteater: Pillar forked from Pier and did not maintain compatibility. I have not updated configurations for Pharo 6. Magritte and Seaside are independent. Load the right metacello group to get a combination. Stephan Eggermont [7:54 AM] @anteater: just load Pier3 from the catalog and check the package cache to see if what is loaded is what you expect. Without pharo6 tags, very old stuff gets loaded Peter Meadows [7:56 AM] Yes, but I wanted my Pier to use the latest pillar code. Surely that was always the plan? It hasn't changed dramatically i think? [7:57] If it was actually a fork they would/should have changed the name! Stephan Eggermont [12:43 PM] @anteater it is definitely a fork with lots of breaking changes. No compatibility [12:46] Pillar broke compatibility on purpose and had zero interest in keeping things working [12:50] ConfigurationOfMagritte3 load loads a default group, which is often not what you want Cyril Ferlicot [12:54 PM] Is there a lot to change in Pillar/Pier to keep compatibility? Pierce Ng [2:01 PM] @cyrilferlicot the Pillar part of Pier has been taken out of Pier and made standalone, so Pier has to be updated to use Pillar. i looked at this a while back so maybe Pier has been kept updated. Stephan Eggermont [2:49 PM] @cyrilferlicot: flatten traits. Pier is cross-dialect. The other things were easy, just breaking the build once a month Cyril Ferlicot [2:51 PM] Maybe when Pillar will move to github we will be able to do a Pharo branch with trait and a flattened branch for cross dialects. [2:52] I think I broke a lot of compatibility during my internship but that was not because I did not wanted to keep compatibility but more because I did not knew the relation between Pillar and Pier. That was the first time I contributed to a real project :slightly_smiling_face: Stephan Eggermont [2:52 PM] Should not be difficult. It just asks for some attention to downstream consequences Dimitris Chloupis [2:53 PM] you are not the only one [2:54] even in the PBE we had half the files in pier extension and half with pillar extension Stephan Eggermont [3:06 PM] @cyrilferlicot: I didn't assume you intended to break things. Pierce Ng [4:07 PM] my blog has switched to pillar. before it was shelling out to the markdown executable called discount. so now the blog has one fewer dependency. thank you for the standalone pillar.

Nov. 10, 2016