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

Re: [Pharo-project] Platform and portable versions for Pharo 2.0 too

by Sean P. DeNigris

EstebanLM wrote > I "backported" the 3.0 publish mechanism to Pharo 2.0. > ... > http://files.pharo.org/platform/ I updated http://www.pharo-project.org/pharo-download/release-2-0 to the "Portable" terminology, with an updated description, and put the platform versions at the top, as the first choice. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Platform-and-portable-versions-for-Pharo-2-0-too-tp46… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 28, 2013

Re: [Pharo-project] Multiselect in method pane

by Benjamin

if it works go ahead ;) Ben On Mar 28, 2013, at 12:48 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 28.03.2013 um 11:51 schrieb stephane ducasse <stephane.ducasse(a)free.fr>: > >> >> On Mar 28, 2013, at 11:21 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> What is the rationale for having the method pane as multi-select list? I don't think it is of greater use when editing code. I could imagine that some refactoring tasks could be easier having multi-select lists. >>> >>> Anyway, if I try to rename a method without using the refactoring engine I just change the selector, save and delete the method with the old selector. In pharo 2.0 when you rename a method and then click on the old selector both methods are selected and shortcut invocation for deleting deletes both. Which is quite annoying. In my opinion there is no reason for two methods being selected. If you agree I'll happily enter a bug. >> >> >> The problem is not a nautilus bug but a compiled method one if I remember correctly. >> because two methods with the same body are equal. >> > It happens in MethodWidget>>#methodSelectionAt:put. When PluggableIconListMorph updates the list selection it calls the MethodWidget to set true on the new method selected. But MethodWidget uses a Dictionary for instVar methodSelection and finds the old method being equal and enables this. > As I don't see a reason why a selection should be done by equality this behavior can be fixed by using an IdentityDictionary. > > Fix: > > MethodWidget>>#initialize > > super initialize. > methodsSelection := IdentityDictionary new. > > Any arguments? > > Norbert

March 28, 2013

Re: [Pharo-project] Multiselect in method pane

by Norbert Hartl

Am 28.03.2013 um 11:51 schrieb stephane ducasse <stephane.ducasse(a)free.fr>: > > On Mar 28, 2013, at 11:21 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> What is the rationale for having the method pane as multi-select list? I don't think it is of greater use when editing code. I could imagine that some refactoring tasks could be easier having multi-select lists. >> >> Anyway, if I try to rename a method without using the refactoring engine I just change the selector, save and delete the method with the old selector. In pharo 2.0 when you rename a method and then click on the old selector both methods are selected and shortcut invocation for deleting deletes both. Which is quite annoying. In my opinion there is no reason for two methods being selected. If you agree I'll happily enter a bug. > > > The problem is not a nautilus bug but a compiled method one if I remember correctly. > because two methods with the same body are equal. > It happens in MethodWidget>>#methodSelectionAt:put. When PluggableIconListMorph updates the list selection it calls the MethodWidget to set true on the new method selected. But MethodWidget uses a Dictionary for instVar methodSelection and finds the old method being equal and enables this. As I don't see a reason why a selection should be done by equality this behavior can be fixed by using an IdentityDictionary. Fix: MethodWidget>>#initialize super initialize. methodsSelection := IdentityDictionary new. Any arguments? Norbert

March 28, 2013

Re: [Pharo-project] Versionner in pharo 2.0

by Esteban Lorenzano

Hi Norbert, Check around SystemAnnouncer :) Esteban On Mar 28, 2013, at 12:37 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > Can you tell me what an equivalent to a SystemChangeNotifier call would be today? I can derive Announcement class names from the message sends to SystemChangeNotifier. But I don't know e.g. where is the announcer in the system where you would register for class change, method modified etc. announcements. > > Norbert > > Am 28.03.2013 um 11:51 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> there is work in progress... a bit slow because my times (and Christoph's) are a bit... overcharged :) >> >> On Mar 28, 2013, at 11:17 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> Is there work in progress to make Versionner work in pharo 2.0? The problems I see are at first related to the removal SystemChangeNotifier. >>> If nobody is working on it is there any reading material about the changes from SystemChangeNotifier to Announcements? I could fix it myself then but I don't know nothing about this system internal. >>> >>> thanks, >>> >>> Norbert >> >> > >

March 28, 2013

Re: [Pharo-project] Fwd: Some question and request for Athens

by Igor Stasenko

