Re: [Pharo-users] Interleaving strings

2016-03-21 17:43 GMT-03:00 Nicolai Hess : > What is your implementation with with:collection: ? > > I know this function from python, they call it "zip" > > we could implement this in SequenceableCollection > > SequenceableCollection>>zip: aCollection > | index | > index := 0. > self

Re: [Pharo-users] Interleaving strings

What is your implementation with with:collection: ? I know this function from python, they call it "zip" we could implement this in SequenceableCollection SequenceableCollection>>zip: aCollection | index | index := 0. self size > aCollection size ifTrue:[ ^ aCollection zip: self].

Re: [Pharo-users] Pharo launcher in homebrew cask

Great ! Thank you Filip On Mon, Mar 21, 2016 at 9:09 PM, Filip Krikava wrote: > Hi, > > I find Pharo launcher incredibly useful and I was surprised not to find it > in homebrew cask [1]. Pharo itself is there. I have therefore created a PR: > https://github.com/caskroom/homebrew-cask/pull/19956 >

[Pharo-users] Pharo launcher in homebrew cask

Hi, I find Pharo launcher incredibly useful and I was surprised not to find it in homebrew cask [1]. Pharo itself is there. I have therefore created a PR: https://github.com/caskroom/homebrew-cask/pull/19956 /cheers Filip [1] https://github.com/caskroom/homebrew-cask

[Pharo-users] [ANN] GNU Dr. Geo 16.03

I am please to announce[1] release 16.03 of Dr. Geo, ready to download[2]. Main changes are (details in the change log[3]): - Bugs fix, mainly in the Smalltalk programming interface and related - New features - New translations "Dr. Geo, a software to design & manipulate interactive geometric ske

Re: [Pharo-users] FLMethodChanged: Materialization error. Method DmQuartalsplan>>#initialize: changed its bytecodes.

On Mon, Mar 21, 2016 at 3:51 PM, Johannes Brauer wrote: > > Am 21.03.2016 um 19:19 schrieb Mariano Martinez Peck < > marianop...@gmail.com>: > > HI Johannes, > > Could I see the source of the DmQuartalsplan>>#initialize: ? > > yes, of course: > 'From Pharo4.0 of 18 March 2013 [Latest update: #40

Re: [Pharo-users] FLMethodChanged: Materialization error. Method DmQuartalsplan>>#initialize: changed its bytecodes.

Am 21.03.2016 um 19:19 schrieb Mariano Martinez Peck mailto:marianop...@gmail.com>>: HI Johannes, Could I see the source of the DmQuartalsplan>>#initialize: ? yes, of course: 'From Pharo4.0 of 18 March 2013 [Latest update: #40626] on 21 March 2016 at 6:19:38.568095 pm'! !DmQuartalsplan metho

Re: [Pharo-users] FLMethodChanged: Materialization error. Method DmQuartalsplan>>#initialize: changed its bytecodes.

HI Johannes, Could I see the source of the DmQuartalsplan>>#initialize: ? I think I workaround may be to do a Fuel replacement to replace the sortedCollection with an OrderedCollection and then a post initialize method. But again, probably seeing if the closure of the sorted collection is clean

[Pharo-users] FLMethodChanged: Materialization error. Method DmQuartalsplan>>#initialize: changed its bytecodes.

Hi, I am trying to port a pharo2 application to pharo4. Therefore I have to migrate some fuel files from version 1.9 to 1.9.4. I've done this using the script shown in the EnterprisePharo Book in my pharo2 image, no problem. But trying to load the migrated fuel file into my pharo4 image I get th

Re: [Pharo-users] BaselineOf's and Loose Dependencies

Dale Henrichs-3 wrote > First, congratulations! Thanks!! Dale Henrichs-3 wrote > A baseline is associated with a "git version", so there is no need to > "pin the version down in a specific version" Yes, but I'm not talking about a version of my main project, but a version of a dependent projec

Re: [Pharo-users] BaselineOf's and Loose Dependencies

