- Pharo-dev - lists.pharo.org

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/… 2 regressions found. KernelTests.Classes.BehaviorTest.testBehaviorRespectsPolymorphismWithTraitBehavior KernelTests.Classes.MetaclassTest.testMetaclassAndTraitClassRespectsPolymorphismRules

Aug. 13, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… 2 regressions found. KernelTests.Classes.BehaviorTest.testBehaviorRespectsPolymorphismWithTraitBehavior KernelTests.Classes.MetaclassTest.testMetaclassAndTraitClassRespectsPolymorphismRules

Aug. 13, 2013

Re: [Pharo-dev] Access to issue tracker?

by Camillo Bruni

I never tried the monkey/registration page. But you should be able to login here: http://pharo.fogbugz.org - reset your password (since you don't have one yet) - login at http://pharo.fogbugz.org I hope that helps. On 2013-08-13, at 01:01, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Same here > > El 13/08/2013 0:34, Javier PimÃ¡s escribiÃ³: >> Hi, I don't know if it's just me or if I'm doing something wrong but I >> was never able to get a user for the issue tracker. I enter here >> <http://bugs.pharo.org/issues/register>, put a username, an email and >> tick the not a monkey box in order to create an account. It redirects me >> here <https://pharo.fogbugz.com/> but I never get a mail or anything I >> could use to login, what I am doing wrong? >> >> Cheers, >> Javier >> >> -- >> Lic. Javier PimÃ¡s >> Ciudad de Buenos Aires > >

Aug. 13, 2013

loosing versions of method after deleting and creating new

by Sabine KnÃ¶fel

Hi, sometimes I have got the following situation: 1) I delete a method 2) I recognize uhhhh, I need it! it was wrong to delete it! 3) I re-write it (or get it from changes file or old image) 4) now, the versions of the method are lost I would have the following wishes for this situation: a) it should be easier for me to get back the deleted method (easier as searching the changes file or load old version of image) b) after re-writing the method, I want the versions of this method back. Perhaps there is another way to handle this and I did not know it. For a while I was renaming methods (e.g. from "methodname" to "methodnameOLD") instead of deleting it but this is not the way it should be imho. I was used to have this functionality in envy. What do you think about this? Regards Sabine -- View this message in context: http://forum.world.st/loosing-versions-of-method-after-deleting-and-creatin… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 13, 2013

Re: [Pharo-dev] [ANN] Stamp, another STOMP implementation

by StÃ©phane Ducasse

> > >> Excellent! >> And with a lovely documentation (even if too short to my eyes :)). > > Indeed, although it is better than nothing, it is too short and the code itself can use more comments as well, but it is a pretty complex subject, especially if you are unfamiliar with messaging-oriented middleware and architecture. > > It will improve over time. Users are an important driver for improvements. I'm sure about that :)

Aug. 13, 2013

Re: [Pharo-dev] [rmod] Link between Spec model and Morph ?

by Erwan Douaille

