October 2008 - Pharo-dev - lists.pharo.org

[Pharo-project] More full screen refactoring
by Michael Roberts Oct. 4, 2008

Oct. 4, 2008

Hi Marcus, issue: 186, I'm not sure why fullScreen.2.cs did not work? Can you check SLICE-fullScreenRefactoring-mike.roberts.1 in the inbox. thanks, Mike

2 2

[Pharo-project] [update] 10086
by Marcus Denker Oct. 4, 2008

Oct. 4, 2008

Issue 214: [enh] executeMethod via primitives - moves the *executeMethod: method to protoObject - uncomments the commented primitive for faster execution Issue 211: undeclared fix for 10084 - fixes one remaining reference to CurrentProjectRefactoring Issue 210: [ENH] CompiledMethod explorer Issue 206: [ENH] simplify unreferencedInstanceVariables, allUnreferencedInstanceVariables - add test for and simplify Behavor>>#whichSelectorsAccess: - simplify Behavior>>#unreferencedInstanceVariables - simplify and remove #isDoIt check from Behavior>>#allUnreferencedInstanceVariables Issue 196: remove #hash from Association Issue 212: random cleans - KillNewWorld: remove class NewWorldWindow - InspectorTileRemove: remove the menus from inspector for tiles - delPlayerSurrogate.1: remove class PlayerSurrogate - CleanExplanation: remove more code related to the "explain" functionality - UnsentMessages: remove some unsent messages Postscript: Vocabulary allStandardVocabularies removeKey: #unknown. PartsBin allInstances do: [:pb| pb submorphs do: [:sm| (sm target name=#AnObsoleteGeeMailMorph) ifTrue: [ pb removeMorph: sm ]]]. Preferences removePreference: #thoroughSenders. Preferences removePreference: #dragNDropWithAnimation. Set rehashAllSets. -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

3 3

Re: [Pharo-project] [update] 10086
by Bill Schwab Oct. 4, 2008

Oct. 4, 2008

Hello all, I have no idea on the answer to Mike's question, but this reminds me of an RB problem that arose in Dolphin. I do not recall the circumstances, but the _instance_ variables were being sorted (alphabetical order IIRC), which is really bad given the way Dolphin's STB (serialization) relies on iv order. OA fixed it long ago. Bottom line: the order of instance variables might be important, and IMHO should not be changed unless the programmer does or requests it. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> mike(a)mjr104.co.uk 10/04/08 7:53 AM >>> I've update to 10086, but when I was going to publish some new changes I have noticed differences between my image and the repository. e.g BalloonMorph, MenuMorph, StandardScriptingSystem, SystemProgressBarMorph all have their classVariables reversed. This expected? thanks, Mike On Sat, Oct 4, 2008 at 9:00 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Neatttttttttt! > > As soon as I have finish with my floor (somebody asked me what it was: > removing the wood layer, hooving the dust, putting wollrock, painting with > xylophene, reputting the wood) > I will really extract etoy :) > then gary fixes and check keith kernel extensions > > Stef > > On Oct 3, 2008, at 10:19 PM, Marcus Denker wrote: > >> Issue 214: [enh] executeMethod via primitives >> - moves the *executeMethod: method to protoObject >> - uncomments the commented primitive for faster execution >> Issue 211: undeclared fix for 10084 >> - fixes one remaining reference to CurrentProjectRefactoring >> Issue 210: [ENH] CompiledMethod explorer >> Issue 206: [ENH] simplify unreferencedInstanceVariables, >> allUnreferencedInstanceVariables >> - add test for and simplify Behavor>>#whichSelectorsAccess: >> - simplify Behavior>>#unreferencedInstanceVariables >> - simplify and remove #isDoIt check from >> Behavior>>#allUnreferencedInstanceVariables >> Issue 196: remove #hash from Association >> Issue 212: random cleans >> - KillNewWorld: remove class NewWorldWindow >> - InspectorTileRemove: remove the menus from inspector for tiles >> - delPlayerSurrogate.1: remove class PlayerSurrogate >> - CleanExplanation: remove more code related to the "explain" >> functionality >> - UnsentMessages: remove some unsent messages >> >> Postscript: >> >> Vocabulary allStandardVocabularies removeKey: #unknown. >> PartsBin allInstances do: [:pb| pb submorphs do: [:sm| (sm target >> name=#AnObsoleteGeeMailMorph) ifTrue: [ pb removeMorph: sm ]]]. >> Preferences removePreference: #thoroughSenders. >> Preferences removePreference: #dragNDropWithAnimation. >> Set rehashAllSets. >> >> -- >> Marcus Denker -- denker(a)iam.unibe.ch >> http://www.iam.unibe.ch/~denker >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] Linux VM with FreeType and closure bytecodes
by bryce＠kampjes.demon.co.uk Oct. 4, 2008

