June 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

by kilon

wait a sec , who said PPA solves my problem ? Damien have you tested it ? PPA did not solve my problem ! It complained about missing a X11 something library and never allowed me to open the image. The problem got away when I used the instructions to install those libraries. If you intended it to be that easy then I advise you to test it on a 64 bit ubuntu without those 32 bit compatibility libraries. Of course not having a 64 bit version when pretty much any programming language out there that it takes itself seriously (intended to be used professionally ) has one, is not exactly good first impression for pharo or squeak. I am sorry to be so strict and I am downgrading anyone's effort but if you guys are serious about making people taking pharo seriously , you better realise thats its 2013 and we are still stuck with a 32 bit version and we do a buch of none sense to get pharo running. Maybe the pharo efforts should be diverted towards that direction. -- View this message in context: http://forum.world.st/Pharo-dev-Pharo-does-not-work-on-ubuntu-13-04-tp46950… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 25, 2013

Challenges for a real debugger for Pharo :)

by StÃ©phane Ducasse

Hi guys when working on a new morphic kernel, we got stuck with a really difficult to find bug (we are still looking for it). If new generation debugger lovers want to try. Here it is - load the bloc version 6 from AlainPlantec/Bloc on smalltalkHub - execute the snippet (alain will post the snippet because it is on his machine) BlProtoMorph new openInWorld (there is another one) - move the mouse and the system gets blocked. After looking for it for a couple of hours here are some wishes list. - would be good to be able to set a haltOnce to **all** the methods of a **particular** object :) - would be good to have the equivalent of GlobalVaHoldingOneObject haltOnce ifTrue: [â¦.] - would be nice that we can say that the object once debugged does not receive any other messages (imagine an object in a fast rendering loops and that one message causes problems). Stef

June 25, 2013

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

by Camillo Bruni

On 2013-06-25, at 19:28, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > Confirmed. The bang line is now hidden. > > The question that remains is: why the duality between html/bash? > Smells like a hack. A clever one for sure. But a hack nonetheless. :) > Esteban A. Maringolo it simplifies a lot since there is only a single static URL which is fully self-documenting.

June 25, 2013

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

by Esteban A. Maringolo

Confirmed. The bang line is now hidden. The question that remains is: why the duality between html/bash? Smells like a hack. A clever one for sure. But a hack nonetheless. :) Esteban A. Maringolo 2013/6/25 Camillo Bruni <camillobruni(a)gmail.com>: > fixed > > On 2013-06-25, at 17:16, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> Comment aside, there is a #!/bin/bash # line at the top of the >> http://get.pharo.org/ page, which is outside of the comment that >> immediately follows it (between ). >> >> That bang line, plus -1em margin rule applied to the html body causes >> a visual glitch at the top, that ruins a perfectly minimal page style >> :) >> > >

June 25, 2013

Re: [Pharo-dev] [update 2.0] #20608

by StÃ©phane Ducasse

martin we should write the doc with gutenberg. I can start porting it. Stef On Jun 25, 2013, at 11:33 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > 20608 > ----- > > 10888 Backport 2.0: Compound Extension Methods Unpackaged > https://pharo.fogbugz.com/f/cases/10888/Backport-2-0-Compound-Extension-Met… > > 10730 Fix for stack serialization with Fuel > https://pharo.fogbugz.com/f/cases/10730/Fix-for-stack-serialization-with-Fu… > > 10994 Backport 2.0: Delays do not work properly directly on image startup > https://pharo.fogbugz.com/f/cases/10994/Backport-2-0-Delays-do-not-work-pro… > > Diff information: > http://ss3.gemstone.com/ss/Pharo20/RPackage-Tests-EstebanLorenzano.111.diff > http://ss3.gemstone.com/ss/Pharo20/RPackage-Core-EstebanLorenzano.216.diff > http://ss3.gemstone.com/ss/Pharo20/Kernel-EstebanLorenzano.1348.diff > http://ss3.gemstone.com/ss/Pharo20/FuelTests-EstebanLorenzano.316.diff > http://ss3.gemstone.com/ss/Pharo20/Fuel-EstebanLorenzano.767.diff > >

June 25, 2013

Re: [Pharo-dev] looking at initialization of LayoutProperties :)

by StÃ©phane Ducasse

