- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [squeak-dev] Re: usability of Pharo and Squeak
by Marcus Denker June 3, 2011

June 3, 2011

On Jun 2, 2011, at 8:32 PM, Andreas Wacknitz wrote: > > The quality of the code and Smalltalk's elegance and kind of OO are only seen after the first hurdle is being taken. The "slice" where you can see this elegance is actually very thin. First people are put off by the look. And *if* you see the beauty of the language and dig deeper, you see the implementation of the rest of the system. Elegance is something else. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] SimpleWebDoc
by GastÃ³n Dall' Oglio June 2, 2011

June 2, 2011

What about the current state of http://www.squeaksource.com/SimpleWebDoc.html ?

2 2

[Pharo-project] CommandShell on 1.2
by Sean P. DeNigris June 2, 2011

June 2, 2011

On 1.2.2-12353 dev with the Mac 4.2.5 VM, evaluating: ExternalCommandShell open. produces: NonBooleanReceiver: proceed for truth from BufferedAsyncFileReadStream>>moveAvailableDataFrom:. It seems that primTestEndOfFileFlag: is returning nil Bug report... 2 June 2011 5:36:59 pm VM: Mac OS - intel - 1067 - Squeak4.1 of 17 April 2010 [latest update: #9957] Squeak VM 4.2.5b1 Image: Pharo1.2.2 [Latest update: #12353] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir /Users/sean/Squeak/Fresh Images/Pharo-1.2.2-12353 Trusted Dir /foobar/tooBar/forSqueak/bogus Untrusted Dir /Users/sean/Library/Preferences/Squeak/Internet/My Squeak UndefinedObject(Object)>>mustBeBooleanIn: Receiver: nil Arguments and temporary variables: context: BufferedAsyncFileReadStream>>moveAvailableDataFrom: proceedValue: nil Receiver's instance variables: nil UndefinedObject(Object)>>mustBeBoolean Receiver: nil Arguments and temporary variables: Receiver's instance variables: nil BufferedAsyncFileReadStream>>moveAvailableDataFrom: Receiver: BufferedAsyncFileReadStream: 'stdin' Arguments and temporary variables: sqFile: #[52 145 119 159 32 218 140 160 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0] bufferSize: 1000 buffer: ' -- View this message in context: http://forum.world.st/CommandShell-on-1-2-tp3569478p3569478.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

[Pharo-project] [update 1.3] #13238
by StÃ©phane Ducasse June 2, 2011

June 2, 2011

13238 ----- - Issue 4330: text DPI notification. Thanks Pavel Krivanek. http://code.google.com/p/pharo/issues/detail?id=4330 - Issue 4333: PharoKernel part 21. Thanks Pavel Krivanek. http://code.google.com/p/pharo/issues/detail?id=4333 - Issue 4332: StartupUIManager is Morphic dependent. Thanks Pavel Krivanek. http://code.google.com/p/pharo/issues/detail?id=4332 Stef

1 0

[Pharo-project] Scratch on Pharo
by Hilaire Fernandes June 2, 2011

June 2, 2011

It's an extremely nice move to keep the babies at home http://smalltalk.cat/blog/Scat+-+Communiqu%E9 Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

2 1

[Pharo-project] TilingWM - layout policies
by laurent laffont June 2, 2011

June 2, 2011

Thanks to Stefan, Serge, Patrick and Estelle now you can choose a Layout Strategy in settings. Actually there's Horizontal (default) and Vertical (last used windows fills all remaining space) strategies. To add your own just subclass TWMLayoutStrategy and implement #tileWindows: Cheers, Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

5 5

[Pharo-project] I am serializing correctly with SIXX?
by Mariano Martinez Peck June 2, 2011

June 2, 2011

>> serialize: anObject on: aStream | sws | sws := SixxWriteStream on: aStream. sws nextPut: anObject. sws close. >> materializeFrom: aStream | srs objects | srs := SixxReadStream on: aStream. objects := srs contents. srs close. ^ objects Is that correct or I am doing it wrong? All I want to do is to serialize a graph into a stream. The stream I am using is or this: (FileDirectory default forceNewFileNamed: 'Bench') or (RWBinaryOrTextStream on: '') I am not sure if I should be doing a #nextPut: or a #nextPutAll:. I mean, sometimes anObject is a collection and sometimes it is not. So, which one should I use? Thanks Mariano -- Mariano http://marianopeck.wordpress.com

3 9

[Pharo-project] creating KOTDC
by GastÃ³n Dall' Oglio June 2, 2011

June 2, 2011

What do you think about creating this?: *Know Of The Day Contest - One Day One Know Rules Each day a not known project is elected. Each day the know will be readed and the project know for more people.* In reality this would not be a contest (which would not be the criterion for selecting the winner:), but rather a sharing by its ideologues, developers, users, critics (why not?) and general interest groups, about the characteristics of a project that is unknown in general. The idea is to focus on those projects that are not so widely known, in which are already widely known does not make sense. For example about these people who have been named to the list recently: Gettext package TestConsoleRunner http://www.squeaksource.com/Mocketry.html http://www.squeaksource.com/Keymapping.html http://www.squeaksource.com/TilingWindowManager

6 7

[Pharo-project] [update 1.3] #13237
by Marcus Denker June 2, 2011

June 2, 2011

13237 ----- Issue 4336: deprecated MorphicTextEditor http://code.google.com/p/pharo/issues/detail?id=4336 Issue 4335: Remove more methods that are the same already in the superclass http://code.google.com/p/pharo/issues/detail?id=4335 Issue 4334: Travial cleanup: some (to:)do: --> to:do http://code.google.com/p/pharo/issues/detail?id=4334 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] A newly discovered Metacello bug (yet to be characterized)
by Dale Henrichs June 2, 2011

June 2, 2011

In the mail to Lukas below, I was able to identify a previously unreported bug in Metacello1.0-beta.28.3.3 when loading Seaside3.0.5 into Pharo1.2-12339. In the process of characterizing the bug, I discovered that the Seaside load was correct when using Metacello 1.0-beta.29 (an unreleased version). However, when I tested Seaside3.0.5 and Metacello1.0-beta.29 using Pharo1.2.2-12353, I discovered more odd behavior and Seaside3.0.5 hit errors during the load. There is something fishy going on and at this point in time the root cause is not obvious. The Metacello unit tests are passing in all three versions: Pharo1.2-12339, Pharo1.2.1-12345 and Pharo1.2.2-12353. I am now in the process of attempting to characterize the bugs. I will keep you posted on my progress. Dale ----- Original Message ----- > Lukas, > > I have looked specifically at Seaside3.0.5 and > Pharo1.2-12339/PharoCore1.2-12336 > and have found two things: > > 1. #stable version for ConfigurationOfOmniBrowser for 1.2 is 1.2.3 > and it should be 1.2.4. > 2. if OB 1.2.4 is already loaded then the version is downgraded to > 1.2.3 > > Item #1 is a configuration issue and item #2 is a bug ... > > I had not heard that "many projects could no longer be loaded into > Pharo1.2", so I was (and still am) blissfully unaware of the > problems that folks are having. > > Seaside3.0.5 loads into Pharo1.2/PharoCore1.2 and passes all of the > unit tests ... so there are no "load issues." The Seaside control > panel works fine and I have not noticed any other > OmniBrowser-related issues ... but then I don't live in the images > day in and day out so there could be subtle issues. > > I am currently trying to characterized the "downgrade version" bug > and will push out a fix as soon as I have one. > > Dale > > > ----- Original Message ----- > > > Here's the current state of 3.0.5: I saved the images from > > > Jenkins > > > and > > > uploaded them to the web site. The change log has also been > > > updated > > > [1]. Everything but the Metacello configuration seems to work > > > fine. > > > If > > > I load the Metacello configuration into a Pharo 1.2 it tries to > > > load a > > > version of OB that does not work in Pharo 1.2. > > > > As far as I know most configurations have been updated to Pharo 1.3 > > already and many projects (I learned that with Glamour, Mondrian, > > Moose, Spy, ...) cannot be loaded into latest stable (Pharo 1.2) > > anymore. What surprised me more is that Metacello does not allow to > > load old versions (at least this is true for the configurations I > > had > > problems with). So I guess we have the same problem here. > > > > I suggest that you load OB with this script: > > https://github.com/renggli/builder/blob/master/scripts/omnibrowser.st > > > > Lukas > > > > -- > > Lukas Renggli > > www.lukas-renggli.ch > > _______________________________________________ > > seaside-dev mailing list > > seaside-dev(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >

1 3