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

Re: [Pharo-project] Don't you think "Windows" menu item should be with the rest?

by Sean Allen

I had to go look and see what was in it. On Fri, Apr 29, 2011 at 8:26 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > Just to wonder. How many of us use the windows options? I have never used > them. > > Cheers, > Alexandre > > > On 29 Apr 2011, at 18:40, Mariano Martinez Peck wrote: > > > Right now, there is a special section for "Windows", but I think it is > easier if it is together with Help, System, Tools, etc. > > I attach a screenshot. > > > > In addition, it changed the order in compare with Pharo 1.2 where it was: > > > > Tools > > Windows > > System > > Help > > > > What do you tink ? > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > <Pharo 1.2.png><Pharo 1.3.png> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > >

April 30, 2011

Re: [Pharo-project] Don't you think "Windows" menu item should be with the rest?

by Alexandre Bergel

Just to wonder. How many of us use the windows options? I have never used them. Cheers, Alexandre On 29 Apr 2011, at 18:40, Mariano Martinez Peck wrote: > Right now, there is a special section for "Windows", but I think it is easier if it is together with Help, System, Tools, etc. > I attach a screenshot. > > In addition, it changed the order in compare with Pharo 1.2 where it was: > > Tools > Windows > System > Help > > What do you tink ? > > -- > Mariano > http://marianopeck.wordpress.com > > <Pharo 1.2.png><Pharo 1.3.png> -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 30, 2011

[Pharo-project] squeaksource Seaside30 repo out of sync

by Yanni Chiu

When I look at the latest version of Seaside-Tests-Core at squeaksource.com, and when I look at the repo in-image in a Metacello browser, the latest version is: Seaside-Tests-Core-lr.219 However, version 305 of ConfigurationOfSeaside30 lists the version as: Seaside-Tests-Core-as.220 I cannot see the "as.220" version. Also, the build at http://jenkins.lukas-renggli.ch/job/Seaside%203.0/ seems to have picked up the "as.220" version. But I don't see ConfigurationOfSeaside30 being used to build that image. Does anyone else see the same thing, or know what's going on?

April 30, 2011

[Pharo-project] HelpBrowser takes too much time to open

by Torsten Bergmann

This is because the help book "Pharo" includes an API reference for the WHOLE system (starting from ProtoObject all subclasses down) and converts all class comments in the system into help text. Accessing sources is slow... Just run MessageTally spyOn: [SystemReference asHelpTopic] If nobody uses this full API reference then we can eliminate the class "PharoAPIHelp" and it should be much faster (from 3705 down to 1006 in my image). Other books like the ones on announcements and on regular expression also contain an API reference ... but only with classes for these packages. Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

April 30, 2011

Re: [Pharo-project] [Pharo-users] [COTDC] 56 - HostFont

by Chris Cunningham

