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

Re: [Pharo-project] Issue 3581 in pharo: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

by pharo＠googlecode.com

Comment #8 on issue 3581 by marianopeck: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3581 mmmm I don't understand. Check CompiledMethod >> at:put: at: key put: value "Set the value at key to be value." | index | index := self findElementOrNil: key. (self basicAt: index) ifNil: [tally := tally + 1. self basicAt: index put: key] ifNotNil: [(array at: index) flushCache]. array at: index put: value. self fullCheck. ^ value I think the problem is because ObjectAsMethodWrapper >> flushCache is empty. what do you think?

March 13, 2011

Re: [Pharo-project] [ANN] More on Keymappings

by Camillo Bruni

I started on the last Lille sprint a complete rewrite of the Keymapping package. As of now it is not yet functional but the growing test-coverage should help to solve this issue. m(^_-)m camillo On 2011-03-03, at 15:16, Camillo Bruni wrote: > Right, > > the stable has a preconditio which limits it to pharo 1.2. > Furthermore the initialization code seems to be incompatible as it uses to:do: on Character which is AFAIK not implemented in the core image Pharo 1.3. Hence apply the following changes: > > KMKeyEvent class >> initializeControlSequences > > ... > $a asciiValue to: $z asciiValue do: [:each | > d add: each asCharacter -> (each - $a asciiValue + 1)]. > ... > > then it should work. > > m(^_-)m > camillo > > > On 2011-03-03, at 09:25, Tudor Girba wrote: > >> Hi, >> >> I am very interested to get Keymapping integrated into Glamour. Could someone help me to load it? >> >> I tried: >> - in Pharo 1.2: >> Gofer it squeaksource: 'Keymapping'; package: 'ConfigurationOfKeymapping'; load. >> (ConfigurationOfKeymapping project version: #stable) load >> >> - in Pharo 1.3: >> Gofer it squeaksource: 'Keymapping'; package: 'ConfigurationOfKeymapping'; load. >> (ConfigurationOfKeymapping project version: '1.5') load >> >> >> Cheers, >> Doru >> >> >> On 27 Feb 2011, at 09:59, Tudor Girba wrote: >> >>> I also I cannot load Keymapping 1.5 in Pharo 1.2. I get DNU for Character>>+. This is due to an initialization in KMKeyEvent (see the attached debug log). >>> >>> I did the followings: >>> Gofer it >>> squeaksource: 'Keymapping'; >>> package: 'ConfigurationOfKeymapping'; >>> load. >>> >>> (ConfigurationOfKeymapping project version: #stable) load >>> >>> Am I missing something, or is this version not supposed to work in Pharo 1.2? >>> >>> Cheers, >>> Doru >>> >>> <PharoDebug.log> >>> >>> >>> On 26 Feb 2011, at 21:08, Francisco Ortiz PeÃ±aloza wrote: >>> >>>> You're telling me that if i do a clean installation of 1.5 it would work? >>>> >>>> Thanks in advance, >>>> Francisco >>>> >>>> On Sat, Feb 26, 2011 at 3:50 PM, Guillermo Polito >>>> <guillermopolito(a)gmail.com> wrote: >>>>> Mmm, If you had 1.4 and updated to 1.5, you will have some problems because >>>>> I did some refactorings on that... :/. >>>>> >>>>> On Sat, Feb 26, 2011 at 10:12 AM, Francisco Ortiz PeÃ±aloza >>>>> <patchinko(a)gmail.com> wrote: >>>>>> >>>>>> Guille i was using 1.4 and worked excellent, just tried 1.5 and on >>>>>> every stroke i made i've got a DNU on #realtarget >>>>>> >>>>>> Installed on last PharoCore 1.2, should i try it on 1.3? >>>>>> >>>>>> Great work, >>>>>> Fran >>>>>> >>>>>> On Sat, Feb 26, 2011 at 5:29 AM, laurent laffont >>>>>> <laurent.laffont(a)gmail.com> wrote: >>>>>>> >>>>>>> On Sat, Feb 26, 2011 at 5:42 AM, Guillermo Polito >>>>>>> <guillermopolito(a)gmail.com> wrote: >>>>>>>> >>>>>>>> What do we have now? >>>>>>>> >>>>>>>> - Can provide settings for a set of morphs >>>>>>>> >>>>>>>> - Can provide settings for a TextEditors (Smalltalk editor and related) >>>>>>>> >>>>>>>> - Settings integration >>>>>>>> I added some methods to the Settings Tree Builder in order to avoid >>>>>>>> references from the users code. >>>>>>>> >>>>>>>> - I ran Slint over it and cleaned it a lot more :). ( And learnt that >>>>>>>> Slint is there :P ) >>>>>>>> >>>>>>>> More info in here: http://guilleel3.blogspot.com/ >>>>>>> >>>>>>> A new blog, cool ! >>>>>>> Can I have Emacs-like keybinding in code editor, to switch browser, ... >>>>>>> ? >>>>>>> Laurent. >>>>>>> >>>>>>>> >>>>>>>> Guille >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow." >>> >>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Every thing should have the right to be different." >> >> >> >> > >

March 13, 2011

Re: [Pharo-project] Issue 3806 in pharo: Duration>>hours is broken

by pharo＠googlecode.com

Comment #10 on issue 3806 by cesar.ra...(a)gmail.com: Duration>>hours is broken http://code.google.com/p/pharo/issues/detail?id=3806 Well I think we need to rephrase that to: What is the consensus on changing these protocols which will break ANSI compliance. Returning 48 hours for (2 days) hours, is obviously non conforming the ANSI standard, except if from the draft I have access to it was materially changed to mean something resembling the OP request. I think the sixth comment brings a compromise solution, which is to implement the #asHours (perhaps even #asMinutes and #asSeconds) message. Leaving those ANSI protocol alone.

March 13, 2011

Re: [Pharo-project] [Pharo-users] Last pending things for Pharo 1.2

by Mariano Martinez Peck

Thanks Guille, perfect work :) On Sun, Mar 13, 2011 at 9:42 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > thanks. > > > Ok, I've blessed as release the version used in pharo dev from the > following Configs: > > > > ConfigurationOfPharoMorphicExtras > > ConfigurationOfPharoNonCore > > ConfigurationOfPharoSound > > ConfigurationOfRefactoringBrowser > > ConfigurationOfScriptManager > > ConfigurationOfShout > > ConfigurationOfXMLSupport > > ConfigurationOfOCompletion > > ConfigurationOfNile > > ConfigurationOfObjectMetaTools > > > > > > These ones were already blessed: > > > > ConfigurationOfAutotest > > ConfigurationOfProfStef > > ConfigurationOfXMLWriter > > ConfigurationOfAutomaticMethodCategorizer > > > > > > These one left to be blessed: > > > > ConfigurationOfOmniBrowser (I'd like not to release it until we get that > last issue fixed) > > ConfigurationOfMemoryMonitor (Alex, can the actual version be released?) > > ConfigurationOfPharo (I'd like not to release it until everything is > ready) > > > > > > > > On Sun, Mar 13, 2011 at 7:45 AM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > > > > > > On Sun, Mar 13, 2011 at 7:19 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > > > > > > On Sat, Mar 12, 2011 at 4:19 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > > So....here is the list of things I guess are pending: > > > > 1) "Release" all configurations included in Pharo (this is, > ConfigurationOfPharo and all it dependencies). I mean, we should NOT use or > depend on #development versions. > > > > I'll take a look at this... I had two weeks without programming, and I > can't sleep now without doing something :P > > > > please, be my guest :) > > > > > > 2) Update the one click image to use latest cog images and "pharo > prepared vms". There are some issues regarding this... > > 3) Write down all the things/summary done in Pharo 1.2 > > 5) Update SystemVersion current -->> Pharo1.2rc2 of 27 January 2011 > update 12340 > > 6) Condense sources? condense changes? #cleanUpForRelease > > > > Cheers > > > > Mariano > > > > > > > > >

March 13, 2011

Re: [Pharo-project] Issue 3706 in pharo: In OB: Text in comment pane of Browser uses syntax highlighting

by pharo＠googlecode.com

Comment #22 on issue 3706 by stephane...(a)gmail.com: In OB: Text in comment pane of Browser uses syntax highlighting http://code.google.com/p/pharo/issues/detail?id=3706 Guys The problem is not the read only access. I understand that lukas wants to control his repo. Now my point is that he should not wait that we release a version to migrate OB to it because right now OB is part of the release and we have a deadlock and people tried to help. We will work hard to make sure that the situation improves in the future and that we control our system.

March 13, 2011

Re: [Pharo-project] Issue 3814 in pharo: Weak announcements refinement

by pharo＠googlecode.com

Updates: Status: Fixed Comment #5 on issue 3814 by stephane...(a)gmail.com: Weak announcements refinement http://code.google.com/p/pharo/issues/detail?id=3814 we will integrate them tomorrow with igor

March 13, 2011

Re: [Pharo-project] Issue 2822 in pharo: possible XMl enhancement

by pharo＠googlecode.com

Comment #3 on issue 2822 by stephane...(a)gmail.com: possible XMl enhancement http://code.google.com/p/pharo/issues/detail?id=2822 yes!

March 13, 2011

Re: [Pharo-project] Issue 3809 in pharo: Fixed Width / Serif Font

by StÃ©phane Ducasse

On Mar 13, 2011, at 5:51 PM, pharo(a)googlecode.com wrote: > > Comment #2 on issue 3809 by tudor.gi...(a)gmail.com: Fixed Width / Serif Font > http://code.google.com/p/pharo/issues/detail?id=3809 > > I do not understand what the situation is. Is there a known and reproducible way for including fonts in the image ? you are talking about two kind of fonts, the one of dejavu are bitmaps fonts and somebody should extract them from bitmap and package them to be loadable in pharo. Else we should have the FT plugin and use it to use the fonts available on your machine.

March 13, 2011

Re: [Pharo-project] [Pharo-users] Last pending things for Pharo 1.2

by StÃ©phane Ducasse

thanks. > Ok, I've blessed as release the version used in pharo dev from the following Configs: > > ConfigurationOfPharoMorphicExtras > ConfigurationOfPharoNonCore > ConfigurationOfPharoSound > ConfigurationOfRefactoringBrowser > ConfigurationOfScriptManager > ConfigurationOfShout > ConfigurationOfXMLSupport > ConfigurationOfOCompletion > ConfigurationOfNile > ConfigurationOfObjectMetaTools > > > These ones were already blessed: > > ConfigurationOfAutotest > ConfigurationOfProfStef > ConfigurationOfXMLWriter > ConfigurationOfAutomaticMethodCategorizer > > > These one left to be blessed: > > ConfigurationOfOmniBrowser (I'd like not to release it until we get that last issue fixed) > ConfigurationOfMemoryMonitor (Alex, can the actual version be released?) > ConfigurationOfPharo (I'd like not to release it until everything is ready) > > > > On Sun, Mar 13, 2011 at 7:45 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Sun, Mar 13, 2011 at 7:19 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > On Sat, Mar 12, 2011 at 4:19 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > So....here is the list of things I guess are pending: > > 1) "Release" all configurations included in Pharo (this is, ConfigurationOfPharo and all it dependencies). I mean, we should NOT use or depend on #development versions. > > I'll take a look at this... I had two weeks without programming, and I can't sleep now without doing something :P > > please, be my guest :) > > > 2) Update the one click image to use latest cog images and "pharo prepared vms". There are some issues regarding this... > 3) Write down all the things/summary done in Pharo 1.2 > 5) Update SystemVersion current -->> Pharo1.2rc2 of 27 January 2011 update 12340 > 6) Condense sources? condense changes? #cleanUpForRelease > > Cheers > > Mariano > > >

March 13, 2011

Re: [Pharo-project] the glamorous toolkit project

by StÃ©phane Ducasse

On Mar 13, 2011, at 2:34 PM, Marcus Denker wrote: > > On Mar 13, 2011, at 2:05 PM, Tudor Girba wrote: > >> I think that this is a good idea. Having the Core tools better is definitely a good thing. >> > > One thing to keep in mind is that we need (ass soon as possible) to have *one* set > of tools... with OB we have seen that we have just not the manpower to in parallel > maintain two sets of tools (Core vs. Dev). > > The notion of "Core Tools" is broken. Whichever tools we do in the future need > to *replace* the old tools. Yes we are working on it. We started to rebuild the finder, the recentmessage list. Now we just go at the speed we can afford to have. Stef > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

March 13, 2011