- Pharo-dev - lists.pharo.org

[Pharo-project] [update 3.0] #30074

by Marcus Denker

30074 ----- 10447 Sync Opal again with 3.0 https://pharo.fogbugz.com/f/cases/10447 10446 deprecate #parserClass https://pharo.fogbugz.com/f/cases/10446 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Regex-Tests-Core-MarcusDenke… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/System-FilePackage-MarcusDen… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/OpalCompiler-Tests-MarcusDen… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/OpalCompiler-Core-MarcusDenk… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Compiler-MarcusDenker.413

April 29, 2013

[Pharo-project] State of PharoConf videos

by Stephan Eggermont

Chris wrote: >I would like to show my talk ("Selling Pharo-based Solutions" at >PharoConf) to my team and enhance it for the next time. Just out of >curiosity: are you still working on those videos? Otherwise, would you >mind to provide the video file somehow? Too many distractions, so not enough speed. I'll put it up. Stephan

April 29, 2013

Re: [Pharo-project] Why keymap modifiers change receiver instead of return new instance?

by Igor Stasenko

On 28 April 2013 22:01, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2013/4/28 stephane ducasse <stephane.ducasse(a)free.fr> > >> > Hello. >> > >> > I found this: >> > >> > shortcut := $a ctrl. >> > self assert: shortcut == shortcut shift >> > >> > Why modifiers change receiver state instead of create new instance? >> >> I can understand since they modify the shortcut. >> >> > To me it is very bad unexpected behaviour. >> >> Why? >> >> > Because > > shortcut1 := $a ctrl. > shortcut2 := $a ctrl shift > > created different shortcuts. > > And it is fully unexpected that I can not refactor it to: > > shotcut2 := shortcut1 shift > > Because after that my shortcut1 become broken. > > It was happen in TxTextMorph where selection and movement shortcuts > created at same time > > TxTextMorph>>moveEditorOn: aShortcut by: aSelector > > self on: aShortcut do: [ > self moveEditorBy: aSelector withSelection: false ]. > self on: selectionModeModifier + aShortcut do: [ > self moveEditorBy: aSelector withSelection: true]. > Wow, that's beatiful piece of code! This is how it should look like: clear and understandable from a first sight. So, we should fix the shortcuts api to let this beauty live :) > > To fix it I add deep copy of given shortcut before modifier operation. > > > >> > There is another example: >> > >> > shortcut := $a ctrl. >> > self assert: shortcut == (KMModifier shift + shortcut) >> > >> > Yes. Such operation modified argument of message #+. What the crapp! >> Why it not returns new instance? >> > >> > I hope you agree to change this behaviour >> > >> > >> >> >> > -- Best regards, Igor Stasenko.

April 29, 2013

Re: [Pharo-project] Spec LabelModel color

by roberto.minelli＠usi.ch

Thanks a lot. Now I implemented the solution you proposed in the previous mail and it works. Cheers, R On Apr 29, 2013, at 4:49 PM, ClÃ©ment Bera <clement.bera(a)inria.fr> wrote: > "Do I have to use Pharo 3.0 to have black labels?" > > If you want to implement something for a customer, you should *not* use Pharo 3.0. It is in alpha state which means you might have unexpected bugs or VM crashes (even if the alpha version is currently quite stable). The best for you would be to patch a Pharo 2.0. For example patch LabelModel with : > > LabelModel>>#text: aText > <api: #string getter: #getText registration: #whenTextChanged:> > "Set the text of the label" > > textHolder contents: (aText asText addAttribute: TextColor black) > > Then all the LabelModels will be black. > > > > 2013/4/29 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > By the way I used a fresh Pharo 2.0 image and labels are still white :D > > > > Cheers, > R > > On Apr 29, 2013, at 3:32 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > wrote: > > > I can't say because I never use Moose image > > > > Ben > > > > On Apr 29, 2013, at 3:07 PM, "roberto.minelli(a)usi.ch" <roberto.minelli(a)usi.ch> wrote: > > > >> By the way.. I often use the Moose image hosted at > >> > >> http://ci.inria.fr/moose/job/moose-latest-dev-4.8/lastSuccessfulBuild/artif… > >> > >> instead of the Pharo image.. And here Spec is not up to date. > >> > >> When I run the "System>Software Update" from the World menu, packages are not updated, right? > >> > >> I think it would be a nice-to-have. > >> > >> Cheers, > >> R > >> > >> > >> > >> On Apr 29, 2013, at 2:07 PM, roberto.minelli(a)usi.ch wrote: > >> > >>> Thanks for the answersâ¦ I will update to the last image ;) > >>> > >>> On Apr 29, 2013, at 1:38 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > >>> wrote: > >>> > >>>> In the latests image, it should be black :) > >>>> > >>>> Which image are you using ? > >>>> Ben > >>>> > >>>> On Apr 29, 2013, at 12:27 PM, roberto.minelli(a)usi.ch wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> I'm building a small UI with spec and I have a problem with the LabelModel. > >>>>> > >>>>> Is there any way to change the default color (white) of the #text: in a LabelModel? > >>>>> > >>>>> Thanks, > >>>>> Roberto > >>>> > >>> > >>> > >> > >> > > > > > > > > -- > ClÃ©ment BÃ©ra > Mate Virtual Machine Engineer > BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

