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

[Pharo-project] Issue 3965 in pharo: Turn off Smart Characters in Full Image by default

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2.2-DevImage New issue 3965 by marcus.d...(a)gmail.com: Turn off Smart Characters in Full Image by default http://code.google.com/p/pharo/issues/detail?id=3965 .. because they make it very hard to type for many people

April 5, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Alexandre Bergel

Running the all unit test is probably a better benchmark. Alexandre On 5 Apr 2011, at 07:56, Igor Stasenko wrote: > VariableNode initialize. > Compiler recompileAll. > > [ > TestCase allSubclasses do: [ :cls| > cls isAbstract > ifFalse: [cls suite run]]. > ] timeToRun > > 178938 > 183963 > > > > (ParseNode classVarNamed: 'StdSelectors') removeKey: #class ifAbsent: []. > Compiler recompileAll. > > [ > TestCase allSubclasses do: [ :cls| > cls isAbstract > ifFalse: [cls suite run]]. > ] timeToRun > > 187168 > 184992 > > the deviation is too big to see if its really so big overhead. > > if you compare worst , you got 187/178 ~ 5% > and if you compare the best you got > 184/183 ~ 0.5% > > > -- > Best regards, > Igor Stasenko AKA sig. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 5, 2011

Re: [Pharo-project] Status of Weak enhancements in Pharo

by Miguel CobÃ¡

Ok, thanks. I was reviewing the Magma code (not working yet in Pharo 1.2, sadly) and found several checks for new finalization code before execution some parts of magma. So, as Chris said that Magma 1.2 is the only supported version (no support for old versions), then I thought that I should remove the checks given that Squeak 4.2 and Pharo 1.2 already have the new finalization code. Cheers El mar, 05-04-2011 a las 09:37 +0200, Igor Stasenko escribiÃ³: > On 5 April 2011 06:30, Miguel CobÃ¡ <miguel.coba(a)gmail.com> wrote: > > What is the status of the Weak enhancements that were applied to Squeak > > 4.2 (by Levente and Igor, mainly) and were targeted for inclusion in > > Pharo? Is there a list of them somewhere? which ones are integrated and > > which ones are not yet? > > > > Yes, they are already in Pharo. > > To check if you running VM which supports new finalization, use: > > WeakFinalizationList hasNewFinalization > > > Other question, is the plan to take the enhancements as they are and > > apply them on Pharo, that is, the versions in Squeak are the reference > > or there are conflicting versions in Pharo that are to be keep instead. > > I remember that some changes were made to Pharo in this regard. > > > > Do not worry about it. We reviewed the code with Stephane, before > integrating it. It was back in Dec 2010 (if i remember). > > > > > Cheers > > -- > > Miguel CobÃ¡ > > http://twitter.com/MiguelCobaMtz > > http://miguel.leugim.com.mx > > > > > > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

April 5, 2011

Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy

by Alexandre Bergel

Hi Guys, Maybe I missed part of the discussion, but what is Nautilus? Squeaksource simply says "A new browser" Cheers, Alexandre On 5 Apr 2011, at 08:32, Fernando Olivero wrote: > Hi Ben, i was thinking about the discussion of the menus: > > Since you are using menu pragma builder, and have explicit views for > each tool, then the CodeHolder hierarchy is no longer needed. Because > the specialized views get the behavior for answering the actions in > the menus (which currently is spread across the StringHolder > hierarchy). > > So this is the main reason why you simple need a pluggable text model, > for the model of the views. And a pluggable TextModel (or StringHolder > in Pharo) would suffice? Is this correct? > > Thanks, > Fernando > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 5, 2011

Re: [Pharo-project] syntax highlighting for (stateful) traits (non-local methods)

by Toon Verwaest

Yes, I read those two things too... but it doesn't seem like a giant leap of an improvement :) On 04/05/2011 02:34 PM, Alexandre Bergel wrote: > I remember Fred has lazy initialization of variable. All variables are lazy initialized. This means that variables set to nil when you change the class are lazy initialized. > It has been a long time I looked at it. > > Alexandre > > > On 4 Apr 2011, at 16:32, StÃ©phane Ducasse wrote: > >> In fact he got a better changeClassToThatOf: implementation and got kind of initform for slots. >> >> Stef >> >> >>> I do read French too, no problem. >>> >>> I'm having a look at >>> >>> http://fredrivard.ifrance.com/fredrivard/pub/dicl/dicl.ps >>> >>> That seems related. >>> >>> On 04/04/2011 09:20 PM, Alexandre Bergel wrote: >>>> he he. I am not sure Fred wrote in English. >>>> http://scg.unibe.ch/scgbib?_k=qQPhJdNf&query=rivard >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> >>>> On 4 Apr 2011, at 14:15, Toon Verwaest wrote: >>>> >>>>> Do you have an exact reference on this? >>>>> >>>>> On 04/04/2011 05:55 PM, StÃ©phane Ducasse wrote: >>>>>>> Another very cool thing that we can do now (which would require 3 lines of change in my system though), is that the slot can also be responsible for instance migration. There are four cases: >>>>>>> 1- the instance variable didn't exist and now it does >>>>>>> 2- the instance variable existed but disappeared >>>>>>> 3- the metaobject changed (new semantics) >>>>>>> 4- the metaobject stayed the same >>>>>>> >>>>>> Did you check the work of fred rivard because he was managing the dynamic change of class and managing slot reinitialization? >>>>>> >>>>>> >>>>>>> Basically the only case that is "handled" by standard Pharo is case 1; and what you do there is putting nil in the field. In our model the slot could do something more interesting when it's migrating the instances. And we could tackle the other cases too. I think it's starting to get ideal to implement an active context on top ;-) >>>>>>> >>>>>>> cheers, >>>>>>> Toon >>> >>

April 5, 2011

Re: [Pharo-project] Issue 3105 in pharo: DeepCopier warnIverNotCopiedIn:sel: dependent on ToolSet

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3105 by marcus.d...(a)gmail.com: DeepCopier warnIverNotCopiedIn:sel: dependent on ToolSet http://code.google.com/p/pharo/issues/detail?id=3105 in 13133

April 5, 2011

Re: [Pharo-project] Issue 3964 in pharo: Enabling double click on PluggableListMorphOfMany

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.3 Comment #1 on issue 3964 by marcus.d...(a)gmail.com: Enabling double click on PluggableListMorphOfMany http://code.google.com/p/pharo/issues/detail?id=3964 in 13133

April 5, 2011

[Pharo-project] [update 1.3] #13133

by Marcus Denker

13133 ----- Issue 3955: Better implementation of the MorphTreeMorph auto select Issue 3956: Better implementation of the PluggableListMorphs auto select Issue 3964: Enabling double click on PluggableListMorphOfMany Issue 3105: DeepCopier warnIverNotCopiedIn:sel: dependent on ToolSet -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 5, 2011

Re: [Pharo-project] Issue 3956 in pharo: Better implementation of the PluggableListMorphs auto select

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3956 by marcus.d...(a)gmail.com: Better implementation of the PluggableListMorphs auto select http://code.google.com/p/pharo/issues/detail?id=3956 in 13133

April 5, 2011

Re: [Pharo-project] Issue 3955 in pharo: Better implementation of the MorphTreeMorph auto select

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3955 by marcus.d...(a)gmail.com: Better implementation of the MorphTreeMorph auto select http://code.google.com/p/pharo/issues/detail?id=3955 in 13133

April 5, 2011