Sean (and others) I don't always keep up-to-date with the posts on the pharo list, so if you have a Metacello-related question, put Metacello in the subject line and I'll have a better chance of seeing the message ... Dale On 3/21/16 8:15 AM, Sean P. DeNigris wrote: I know this is not technic

Re: [Pharo-users] BaselineOf's and Loose Dependencies

First, congratulations! A baseline is associated with a "git version", so there is no need to "pin the version down in a specific version" ... in a "git project" you have the option of changing the specific version associated with a baseline on "every commit" So you would specify the Ba

[Pharo-users] BaselineOf's and Loose Dependencies

I know this is not technically a Pharo question, but I'm in China on my honeymoon and can't access the Metacello Google group! There was a pattern in pre-BaselineOf Metacello where one would define dependencies loosely in the #baselineXyz:, and then pin them to a specific version in the #versionAb

Re: [Pharo-users] [Pillar] Logo for Pillar

I don't like it. It's more an illustration than an actual iso/logotype. Sorry. I didn't know there was a logo for Pillar, and though it's not fantastic, it is nice and continues with the style of a Pharo thing. Regards! Esteban A. Maringolo 2016-03-21 11:05 GMT-03:00 Thibault ARLOING : > oh I

Re: [Pharo-users] [Pharo-dev] DeprecationAssistant

Oh, that’s an interesting use case. It’s not easy no make predictions further in stack so by default it is assumed that the change should happen in the method that has called the deprecated one. In fact usually this should help with the method deprecation, and in the particular case we are deali

Re: [Pharo-users] [Pillar] Logo for Pillar

oh I didn't see either that pillar had a logo. Moreover, he is better. thanks De : Pharo-users de la part de Damien Cassou Envoyé : lundi 21 mars 2016 14:19 À : Yuriy Tymchuk; Any question about pharo is welcome Objet : Re: [Pharo-users] [Pillar] Logo f

Re: [Pharo-users] [Pharo-dev] DeprecationAssistant

Ah okay! But how does the system resolve it ? I mean, the class RTLabelled does not refer to RTLabeled. So, what is the magic behind your tool? I found an interesting situation. Look at this: Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu

Re: [Pharo-users] [Pillar] Logo for Pillar

Yuriy Tymchuk writes: > IMHO it’s too airy, to much free area. By the way, have you seen the previous > logo? > https://github.com/pillar-markup I didn't know Pillar already had a logo :-). Thanks -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one f

Re: [Pharo-users] [Pharo-dev] DeprecationAssistant

Hi Alex, this is not about critics… If you have a method like labeledObject ^ RTLabelled new in the latest roassal image and you will execute it, you will get a debugger deprecation warning with an option to fix that. Cheers. Uko > On 21 Mar 2016, at 14:07, Alexandre Bergel wrote:

Re: [Pharo-users] Seaside 3.1 and 3.2 in Pharo 5

Thanks Johan! Le 20/03/2016 19:49, Johan Brichau a écrit : > If you are looking to use Seaside in Pharo 5, please go ahead and let us > know if you run into any issues. > Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are > green [1]. > -- Dr. Geo http://drgeo.eu

Re: [Pharo-users] DeprecationAssistant

Hi! I cannot figure out what I should expect after loading DeprecationAssistant. I have loaded it and created a method: -=-=-=-=-=-=-=-=-= foo self deprecated: 'use bar instead’ -=-=-=-=-=-=-=-=-= Is there anything that should be displayed in the critic list? Alexandre -- _,.;:~^~:;._,

Re: [Pharo-users] [Pillar] Logo for Pillar

Hi, IMHO it’s too airy, to much free area. By the way, have you seen the previous logo? https://github.com/pillar-markup Uko > On 18 Mar 2016, at 15:30, Thibault ARLOING > wrote: > > Hi, > > With a mate, we've worked on a logo for Pillar. > We just want feedbacks on it. > > You can fin th

[Pharo-users] DeprecationAssistant

HI everyone, last week I’ve created a little tool that automates deprecation resolution. The goal is to provide a help based on the existing code (no need for extra actions). You can read more here: http://blog.yuriy.tymch.uk/2016/03/deprecationassistant-aiding-developers.html