April 29, 2013

[Pharo-project] [update 3.0] #30073

by Marcus Denker

30073 ----- 10445 Running NonDestructive Regression Tests Headless: wrong error handling https://pharo.fogbugz.com/f/cases/10445 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/UIManager-md.101 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Polymorph-Widgets-md.798

April 29, 2013

Re: [Pharo-project] Spec LabelModel color

by ClÃ©ment Bera

* "Do I have to use Pharo 3.0 to have black labels?"* If you want to implement something for a customer, you should *not* use Pharo 3.0. It is in alpha state which means you might have unexpected bugs or VM crashes (even if the alpha version is currently quite stable). The best for you would be to patch a Pharo 2.0. For example patch LabelModel with : LabelModel>>#text: aText <api: #string getter: #getText registration: #whenTextChanged:> "Set the text of the label" textHolder contents: (aText asText addAttribute: TextColor black) Then all the LabelModels will be black. 2013/4/29 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > By the way I used a fresh Pharo 2.0 image and labels are still white :D > > Do I have to use Pharo 3.0 to have black labels? > > Cheers, > R > > On Apr 29, 2013, at 3:32 PM, Benjamin < > benjamin.vanryseghem.pharo(a)gmail.com> > wrote: > > > I can't say because I never use Moose image > > > > Ben > > > > On Apr 29, 2013, at 3:07 PM, "roberto.minelli(a)usi.ch" < > roberto.minelli(a)usi.ch> wrote: > > > >> By the way.. I often use the Moose image hosted at > >> > >> > http://ci.inria.fr/moose/job/moose-latest-dev-4.8/lastSuccessfulBuild/artif… > >> > >> instead of the Pharo image.. And here Spec is not up to date. > >> > >> When I run the "System>Software Update" from the World menu, packages > are not updated, right? > >> > >> I think it would be a nice-to-have. > >> > >> Cheers, > >> R > >> > >> > >> > >> On Apr 29, 2013, at 2:07 PM, roberto.minelli(a)usi.ch wrote: > >> > >>> Thanks for the answersâ¦ I will update to the last image ;) > >>> > >>> On Apr 29, 2013, at 1:38 PM, Benjamin < > benjamin.vanryseghem.pharo(a)gmail.com> > >>> wrote: > >>> > >>>> In the latests image, it should be black :) > >>>> > >>>> Which image are you using ? > >>>> Ben > >>>> > >>>> On Apr 29, 2013, at 12:27 PM, roberto.minelli(a)usi.ch wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> I'm building a small UI with spec and I have a problem with the > LabelModel. > >>>>> > >>>>> Is there any way to change the default color (white) of the #text: > in a LabelModel? > >>>>> > >>>>> Thanks, > >>>>> Roberto > >>>> > >>> > >>> > >> > >> > > > > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

April 29, 2013

Re: [Pharo-project] Spec LabelModel color

by ClÃ©ment Bera

* "Do I have to use Pharo 3.0 to have black labels?"* If you want to implement something for a customer, you should *not* use Pharo 3.0. It is in alpha state which means you might have unexpected bugs or VM crashes (even if the alpha version is currently quite stable). The best for you would be to patch a Pharo 2.0. For example patch LabelModel with : LabelModel>>#text: aText <api: #string getter: #getText registration: #whenTextChanged:> "Set the text of the label" textHolder contents: (aText asText addAttribute: TextColor black) Then all the LabelModels will be black. 2013/4/29 roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> > By the way I used a fresh Pharo 2.0 image and labels are still white :D > > > > Cheers, > R > > On Apr 29, 2013, at 3:32 PM, Benjamin < > benjamin.vanryseghem.pharo(a)gmail.com> > wrote: > > > I can't say because I never use Moose image > > > > Ben > > > > On Apr 29, 2013, at 3:07 PM, "roberto.minelli(a)usi.ch" < > roberto.minelli(a)usi.ch> wrote: > > > >> By the way.. I often use the Moose image hosted at > >> > >> > http://ci.inria.fr/moose/job/moose-latest-dev-4.8/lastSuccessfulBuild/artif… > >> > >> instead of the Pharo image.. And here Spec is not up to date. > >> > >> When I run the "System>Software Update" from the World menu, packages > are not updated, right? > >> > >> I think it would be a nice-to-have. > >> > >> Cheers, > >> R > >> > >> > >> > >> On Apr 29, 2013, at 2:07 PM, roberto.minelli(a)usi.ch wrote: > >> > >>> Thanks for the answersâ¦ I will update to the last image ;) > >>> > >>> On Apr 29, 2013, at 1:38 PM, Benjamin < > benjamin.vanryseghem.pharo(a)gmail.com> > >>> wrote: > >>> > >>>> In the latests image, it should be black :) > >>>> > >>>> Which image are you using ? > >>>> Ben > >>>> > >>>> On Apr 29, 2013, at 12:27 PM, roberto.minelli(a)usi.ch wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> I'm building a small UI with spec and I have a problem with the > LabelModel. > >>>>> > >>>>> Is there any way to change the default color (white) of the #text: > in a LabelModel? > >>>>> > >>>>> Thanks, > >>>>> Roberto > >>>> > >>> > >>> > >> > >> > > > > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

