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

[Pharo-project] [update 2.0] #20022
by Marcus Denker April 27, 2012

April 27, 2012

20022 ----- Issue 5633: Cleaning addUpdating: wordingSelector target: target selector: aSymbol argumentList: argList http://code.google.com/p/pharo/issues/detail?id=5633 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 2.0] #20021
by Marcus Denker April 27, 2012

April 27, 2012

20021 ----- Issue 5584: File Browser not recognizing cs and st if filename has more than one point http://code.google.com/p/pharo/issues/detail?id=5584 Issue 5714: VersionsBrowser for human beings http://code.google.com/p/pharo/issues/detail?id=5714 Issue 5646: use a dictionary instead of caseOf: http://code.google.com/p/pharo/issues/detail?id=5646 -- Marcus Denker -- http://marcusdenker.de

2 1

[Pharo-project] [update 2.0] #20020
by Marcus Denker April 27, 2012

April 27, 2012

20020 ----- Issue 5675: Easy fix in DropListMorph http://code.google.com/p/pharo/issues/detail?id=5675 Issue 5642: better tempNamed: http://code.google.com/p/pharo/issues/detail?id=5642 Issue 5594: ClassOrganizer use printString for changeSet http://code.google.com/p/pharo/issues/detail?id=5594 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] remotely sharing a pharo screen
by Ben Coman April 27, 2012

April 27, 2012

I want to remotely share a Pharo screen, so can have a phone hookup with someone while are trying some things out. I have just seen VNC metioned is for remote control. Does this allow shared access to the screen? Or are the some other options cheers -ben

3 2

[Pharo-project] [update 2.0] #20019
by Marcus Denker April 27, 2012

April 27, 2012

20019 ----- Issue 5598: SHParserST80Test>>testObjectClass fails after Magritte is loaded http://code.google.com/p/pharo/issues/detail?id=5598 Issue 5621: PackageInfo extensionMethods not gathering all extensions http://code.google.com/p/pharo/issues/detail?id=5621 Issue 5660: having more handles*: for keyboard handling http://code.google.com/p/pharo/issues/detail?id=5660 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Pharo 2.0 feels great
by Sven Van Caekenberghe April 27, 2012

April 27, 2012

A quick note: I just played a little bit with Pharo 2.0 and it feels great. I really love the fact that Nautilus and some other stuff is just there. Beautiful out of the box experience ! Thanks, Sven PS: Opening the Config browser gives: 'Could not access http://www.squeaksource.com/MetaRepoForPharo20: ZnHttpUnsuccessful: 404 Not Found' the repo does not exist (yet).

1 0

[Pharo-project] [update 2.0] #20018
by Marcus Denker April 27, 2012

April 27, 2012

20018 ----- Issue 5709: #getSourceFromFile should not be called from external clients http://code.google.com/p/pharo/issues/detail?id=5709 Issue 5648: self world in HaloMorph is nil http://code.google.com/p/pharo/issues/detail?id=5648 Issue 5666: Unable to open the menu with one click mouse (again) http://code.google.com/p/pharo/issues/detail?id=5666 Issue 5619: PluggableListMorph drag/drop raise DNU http://code.google.com/p/pharo/issues/detail?id=5619 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] TestCase>>#assert:equals: optimization
by Stefan Marr April 27, 2012

April 27, 2012

Hi: While stepping through bytecodes, I noticed a slightly annoying inefficiency in the SUnit implementation. The description string in #assert:equals: is always computed, even if it is not necessary. While that might not be a performance problem, I find it rather distracting when I have to debug on the bytecode/VM level. Since there seem to be only 127 senders or so in the image, you will probably not notice a big performance gain. The change to compute the string only when necessary is below. Best regards Stefan PS: This is a resend, because the original mail seemed to have been lost, while the mailing list was down. !TestCase methodsFor: 'asserting' stamp: 'StefanMarr 3/13/2012 23:41'! assert: aBooleanOrBlock description: aStringOrBlock aBooleanOrBlock value ifFalse: [ | aString | aString := aStringOrBlock value. self logFailure: aString. TestResult failure signal: aString] ! ! !TestCase methodsFor: 'asserting' stamp: 'StefanMarr 3/13/2012 23:40'! assert: aBooleanOrBlock description: aStringOrBlock resumable: resumableBoolean | exception | aBooleanOrBlock value ifFalse: [|aString| aString := aStringOrBlock value. self logFailure: aString. exception := resumableBoolean ifTrue: [TestResult resumableFailure] ifFalse: [TestResult failure]. exception signal: aString] ! ! !TestCase methodsFor: 'asserting' stamp: 'StefanMarr 3/13/2012 23:40'! assert: expected equals: actual ^ self assert: (expected = actual) description: [self comparingStringBetween: actual and: expected] ! ! -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

4 6

[Pharo-project] [update 2.0] #20017
by Marcus Denker April 27, 2012

April 27, 2012

20017 ----- Issue 5684: Integrate famfam icons http://code.google.com/p/pharo/issues/detail?id=5684 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [ANN] ImageWriter, the SystemTracer's son
by Guillermo Polito April 27, 2012

April 27, 2012

First public push of the first step of the hazelnut GSoC project :) *In a nutshell* For those who didn't know SystemTracer (the father): It is a tool that traces a graph of objects and writes an image from it. ImageWriter is a refactored, renamed and repackaged version of SystemTracer2 with the following changes: - The image format can be provided as a parameter. - You have to provide an SmalltalkImage object as root to write the image (so in the future we can write bootstrap with this). - The object format was reified in objects. So the code is easier to understand + change, and people can learn how are our objects in memory easily :D. Right now, only 32 bit image format is supported. *Structure* - ImageWriter-Core has the image formats and the image writer in itself - ImageWriter-ObjectFormats contains objects that represent the memory layout of the objects and it's headers. - ImageWriter-Tests has some tests. *Tests done* - Only tested in Pharo-1.4 - There are specific tests written for the size and headers of the objects - Also, I've written a Pharo-1.4 image and then run the tests in the copied image. Only one failure compared to the original :) *Known Bugs :)* - WeakRegistryTest>>#testFinalizationWithOnFork is failing, and when I run it manually it works :/. In the image I use to write, it does not happen, only in the clone. - When opening the new image, the window is too small. It is not respecting the original image size. Don't know yet what is the problem. *How To Download* Gofer it squeaksource3: 'ImageWriter'; package: 'ImageWriter-Core'; package: 'ImageWriter-ObjectFormats'; package: 'ImageWriter-Tests'; load *How to Use it* HzImageWriter new format: HzCogImageFormat new; "or HzInterpreterImageFormat new" imageFileName: 'someFile.image'; onInitializeDo: [ "Some initialization?" ]; "this is optional, probably the same as an startup script, probably nonsense" writeImage: Smalltalk "Yes, we provide the our lovely global Smalltak, but any SmalltalkImage instance could be" *Next steps on this direction* - support to write an isolated image different from the host one (I'll know what I need later, hehe) - class comments! - metacello configuration - better api :) *Links* http://ss3.gemstone.com/ss/ImageWriter.html Cheers, Guille

6 8