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

Re: [Pharo-dev] UI Workflows Are Like Snowflakes

by Sean P. DeNigris

stepharo wrote > Could you stop crying because this is a bit boring? Could you address my policy suggestion instead of crying? ;) It would've taken the same amount of time to answer my message productively instead of lawyering it by pointing out the one example out of three that you could turn back around on me and ignoring everything else. stepharo wrote > So instead of crying help. I've participated in fixing hundreds of issues, and that's just on the new issue tracker. Is that a reasonable comment? ----- Cheers, Sean -- View this message in context: http://forum.world.st/UI-Workflows-Are-Like-Snowflakes-tp4814234p4814344.ht… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 23, 2015

Re: [Pharo-dev] Issue Validator Report - Service Temporarily Unavailable

by Ben Coman

thanks Christophe. On Mon, Mar 23, 2015 at 8:17 PM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > Jenkins was down. I just restarted it. > > Le 23 mars 2015 Ã 13:04, Ben Coman a Ã©crit : > > I went to review an issue validation report and got "Service Temporarily > Unavailable" > > > https://ci.inria.fr/pharo/job/Pharo-4.0-Issue-Validator/27809//artifact/val… > > cheers -ben > > >

March 23, 2015

Re: [Pharo-dev] QUESTION: Is anybody using zeroconf with Pharo 2.0?

by Esteban Lorenzano

wellâ¦ after sending this mail I stayed thinking and I think something like this is precisely what I have to do :) so I will do an important change to zeroconf to ensure newer versions do not screw with older ones. cheers, Esteban > On 23 Mar 2015, at 09:06, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 22 Mar 2015, at 22:56, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: >> >> Damien, >> >> I'm using zeroconf for Pharo 1.2, 1.4 and 2.0 ... I still test Metacello against Pharo1.1 ... I would use zeroconf with 1.3 but there is something funkily different between what is available on zeroconf for 1.3 and what actually "works" for for 1.3 (https://gforge.inria.fr/frs/download.php/30567/PharoCore-1.3-13328.zip) > > why? I do not think anyone is using Pharo < 2.0 (and not even 2.0, with the exception of some legacy apps) > this âforever backward compatibilityâ ends up being really complicated. > > I want to deprecate zeroconf for, at least, all pharo < 2.0. > > why? > because the scripts right now downloads one unique vm for all images. Which means download of sources V1, V2, V3â¦ and starting next month V4. > I want to remove at least one of those sources. > > Alsoâ¦ the upcoming spur VM will add another level of complexity to zeroconf scripts (because is everything goes smooth, Pharo5 will dispatch with spur, without backward compatibility). So it will be another V5 + the different VMâ¦ > > What to do with those scripts? > > maybe deprecate the âvmâ part, and replace it for: > > /vm1 > /vm2 > /vm3 > /vm4 > /vmN > > â¦ and /vm downloading the latest stable (/vm4, next month) > > but thenâ¦ what to do with the > > /30+vm > /40+vm > > scripts? > yesâ¦ they *could* realise link is talking to âconvenient vmâ so it would download /vm3 and /vm4â¦ but Iâm describing the problem, who grows exponentially. > Keeping âforever compatibilityâ is not good. > It does not work. > It does not scale. > > Esteban > >> Dale >> >> On 3/13/15 5:04 AM, Damien Cassou wrote: >>> Esteban Lorenzano writes: >>> >>>> thatâ¦ is someone using it? >>> I think the pharo-users mailing list is more appropriate >>> >> >> >

March 23, 2015

Re: [Pharo-dev] [Pharo4] Failing tests on CI server

by Andrei Chis

testBehaviorRespectsPolymorphismWithTraitBehavior is also fixed in upstream. On Mon, Mar 23, 2015 at 2:07 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi > > We have 4 failing tests left, one is already fixed but not yet in the > release: > > GLMTabulatorMorphicTest>>#testSpawnTabulator > - fixed upstream > > TxAthensLayoutTest>>#testScrollToLargeX > > BehaviorTest>>#testBehaviorRespectsPolymorphismWithTraitBehavior > > > ClassDescriptionTest>>#testClassDescriptionRespectsPolymorphismWithTraitDescription >

March 23, 2015

[Pharo4] Failing tests on CI server

by Marcus Denker