> things which you can easily do in prototype-based system, not easy in > class-based. Yes I know now this is a nest for bugs (if the assure methods is not sent correctlyâ¦). > > Here, i think a side effect of porting Morphic from self to smalltalk. > So, in prototype-based system, a prototype could have a default > property (like hResizing) > and hold some default value (#rigid, for instance)... > like that, all objects which inherit from that one, will also inherit > this property. > But if one would like to set it, it will set new value of this > property, but not in prototype, > but actually in object which you sent message to. > That's why all this dance with ifNil: â¦ This is why I want also in addition to variableSubclass: hashTableSubclass: Stef

June 25, 2013

Re: [Pharo-dev] Conflict merging resolution is a bit doomed :)

by StÃ©phane Ducasse

Imagine that you have a conflict because a method changed in the image and that the resolution is please keep the version that was in the slice, then you republish a slice with the same method and when the integrator will do merge he will get again: there is a conflict with the different version that it is the image. So from a person performing a fix there is no way that I can produce a slice that does not produce a conflict. > I don't understand. If you merge and recommit it is fine, since the new slice will have different ancestors the 3-way merge won't complain a second time, no? > > On 2013-06-25, at 11:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> I do not know how I can republish a Slice when there is a conflict. Especially when I merged and say that I want to keep the change I did. So we are in the deadlock. There is no way for the fix producers to indicate that >> he merged and that his changes should be keep. >> >> So from a bug integration process this is not really good. >> >> Stef > >

June 25, 2013

Re: [Pharo-dev] [update 3.0] #30221

by Andrei Vasile Chis

> Also it would be good to sync with the content from the Debugger >> repository as it contains some bug fixes. >> What can I do to make this easy or you? (I can merge the version from >> pharo with the one from the Debugger repository; >> should I also create a slice?) >> >> Yeah please merge it and make a slice and a bug report in fogbugz. It > will be integrated the day after you create the slice and put the bug in > bugtracker to status 'fix review needed'. > Will do it by tomorrow. > Andrei I have a question. On the old debugger when I right click on the > stack I have a lot of features (as return value, browse class, ..). On the > new debugger with Spec UI and your model I don't have all these features. > > Are they implemented in the model and not in the spec UI ? Are they not > implemented because no one requested :) ?Could you add them ? > They are not implemented because at beginning I didn't needed them :). They will be added soon (https://pharo.fogbugz.com/default.asp?10952) Also I've created some more issues with the things that should be done in order for the new debugger to be ready for integration. I'd be online Friday afternoon during the sprint working on those issues. Andrei

June 25, 2013

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

by Pablo R. Digonzelli

+1 Ing. Pablo Digonzelli Sofware Solutions IP Soluciones SRL 25 de Mayo 521. Entrepiso A email: pdigonzelli(a)softsargentina.com email: pdigonzelli(a)gmail.com twitter: @pdigonzelli Tel: 0381 4227378 Cel: 0381 155982714 ----- Mensaje original ----- De: "Damien Cassou" <damien.cassou(a)gmail.com> Para: "Pharo Development List" <pharo-dev(a)lists.pharo.org> Enviados: Martes, 25 de Junio 2013 11:32:06 Asunto: Re: [Pharo-dev] Pharo does not work on ubuntu 13.04 On Tue, Jun 25, 2013 at 4:17 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hmm, you also need libssl0.9.8 or libssl0.9.8:i386 for Pharo since it includes SSL/TLS/HTTPS support out of the box. > > Anyway, missing deps are easily found using ldd. what is the problem with you guys? I spent and continue to spend days on packaging Pharo for Ubuntu so that everyone can forget about dependencies and 32 vs. 64 issues. So why do you keep on talking about this complex and undocumented method of installing Pharo? Just execute what is documented on the pharo.org website and you are guaranteed to have the latest version of the VM working whatever your Ubuntu is (provided it is still supported by Canonical) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 25, 2013

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

by Camillo Bruni

fixed On 2013-06-25, at 17:16, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Comment aside, there is a #!/bin/bash # line at the top of the > http://get.pharo.org/ page, which is outside of the comment that > immediately follows it (between ). > > That bang line, plus -1em margin rule applied to the html body causes > a visual glitch at the top, that ruins a perfectly minimal page style > :) >

June 25, 2013