April 29, 2013

Re: [Pharo-project] Spec LabelModel color

by roberto.minelli＠usi.ch

By the way I used a fresh Pharo 2.0 image and labels are still white :D Do I have to use Pharo 3.0 to have black labels? Cheers, R On Apr 29, 2013, at 3:32 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > I can't say because I never use Moose image > > Ben > > On Apr 29, 2013, at 3:07 PM, "roberto.minelli(a)usi.ch" <roberto.minelli(a)usi.ch> wrote: > >> By the way.. I often use the Moose image hosted at >> >> http://ci.inria.fr/moose/job/moose-latest-dev-4.8/lastSuccessfulBuild/artif… >> >> instead of the Pharo image.. And here Spec is not up to date. >> >> When I run the "System>Software Update" from the World menu, packages are not updated, right? >> >> I think it would be a nice-to-have. >> >> Cheers, >> R >> >> >> >> On Apr 29, 2013, at 2:07 PM, roberto.minelli(a)usi.ch wrote: >> >>> Thanks for the answersâ¦ I will update to the last image ;) >>> >>> On Apr 29, 2013, at 1:38 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> >>> wrote: >>> >>>> In the latests image, it should be black :) >>>> >>>> Which image are you using ? >>>> Ben >>>> >>>> On Apr 29, 2013, at 12:27 PM, roberto.minelli(a)usi.ch wrote: >>>> >>>>> Hi, >>>>> >>>>> I'm building a small UI with spec and I have a problem with the LabelModel. >>>>> >>>>> Is there any way to change the default color (white) of the #text: in a LabelModel? >>>>> >>>>> Thanks, >>>>> Roberto >>>> >>> >>> >> >> >

April 29, 2013

Re: [Pharo-project] Spec LabelModel color

by Benjamin

I can't say because I never use Moose image Ben On Apr 29, 2013, at 3:07 PM, "roberto.minelli(a)usi.ch" <roberto.minelli(a)usi.ch> wrote: > By the way.. I often use the Moose image hosted at > > http://ci.inria.fr/moose/job/moose-latest-dev-4.8/lastSuccessfulBuild/artif… > > instead of the Pharo image.. And here Spec is not up to date. > > When I run the "System>Software Update" from the World menu, packages are not updated, right? > > I think it would be a nice-to-have. > > Cheers, > R > > > > On Apr 29, 2013, at 2:07 PM, roberto.minelli(a)usi.ch wrote: > >> Thanks for the answersâ¦ I will update to the last image ;) >> >> On Apr 29, 2013, at 1:38 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> >> wrote: >> >>> In the latests image, it should be black :) >>> >>> Which image are you using ? >>> Ben >>> >>> On Apr 29, 2013, at 12:27 PM, roberto.minelli(a)usi.ch wrote: >>> >>>> Hi, >>>> >>>> I'm building a small UI with spec and I have a problem with the LabelModel. >>>> >>>> Is there any way to change the default color (white) of the #text: in a LabelModel? >>>> >>>> Thanks, >>>> Roberto >>> >> >> > >

April 29, 2013

Re: [Pharo-project] Spec LabelModel color

by roberto.minelli＠usi.ch

By the way.. I often use the Moose image hosted at http://ci.inria.fr/moose/job/moose-latest-dev-4.8/lastSuccessfulBuild/artif… instead of the Pharo image.. And here Spec is not up to date. When I run the "System>Software Update" from the World menu, packages are not updated, right? I think it would be a nice-to-have. Cheers, R On Apr 29, 2013, at 2:07 PM, roberto.minelli(a)usi.ch wrote: > Thanks for the answersâ¦ I will update to the last image ;) > > On Apr 29, 2013, at 1:38 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > wrote: > >> In the latests image, it should be black :) >> >> Which image are you using ? >> Ben >> >> On Apr 29, 2013, at 12:27 PM, roberto.minelli(a)usi.ch wrote: >> >>> Hi, >>> >>> I'm building a small UI with spec and I have a problem with the LabelModel. >>> >>> Is there any way to change the default color (white) of the #text: in a LabelModel? >>> >>> Thanks, >>> Roberto >> > >

April 29, 2013