Oct. 4, 2008

http://ftp.squeak.org/Exupery/vms/pharo-vm.tz It's got both FreeType and Eliot's closure bytecodes. It's fully compatable with normal VMs. It can also run the latest Exupery from SqueakSource. You could use this VM to run Squeak 3.10, just for the sub-pixel anti-aliasing. I'm still working on automating the image building for rebuilding the VM. I'd also like to get automake to find the locations of the FreeType headers so the VM is more likely to build on other distros where the locations may be different. Bryce P.S. Please shout when there's an image built which uses the closure bytecodes.

3 4

[Pharo-project] iphone squeak vm 1.05b4
by John M McIntosh Oct. 3, 2008

Oct. 3, 2008

I've push out the source code and placed a 1.05b4 iPhone VM on my ftp site. This VM includes a fix to ensure equalTo: uses the correct Objective-C method so that all the SUnit tests now pass when running it via the ObjectiveCPlugin.bundle under OS-X, or within the iPhone VM. I note the 1.0.5b3 and 1.0.5b4 VMs use a different squeak image that includes an VNC server, this allows you to interact with the VM from a VM client and have full keyboard/mouse control within the image from your VNC client.

1 0

[Pharo-project] Save and quit menu
by Mathieu Suen Oct. 3, 2008

Oct. 3, 2008

Hi, From the latest pharo image the Save and quit menu have disappear. Is there any reason for removing it. I always use it so I found annoying to first click quit and then answer the question... Mth ___________________________________________________________________________ Yahoo! Mail rï¿½invente le mail ! Dï¿½couvrez le nouveau Yahoo! Mail et son interface rï¿½volutionnaire. http://fr.mail.yahoo.com

2 1

[Pharo-project] Fonts related from OLPC / rome also
by StÃ©phane Ducasse Oct. 3, 2008

Oct. 3, 2008

I started to go over http://tinlizzie.org/updates/etoys/updates to see if some of the fixes of yoshiki for unicode and others were there. Here is a list of names that may be should be further investigated - 1622fontFix-sw.cs - 1626FontNameGlitch-y.. - 1711UTF8Clipboard.cs - 1712utf8toSqueakFix-. - 1713UnicodeInput1-yo.cs - 1714UnicodeInput2-yo.cs - 1715utf8toSqueakFix2..> - 1725SystemFont-yo.cs - 1726SystemFont2-yo.cs - 1731UpdBtnFontFix-KR.cs - 1813macPasteUTF8-bf.cs - 1815latin1Chars-yo.cs - 1821UnicodeFntLoadin..> - 1826TTCFontSetRework..> - 1826TTCFontSetRework..> - 1827sketchColor-sw.cs - 1832TTCFontSetFix-yo.cs -1834FontRegFix-yo.cs - 1862TTCFontObjStream..> - 1869latin1PathEncodi..> - 1884TTObjForStream-y.. - 1907crlfFix-bf.cs - 1918UTF8InputFix-ar.cs - 1925unixLatin1Input-..> - 1935unicodeFallback-. - 2143macEnc-bf.cs about the rome canvas 1932romepango-base.cs 1933romepango.cs 1934romepango2-yo.cs 24

2 3

[Pharo-project] Fwd: Yet another Objective-C bridge
by John M McIntosh Oct. 3, 2008

Oct. 3, 2008

Begin forwarded message: > From: John M McIntosh <jmmcintosh(a)gmail.com> > Date: October 2, 2008 11:50:56 PM PDT (CA) > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > Cc: iSqueak(a)isqueak.org > Subject: Yet another Objective-C bridge > Reply-To: johnmci(a)smalltalkconsulting.com > > As part of my iPhone work I've built yet another Objective-C bridge. > > It can be found within ftp://ftp.smalltalkconsulting.com/experimental/ > The required Smalltalk code for the basic logic, the SUnits, and the > Plugin generation can be loaded from http://www.squeaksource.com/ObjectiveCBridge2.html > The additional pieces required to build the plugin are found within > the iSqueak SVN tree. http://svn.isqueak.org/vm/ > > Using aregular 3.8.18b4U macintosh carbon VM with the > ObjectiveCBridge installed means you can invoke. > > testRetainCount > | classOop instance1 count | > > classOop := ObjectiveCObject findClassName: 'NSObject'. > instance1 := classOop new. > count := instance1 retainCount. > self should: [count = 1]. > instance1 retain. > count := instance1 retainCount. > self should: [count = 2]. > instance1 release. > count := instance1 retainCount. > self should: [count = 1]. > > > People are welcome to confirm that it works, although it is compiled > for ppc and i386 (32bit) I have not yet tested on ppc. > > This plugin was also installed for the currently shipping iPhone VM > 1.05b3, however there seems to be a problem > where resolving the method signature object isEqualTo: for usage > between two instances of NSObject returns nil. > But only on an ipod touch or iPhone not in the Simulator, or running > as an os-x application. > > > >