2013/8/13 ClÃ©ment Bera <bera.clement(a)gmail.com> > Ok I think get your question. Not an easy one :) > > So LabelModel knows its AbstractSpec with a class side method: > > LabelModel class>>defaultSpec > <spec> > ^ {#LabelSpec. > #model:. #model. > #getEnabledSelector:. #enabled. > #getTextSelector:. #getText. > #vResizing:. #shrinkWrap. > #hResizing:. #spaceFill. > #borderWidth:. #(model borderWidth). > #borderColor:. #(model borderColor). > #dragEnabled:. #(model dragEnabled). > #dropEnabled:. #(model dropEnabled). > #setBalloonText:. { #model . #help}} > > So you have LabelModel->#LabelSpec. > > This symbol, #LabelSpec, corresponds to a class. You can check: > > SpecBinder class>>initializeBindings > "self initializeBindings" > bindings := IdentityDictionary new. > bindings > at: #ListSpec put: ListSpec; > at: #MultiColumnListSpec put: MultiColumnListSpec; > at: #IconListSpec put: IconListSpec; > at:#model put: ModelSpec; > at: #RawSpec put: RawSpec; > at: #ComposableSpec put: ComposableSpec; > at: #TextSpec put: TextSpec; > at: #ButtonSpec put: ButtonSpec; > at: #CheckboxSpec put: CheckboxSpec; > at: #DropListSpec put: DropListSpec; > at: #LabelSpec put: LabelSpec; > at: #FrameLayoutSpec put: FrameLayoutSpec; > at: #TextFieldSpec put: TextFieldSpec; > at: #TreeSpec put: TreeSpec; > at: #WindowSpec put: WindowSpec; > at:#DialogWindowSpec put: DialogWindowSpec; > > So you have LabelModel->#LabelSpec->LabelSpec. > > LabelSpec is an AbstractSpec and subclasses of AbstractSpec has the method > classSymbol. Here we have > > LabelSpec>>classSymbol > ^ #Label > > So you have LabelModel->#LabelSpec->LabelSpec->#Label. > > Now this symbol corresponds to a class. You can check: > > MorphicBindings>>initializeClassesDictionary > > ^ IdentityDictionary new > at: #List put: #PluggableListMorph; > at: #IconList put: #PluggableIconListMorph; > at: #Text put: #PluggableTextMorph; > at: #Button put: #PluggableButtonMorph; > at: #Panel put: #PanelMorph; > at: #Checkbox put: #CheckboxMorph; > at: #DropList put: #DropListMorph; > at: #TextField put: #PluggableTextFieldMorph; > at: #Label put: #LabelMorph; > at: #MultiColumnList put: #PluggableMultiColumnListMorph; > at: #Tree put: #MorphTreeMorph; > at: #Slider put: #PluggableSliderMorph; > at: #FrameLayout put: #LayoutFrame; > at: #Window put: #SpecWindow; > at: #DialogWindow put: #SpecDialogWindow; > yourself > > So you have LabelModel->#LabelSpec->LabelSpec->#Label->LabelMorph. > > Does that answer your question this time ? > > > Perfect ! Thanks ! :) > > > > 2013/8/13 Erwan Douaille <douailleerwan(a)gmail.com> > >> Hi, >> >> Does anyone can explain me how/where the link is ? >> I guess its related to AbstractSpec subclasses, but i don't know how does >> it work. >> >> I will be at lab the whole week. >> >> >> 2013/8/12 ClÃ©ment Bera <clement.bera(a)minesdedouai.fr> >> A spec model (ComposableModel) has a window (WindowModel), this window >> has a window (SpecWindow), this window inherits from StandardWindow which >> inherits from SystemWindow which inherits from MorphicModel which inherits >> fromBorderedMorph which inherits from Morph >> >> Does that answer your question ? >> >> >> No :) >> >> I mean How the labelModel know than his morph is a LabelMorph ? >> >> >> -- >> Best regards, >> >> Douaille Erwan <douaille.erwan(a)gmail.com> >> > > -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

Aug. 13, 2013

Re: [Pharo-dev] [rmod] Link between Spec model and Morph ?

by ClÃ©ment Bera

Ok I think get your question. Not an easy one :) So LabelModel knows its AbstractSpec with a class side method: LabelModel class>>defaultSpec <spec> ^ {#LabelSpec. #model:. #model. #getEnabledSelector:. #enabled. #getTextSelector:. #getText. #vResizing:. #shrinkWrap. #hResizing:. #spaceFill. #borderWidth:. #(model borderWidth). #borderColor:. #(model borderColor). #dragEnabled:. #(model dragEnabled). #dropEnabled:. #(model dropEnabled). #setBalloonText:. { #model . #help}} So you have LabelModel->#LabelSpec. This symbol, #LabelSpec, corresponds to a class. You can check: SpecBinder class>>initializeBindings "self initializeBindings" bindings := IdentityDictionary new. bindings at: #ListSpec put: ListSpec; at: #MultiColumnListSpec put: MultiColumnListSpec; at: #IconListSpec put: IconListSpec; at:#model put: ModelSpec; at: #RawSpec put: RawSpec; at: #ComposableSpec put: ComposableSpec; at: #TextSpec put: TextSpec; at: #ButtonSpec put: ButtonSpec; at: #CheckboxSpec put: CheckboxSpec; at: #DropListSpec put: DropListSpec; at: #LabelSpec put: LabelSpec; at: #FrameLayoutSpec put: FrameLayoutSpec; at: #TextFieldSpec put: TextFieldSpec; at: #TreeSpec put: TreeSpec; at: #WindowSpec put: WindowSpec; at:#DialogWindowSpec put: DialogWindowSpec; So you have LabelModel->#LabelSpec->LabelSpec. LabelSpec is an AbstractSpec and subclasses of AbstractSpec has the method classSymbol. Here we have LabelSpec>>classSymbol ^ #Label So you have LabelModel->#LabelSpec->LabelSpec->#Label. Now this symbol corresponds to a class. You can check: MorphicBindings>>initializeClassesDictionary ^ IdentityDictionary new at: #List put: #PluggableListMorph; at: #IconList put: #PluggableIconListMorph; at: #Text put: #PluggableTextMorph; at: #Button put: #PluggableButtonMorph; at: #Panel put: #PanelMorph; at: #Checkbox put: #CheckboxMorph; at: #DropList put: #DropListMorph; at: #TextField put: #PluggableTextFieldMorph; at: #Label put: #LabelMorph; at: #MultiColumnList put: #PluggableMultiColumnListMorph; at: #Tree put: #MorphTreeMorph; at: #Slider put: #PluggableSliderMorph; at: #FrameLayout put: #LayoutFrame; at: #Window put: #SpecWindow; at: #DialogWindow put: #SpecDialogWindow; yourself So you have LabelModel->#LabelSpec->LabelSpec->#Label->LabelMorph. Does that answer your question this time ? 2013/8/13 Erwan Douaille <douailleerwan(a)gmail.com> > Hi, > > Does anyone can explain me how/where the link is ? > I guess its related to AbstractSpec subclasses, but i don't know how does > it work. > > I will be at lab the whole week. > > > 2013/8/12 ClÃ©ment Bera <clement.bera(a)minesdedouai.fr> > A spec model (ComposableModel) has a window (WindowModel), this window has > a window (SpecWindow), this window inherits from StandardWindow which > inherits from SystemWindow which inherits from MorphicModel which inherits > fromBorderedMorph which inherits from Morph > > Does that answer your question ? > > > No :) > > I mean How the labelModel know than his morph is a LabelMorph ? > > > -- > Best regards, > > Douaille Erwan <douaille.erwan(a)gmail.com> >

Aug. 13, 2013

Re: [Pharo-dev] [ANN] Stamp, another STOMP implementation

by phil＠highoctane.be

superb! On Tuesday, August 13, 2013, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 13 Aug 2013, at 15:30, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Excellent! >> And with a lovely documentation (even if too short to my eyes :)). > > Indeed, although it is better than nothing, it is too short and the code itself can use more comments as well, but it is a pretty complex subject, especially if you are unfamiliar with messaging-oriented middleware and architecture. > > It will improve over time. Users are an important driver for improvements. > >> On Aug 13, 2013, at 3:18 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> Hi, >>> >>> I am pleased to announce the public release of Stamp >>> >>> http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Stamp >>> https://github.com/svenvc/docs/blob/master/neo/stamp.md >>> >>> Stamp is an implementation of STOMP, the Simple (or Streaming) Text Oriented Message Protocol, for Pharo, a protocol to interact with message-oriented middleware (MOM). >>> >>> More specifically, Stamp implements STOMP 1.2 and was tested against RabbitMQ 3.1. Other message-oriented middleware implementations accessible through STOMP include Apache ActiveMQ, Glassfish Open MQ and Fuse Message Broker based on Active MQ - but these have not yet been tested. >>> >>> Messaging middleware is an important technology for building scaleable and flexible enterprise software architectures. >>> >>> Stamp itself is still evolving. Any feedback is welcome. >>> >>> Sven >>> >>> PS: As noted in https://github.com/svenvc/docs/blob/master/neo/stamp.md#acknowledgementthere is a relation with GÃ¶ran Krampe's older http://www.squeaksource.com/StompProtocol.html >>> >>> -- >>> Sven Van Caekenberghe >>> http://stfx.eu >>> Smalltalk is the Red Pill >>> >>> >> >> > > > -- --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Featured on the Software Process and Measurement Cast http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller

Aug. 13, 2013

[update 3.0] #30332

by StÃ©phane Ducasse

less broken tests soon green 30332 ----- - issue 11414 Fixing s1 change parsing https://pharo.fogbugz.com/default.asp?11414 - issue 11409 EyeInspector class-side slot #useAutoRefresh is missing https://pharo.fogbugz.com/default.asp?11409 - issue 11411 Cannot resize inspector window per inspector class https://pharo.fogbugz.com/default.asp?11411 - 11410 failing test (Polymorphism between classes and traits) https://pharo.fogbugz.com/default.asp?11410 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-StephaneDucass… http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusRefactoring-StephaneD… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-StephaneDucasse.511.… http://smalltalkhub.com/mc/Pharo/Pharo30/main/KernelTests-StephaneDucasse.5…

Aug. 13, 2013

Re: [Pharo-dev] [ANN] Stamp, another STOMP implementation

by Sven Van Caekenberghe

On 13 Aug 2013, at 15:30, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Excellent! > And with a lovely documentation (even if too short to my eyes :)). Indeed, although it is better than nothing, it is too short and the code itself can use more comments as well, but it is a pretty complex subject, especially if you are unfamiliar with messaging-oriented middleware and architecture. It will improve over time. Users are an important driver for improvements. > On Aug 13, 2013, at 3:18 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Hi, >> >> I am pleased to announce the public release of Stamp >> >> http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Stamp >> https://github.com/svenvc/docs/blob/master/neo/stamp.md >> >> Stamp is an implementation of STOMP, the Simple (or Streaming) Text Oriented Message Protocol, for Pharo, a protocol to interact with message-oriented middleware (MOM). >> >> More specifically, Stamp implements STOMP 1.2 and was tested against RabbitMQ 3.1. Other message-oriented middleware implementations accessible through STOMP include Apache ActiveMQ, Glassfish Open MQ and Fuse Message Broker based on Active MQ - but these have not yet been tested. >> >> Messaging middleware is an important technology for building scaleable and flexible enterprise software architectures. >> >> Stamp itself is still evolving. Any feedback is welcome. >> >> Sven >> >> PS: As noted in https://github.com/svenvc/docs/blob/master/neo/stamp.md#acknowledgement there is a relation with GÃ¶ran Krampe's older http://www.squeaksource.com/StompProtocol.html >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> > >

Aug. 13, 2013