"Uses host fonts from a Win32 system for display. On a Windows system, if you have FontPlugin.dll with your executable, execute HostFont initWin32 Then, you should be able to use fonts from a variety of native Windows fonts of various sized and emphasis." Except, of course, for the bugs. I can't actually choose one due to some issue with IdentityGlyphMap. And, Pharo isn't shipped with the dll (I don't think) - so I picked on up from Squeak 3.8, the last time I used HostFonts (for a month or so). There are currently a lot of additional candidates for what this does. -Chris

April 29, 2011

[Pharo-project] Don't you think "Windows" menu item should be with the rest?

by Mariano Martinez Peck

Right now, there is a special section for "Windows", but I think it is easier if it is together with Help, System, Tools, etc. I attach a screenshot. In addition, it changed the order in compare with Pharo 1.2 where it was: Tools Windows System Help What do you tink ? -- Mariano http://marianopeck.wordpress.com

April 29, 2011

[Pharo-project] HelpBrowser takes too much time to open

by Mariano Martinez Peck

MessageTally time: [HelpBrowser open] between 2 seconds in Cog and with a regular VM between 6 and 8.... is there an easy way to improve it ? Alexandre, do you want another place where to put a cache like Metacello's currentVersion? ;) Cheers -- Mariano http://marianopeck.wordpress.com

April 29, 2011

Re: [Pharo-project] DBXTalk (SqueakDBX) goes to Pharo 1.3

by Alexandre Bergel

Excellent! Keep going! Alexandre On 29 Apr 2011, at 16:41, Mariano Martinez Peck wrote: > Hi. This is just to let you know that SqueakDBX (soon DBXTalk) has 100% green tests in Pharo 1.3 without chaning one single line of code. In addition, half of the team is using Pharo 1.3 and the other one 1.2. > > We updated ConfigurationOfSquealDBX >> #stable > > Cheers > > -- > Mariano > http://marianopeck.wordpress.com > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 29, 2011

Re: [Pharo-project] UndefinedObject(Object)>>doesNotUnderstand: #findNextHandlerContextStarting

by Marcus Denker

On Apr 29, 2011, at 11:23 PM, Mariano Martinez Peck wrote: > > > > > So I added the DebuggerMethodMap intialize (reset the cache) to Smalltalk cleanUp. > > > > > > Thanks Marcus. I don't see this commit. Did you commit it? or we lost it with the squeaksource down ? > > > This was part of the cleanUp improvements... some time ago. > > see DebuggerMethodMap>>#cleanUp > > > ok...after looking for a while, it is never called when you do > Smalltalk cleanUp: true except: #() confirming: false. > > I think it is because such method does: > > "Find all classes implementing #cleanUp or cleanUp:" > classes := Smalltalk allClasses select: [:aClass| > (aClass class includesSelector: #cleanUp) > or: [aClass class includesSelector: #cleanUp:]]. > > it checks for both messages, #cleanUp: or #cleanUp > > But then, it does: > > "Run the cleanup code" > classes > do:[:aClass| aClass cleanUp: aggressive] > displayingProgress: [:aClass| 'Cleaning up in ', aClass name]. > > > In your case, DebuggerMethodMap only implements #cleanUp, hence it is never called. > But there is in Behavior: cleanUp: aggressive "Clean out any caches and other state that should be flushed when trying to get an image into a pristine state. The argument should be used to indicate how aggressive the cleanup should be. Some subclasses may act differently depending on its value - for example, ChangeSet will only delete all unused and reinitialize the current change set if we're asking it to be aggressive." ^self cleanUp So it calls cleanUp even when you do Smalltlak cleanUp: true. Now I wonder if we should remove the displayingProgress and do the call to #cleanUp (the non-agressive one) on image save.... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 29, 2011

Re: [Pharo-project] UndefinedObject(Object)>>doesNotUnderstand: #findNextHandlerContextStarting

by Mariano Martinez Peck

> > > > So I added the DebuggerMethodMap intialize (reset the cache) to Smalltalk > cleanUp. > > > > > > Thanks Marcus. I don't see this commit. Did you commit it? or we lost it > with the squeaksource down ? > > > This was part of the cleanUp improvements... some time ago. > > see DebuggerMethodMap>>#cleanUp > > ok...after looking for a while, it is never called when you do Smalltalk cleanUp: true except: #() confirming: false. I think it is because such method does: "Find all classes implementing #cleanUp or cleanUp:" classes := Smalltalk allClasses select: [:aClass| (aClass class includesSelector: #cleanUp) or: [aClass class includesSelector: #cleanUp:]]. it checks for both messages, #cleanUp: or #cleanUp But then, it does: "Run the cleanup code" classes do:[:aClass| aClass cleanUp: aggressive] displayingProgress: [:aClass| 'Cleaning up in ', aClass name]. In your case, DebuggerMethodMap only implements #cleanUp, hence it is never called. Cheers -- Mariano http://marianopeck.wordpress.com

April 29, 2011