1 0

[Pharo-project] How to integrate Kernel-Extensions
by Damien Pollet Oct. 3, 2008

Oct. 3, 2008

Hi list, we (with Stef) are browsing Kernel-Extensions, here are some notes for discussion, as we think there is stuff that should be merged in Pharo. Null and Split-Join could be packaged on their own since they are well-defined features. Most of the cleanup methods make sense, but what's the difference between cleanUp and freeSomeSpace ? AppRegistry class >> removeObsolete "AppRegistry removeObsoleteClasses" self registeredClasses copy do:[:cls| (cls class isObsolete or:[cls isBehavior and:[cls isObsolete]]) ifTrue:[self unregister: cls]]. self subclasses do:[:cls| cls removeObsolete]. Behavior class >> flushObsoleteSubclasses "Behavior flushObsoleteSubclasses" ObsoleteSubclasses finalizeValues. Behavior >> sourceMatchesBytecodeAt: Class class >> freeSomeSpace "Fix some problems with classes. Use Smalltalk allClassesDo: since it does not use the subclass list, which we may be modifying during this iteration" Smalltalk allClassesDo: [:ea | ea fixObsoleteSuperclass. ea removeDuplicateSubclassEntries] Collection >> contains: should probably be standardized as part of the STEPS project Collection >> reject:thenDo: and select:thenDo: should be included and similar enumerations reimplemented in this way too SystemDictionary >> forgetClass: aClass logged: aBool badly named but interesting "Delete the class, aClass, from the system. Note that this doesn't do everything required to dispose of a class - to do that use Class>>removeFromSystem." aBool ifTrue: [SystemChangeNotifier uniqueInstance classRemoved: aClass fromCategory: aClass category]. SystemOrganization removeElement: aClass name. self removeFromStartUpList: aClass. self removeFromShutDownList: aClass. self removeKey: aClass name ifAbsent: []. DataStream classRemoved: aClass. self flushClassNameCache SystemDictionary >> globals needs to pay attention that compiled methods share the associations Number >> to: stop do: aBlock displayingProgress: aString would be probably nicer with the block argument last === To discuss: Collection >> removeAll: comment should explain in which cases it is useful "the slow way" ^ self removeAllSuchThat: [ :each | true ] SequenceableCollection >> <= smells funnyâ¦ what is it useful for ? SequenceableCollection >> replacing:with: replaces in place, not obvious from the name the stream methods like putOn: â¦ convenience ? are they coherent ? String >> withoutTrailing: probably makes sense but then this is mostly useful for line breaksâ¦ why not a #trimLinebreak Set >> likeOrAdd: ok but then that should be available for any collection (and renamed addIfAbsent:) "Include newObject as one of the receiver's elements, but only if not already present. Answer the oldObject." === Useless: ProtoObject >> iconOrThumbnailOfSize: Object >> askFor: and askFor:ifDefault: that's a workaround Object >> deprecated is already here Object >> log should be packaged in a logging package since it's a convenience method SequenceableCollection >> copyReplacing:with: just to type one space less ? -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

8 12

Oct. 3, 2008

Hi marcus did you harvest ? Name: Kernel-dc.198 Author: dc Time: 28 September 2008, 4:00:03 pm UUID: 3b2eeec4-6461-4d22-94d1-e7f692e7e177 Ancestors: Kernel-marcus.denker.197 - M7166: speedup allSelectors add allSelectorsBelow:. Firstly #allSelectors inefficiently creates multiple intermediate collections. Refactoring this yields a 27% speed improvement. Secondly many users of #allSelectors forget that when applied to the class side it doesnt stop at ProtoObject class, it continues to Class ClassDescription, Behavior, Object and ProtoObject. This is catered for by adding #allSelectorsBelow: Magritte and SUnit are heavy users which benefit. I imagine not so I will.

2 2