On 27 March 2013 14:44, Tristan Bourgois <tristan.bourgois(a)gmail.com> wrote: > 2013/3/26 Igor Stasenko <siguctua(a)gmail.com>: >> On 26 March 2013 11:29, Tristan Bourgois <tristan.bourgois(a)gmail.com> wrote: >>> 2013/3/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> >>>> >>>> Begin forwarded message: >>>> >>>> From: Igor Stasenko <siguctua(a)gmail.com> >>>> Subject: Re: Some question and request for Athens >>>> Date: March 25, 2013 2:57:33 PM GMT+01:00 >>>> To: Tristan Bourgois <tristan.bourgois(a)gmail.com> >>>> Cc: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>, LE PORS Eric >>>> <eric.lepors(a)fr.thalesgroup.com> >>>> >>>> On 25 March 2013 11:45, Tristan Bourgois <tristan.bourgois(a)gmail.com> wrote: >>>> >>>> Hi Igor! >>>> >>>> I have some questions and request for Athens :) >>>> >>>> 1 Do exist a possibility in Athens to draw a Surface on a Surface? >>>> For example : >>>> aSurf drawSurface: anOtherSurface at: aPosition >>>> (I need it for draw image on a surface) >>>> >>>> >>>> yes. You can use Forms or surfaces as paints so they act like 2D textures: >>>> >>>> canvas setPaint: someSurface. >>>> canvas drawShape: myRect. >>> >>> Thanks that's works fine :) >>> >>>> >>>> 2 About my first question, I try to draw a png image on a Surface and >>>> I get some strange behavior. When nothing is applied on my first >>>> surface and draw the image in a rectangle path I crash the VM! >>>> This an example I tried and crash my VM: >>>> >>>> |surf pharoLogo ref path patternPaint| >>>> surf := AthensCairoSurface extent: 600@600. >>>> >>>> ref := 'pharo.png' asFileReference. >>>> pharoLogo := AthensCairoSurface createFromFile: ref fullName ifFailed:[nil]. >>>> >>>> surf drawDuring: [:can| >>>> surf clear. >>>> patternPaint := can setPaint: pharoLogo. >>>> patternPaint setExtend: #None. >>>> can drawShape: (0@0 extent: pharoLogo extent). >>>> ]. >>>> Display getCanvas drawImage: surf asForm at: 0@0. > > Did this code work fine on your image or other machine? (I'm working > on a Windows XP pro) > could be a problem. we should check. To workaround this, you can try to load .png into a form: Form fromBynaryStream: (ref ... readStream) >>>> If you need more information about the crash and my environment ask it :) >>>> >>>> weird... it should be working fine. >>> >>> I try it on a new clean image and again get a VM crash. >> >> okay, then i need more information :) > > I send the report of the crash in the mail. > yes, i see there's some problem.. but cannot tell anything why it happens. > Tristan > >> -- >> Best regards, >> Igor Stasenko. >> -- Best regards, Igor Stasenko.

March 28, 2013

Re: [Pharo-project] Versionner in pharo 2.0

by Norbert Hartl

Can you tell me what an equivalent to a SystemChangeNotifier call would be today? I can derive Announcement class names from the message sends to SystemChangeNotifier. But I don't know e.g. where is the announcer in the system where you would register for class change, method modified etc. announcements. Norbert Am 28.03.2013 um 11:51 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > there is work in progress... a bit slow because my times (and Christoph's) are a bit... overcharged :) > > On Mar 28, 2013, at 11:17 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Is there work in progress to make Versionner work in pharo 2.0? The problems I see are at first related to the removal SystemChangeNotifier. >> If nobody is working on it is there any reading material about the changes from SystemChangeNotifier to Announcements? I could fix it myself then but I don't know nothing about this system internal. >> >> thanks, >> >> Norbert > >

March 28, 2013

Re: [Pharo-project] one-click restored for pharo 3.0, renamed as "portable"

by Sean P. DeNigris

EstebanLM wrote > I created a "portable" version of Pharo 3.0, for those power users who > still need it :) Cool, Thanks :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/one-click-restored-for-pharo-3-0-renamed-as-portable-… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 28, 2013

Re: [Pharo-project] Platform and portable versions for Pharo 2.0 too

by Guillermo Polito

Cool! :) On Thu, Mar 28, 2013 at 12:34 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Hi, > > I "backported" the 3.0 publish mechanism to Pharo 2.0. > I suppose the 2.0 Summer will be like this then :) > > http://files.pharo.org/platform/ > > Cheers, > Esteban > >

March 28, 2013

[Pharo-project] Platform and portable versions for Pharo 2.0 too

by Esteban Lorenzano

Hi, I "backported" the 3.0 publish mechanism to Pharo 2.0. I suppose the 2.0 Summer will be like this then :) http://files.pharo.org/platform/ Cheers, Esteban

March 28, 2013

[Pharo-project] [update 2.0] #20594

by Esteban Lorenzano

20594 ----- 10123 Bug in warning in CriticBrowser https://pharo.fogbugz.com/f/cases/10123 Diff information: http://ss3.gemstone.com/ss/Pharo20/Manifest-CriticBrowser-EstebanLorenzano.… (yep, 2.0 keeps going... for sometime)

March 28, 2013