Hi We have 4 failing tests left, one is already fixed but not yet in the release: GLMTabulatorMorphicTest>>#testSpawnTabulator - fixed upstream TxAthensLayoutTest>>#testScrollToLargeX BehaviorTest>>#testBehaviorRespectsPolymorphismWithTraitBehavior ClassDescriptionTest>>#testClassDescriptionRespectsPolymorphismWithTraitDescription

March 23, 2015

Morphs becoming unresponsive

by Henrik Johansen

I just ran into a case where all morphs became unresponsive, and clicking anywhere only gave me the World Menu. After some investigation, it turned out all the World submorphs had been locked, and I could "unfreeze" them with the following (from a new Workspace): World submorphsDo: [ :aMorph | aMorph unlock ] What triggered it? Well, the image had become unresponsive, so I clicked the close buttons a couple of times (before trying good ol' cmd-dot, which brought up a debugger on the old UI process and let me continue). The close dialog is modal, normally that's no problem, since the modal morph locks all other morphs, no two can be opened at the same time (unless you somehow let that modal morph open another), but the close triggered by the system window's close button is special, since it is triggered outside the control of the World. The bug is rare in occurrence, yet easy to trigger; press the window close button twice, cancel one of the close dialogs, all windows that were open will remain locked and seem unresponsive. It might be smart to rethink the whole modality concept to make the code more robust/coherent, but for now an extra check for this single case in PasteUpMorph >> windowEvent: (for instance, using a morph property) should do the trick, I'll submit a slice shortly. Cheers, Henry

March 23, 2015

Re: [Pharo-dev] Old Pharo Mac VM on pharo.org

by Esteban Lorenzano

> On 23 Mar 2015, at 10:27, Norbert Hartl <norbert(a)hartl.name> wrote: > > >> Am 23.03.2015 um 09:51 schrieb Noury Bouraqadi <bouraqadi(a)gmail.com <mailto:bouraqadi@gmail.com>>: >> >> Hi, >> >> On http://pharo.org/download <http://pharo.org/download> I got the Mac VM dating back to sept 2014. >> Shouldn't it be http://files.pharo.org/vm/pharo/mac/latest.zip <http://files.pharo.org/vm/pharo/mac/latest.zip> ? >> > No, I think latest is more less a direct copy of the latest successful build on jenkins. That would be a no-go to offer as the vm to use. VMs have have releases as well. And in the same directory there is a stable.zip which is the right one. And it is from september. Everything else is in the hands of esteban. this :) but seriously: Iâve been having some problems to promote a newer vm as stable, concretely in the pharo-minimal step. I wanted to have new one for Pharo4, but Iâm not arriving eitherâ¦ so I will move it as soon as I find a solution, Iâm sorry :( Esteban > > Norbert >

March 23, 2015

Re: [Pharo-dev] Issue Validator Report - Service Temporarily Unavailable

by Christophe Demarey

Jenkins was down. I just restarted it. Le 23 mars 2015 Ã 13:04, Ben Coman a Ã©crit : > I went to review an issue validation report and got "Service Temporarily Unavailable" > > https://ci.inria.fr/pharo/job/Pharo-4.0-Issue-Validator/27809//artifact/val… > > cheers -ben

March 23, 2015

Issue Validator Report - Service Temporarily Unavailable

by Ben Coman

I went to review an issue validation report and got "Service Temporarily Unavailable" https://ci.inria.fr/pharo/job/Pharo-4.0-Issue-Validator/27809//artifact/val… cheers -ben

March 23, 2015

Re: [Pharo-dev] Old Pharo Mac VM on pharo.org

by Norbert Hartl

> Am 23.03.2015 um 09:51 schrieb Noury Bouraqadi <bouraqadi(a)gmail.com>: > > Hi, > > On http://pharo.org/download <http://pharo.org/download> I got the Mac VM dating back to sept 2014. > Shouldn't it be http://files.pharo.org/vm/pharo/mac/latest.zip <http://files.pharo.org/vm/pharo/mac/latest.zip> ? > No, I think latest is more less a direct copy of the latest successful build on jenkins. That would be a no-go to offer as the vm to use. VMs have have releases as well. And in the same directory there is a stable.zip which is the right one. And it is from september. Everything else is in the hands of esteban. Norbert

March 23, 2015