September 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] A point about pharo: the red line
by StÃ©phane Ducasse Sept. 18, 2010

Sept. 18, 2010

Hi pharoers We want to stress something that may seem obvious for us but that can may be not for you and that people attending ESUG could discover live :) lucky them :) But you will be able to watch the video and get an idea soon. What is important is that it can explain a lot of our actions and future actions. Here is a list of statements that I tried to make short. - We do pharo because we want to create an ecosystem for companies and research/innovation. - We don't do pharo for fame and fans else we would do ruby or hard-rock. :) (ok probably ruby) - We want to build a powerful open-source community. - Every single node in the community is important. So yes you doing your little project in your corner you are important. Why? Because a community is a synergetic beast and we are all cool because the community is cool. So you are also important to us. For example if you want to give a lecture on pharo, we can help. if you want to do presentations, we can help, if you have problems/ideas let us know. - Often we do actions not because we want credit but just because somebody has to do it: seaside book, esug are to other examples of why we did pharo. Because we need a power rocking hyper cool beautifully designed system. (I know some of you think that I'm lousy and I use too much cool but this is what I mean) - We believe in strong elegant beautiful infrastructure: fix the stuff so that you can go faster to build the next one. We did that with Moose: offer to software engineering researchers a foundation to focus on problems versus rebuilding each time a clean source code meta model and importer. Infrastructure will give us the leverage to build the next generation. Stef and other pharoers

1 0

Re: [Pharo-project] [squeak-dev] Re: Morphic
by StÃ©phane Ducasse Sept. 18, 2010

Sept. 18, 2010

Yes and I would like to have a kind of MVP model. Stef On Sep 18, 2010, at 9:15 AM, Hilaire Fernandes wrote: > Le 17/09/2010 23:58, Juan Vuletich a Ã©crit : >> DeNigris Sean wrote: >>> I was doing a lot of playing with Morphic this week at ESUG in >>> Barcelona. Many people seem to really not like it and complain about >>> it, but it seems very vague i.e. they can't point to a specific >>> problem with it. >>> >>> I think it's amazingly powerful and universally misunderstood. >> >> I agree. > > > I agree too. This is also why I like so much Polymorph, it adds the > widgets layer on top of Morphic. So now we have the option to use > barebone Moprh for very special widgetries and also standard widget > provided by Polymorph. It becomes very productive to write GUI > application... > > Hilaire > > > -- > Dr. Geo, to discover geometry on Linux, Windows, MAC and XO > http://community.ofset.org/index.php/DrGeo > >

1 0

[Pharo-project] Best Spreading Smalltalk Actions
by Noury Bouraqadi Sept. 17, 2010

Sept. 17, 2010

Although the technology is important, spreading the word is also of great value to the Smalltalk community. This is why the ESUG board decided to distinguish two people for their actions on this-level: -Damien Cassou for Squeak-dev: an initiative which makes developers life easier by setting a ready to use image including best available tools. -Laurent Laffont for Pharocast: quality screencasts that illustrates various facets of http://pharocasts.blogspot.com/ Congratulations Damien and Laurent! Noury @ ESUG 2010 - Barcelona :-) --- 18th International Smalltalk Joint Conference, September 13 -17 2010 Barcelona, Spain. http://www.esug.org/Conferences/2010

5 4

[Pharo-project] ISSUE 2967: urgent do-it fix
by Fernando olivero Sept. 17, 2010

Sept. 17, 2010

Issue 2967: DoIt on a workspace doesnt work, raises a subscript out of bounds error. Fixed, removed some other methods that were added to ByteString, but belong in SmalltalkEditor. Fernando

2 1

[Pharo-project] ESUG 2010 Tech Awards Results
by Noury Bouraqadi Sept. 17, 2010

Sept. 17, 2010

Hi, Monday evening we had demos of participants. It was great and we had hard time voting. Yesterday evening we had the awards ceremony. And the winners are... -1st Physical Etoys (Squeak Etoys) â¢ Developers: Lic. Gonzalo Zabala, Ricardo Moran, SebastiÃ¡n Blanco â¢ Keywords: Visual programming, Programming Real world objects -2nd Cog (Squeak, Pharo) â¢ Developers: Eliot Miranda â¢ Keywords: Virtual machine -3rd Mars (Pharo) â¢ Developers: Esteban Lorenzano â¢ Keywords: MVC framework, native UI, OSX Videos and more info about participants and winners are on: http://www.esug.org/wiki/pier/Conferences/2010/InnovationTechnologyAwards Thanx to all participants and congratulations to the winners! Noury @ ESUG 2010 - Barcelona :-) --- 18th International Smalltalk Joint Conference, September 13 -17 2010 Barcelona, Spain. http://www.esug.org/Conferences/2010

2 1

[Pharo-project] failing/errors Pharo Tests with CogVM
by Mariano Martinez Peck Sept. 16, 2010

Sept. 16, 2010

Hi Eliot. I took a Pharo 1.1.1 image (which has included the changes to run Cog) and I run all the tests with the build r2219 And these are the results: 9768 run, 9698 passes, 53 expected failures, 15 failures, 2 errors, 0 unexpected passes Failures: FloatTest>>#testRaisedTo MCInitializationTest>>#testWorkingCopy FloatTest>>#testReciprocal ReleaseTest>>#testUndeclared FloatTest>>#testDivide MethodContextTest>>#testClosureRestart FloatTest>>#testCloseTo FloatTest>>#testHugeIntegerCloseTo FloatTest>>#testInfinityCloseTo WeakRegistryTest>>#testFinalization PCCByLiteralsTest>>#testSwitchPrimCallOffOn AllocationTest>>#testOneGigAllocation FloatTest>>#testNaNCompare FileStreamTest>>#testPositionPastEndIsAtEnd NumberTest>>#testRaisedToIntegerWithFloats Errors: MessageTallyTest>>#testSampling1 WeakSetInspectorTest>>#testSymbolTableM6812 I think that most of these problems were fixed in latest official SqueakVM. I guess they were integrated in VMMaker in versions later than the one you used for Cog. Maybe you can integrate them and create a new version? I am not a VM expert so please if you can help us with this tests it would be cool. Thanks Mariano

1 0

[Pharo-project] Enable/Disable NewInspector
by Mariano Martinez Peck Sept. 16, 2010

Sept. 16, 2010

Hi, is there a way to enable and disable NewInspector in a PharoDev image? I don't want to remove neither not load. I want that having both in the system, if there is a way right now to decide which one to use. thanks mariano

3 3

[Pharo-project] Best Smalltalk Book of the previous 6 years
by Noury Bouraqadi Sept. 16, 2010

Sept. 16, 2010

Yesterday evening we also announced the result of the survey. And the winner is... Dynamic Web Development with Seaside By StÃ©phane Ducasse, Lukas Renggli, David C. Shaffer, Rick Zaccone, Michael Davies Noury @ ESUG 2010 - Barcelona :-) --- 18th International Smalltalk Joint Conference, September 13 -17 2010 Barcelona, Spain. http://www.esug.org/Conferences/2010

1 0

[Pharo-project] two dots in latest 1.2 prebuilt image file name
by Pavel Krivanek Sept. 16, 2010

Sept. 16, 2010

Hi, prebuilt PharoCore-1.2-12137 image contanins two dots in the image and changes file name: PharoCore-1.2-12137..image PharoCore-1.2-12137..changes Cheers, -- Pavel

1 0

[Pharo-project] Another silent failure?
by Schwab,Wilhelm K Sept. 16, 2010

Sept. 16, 2010

I am playing with a new library and for kicks thought I would call its get-version function: | buffer | buffer := String new:80. PLplotLibrary default cPlgver:buffer. buffer. The above appears to do nothing; the buffer remains blank, and there is no error raised from it. I tried something more complicated involving external address and #alloc: and got the version number. That is encouraging from a perspective of talking to the library, but then I had to square the above failure with my use of memcpy() not long ago (different topic). In that case, I had real need to allocate a buffer in a fixed heap, but was told that I could ultimately copy from said buffer (which lives across multiple gcs and would move) into a ByteArray of the needed size, which would not move during the memcpy() call. That worked. So I tried | buffer | buffer := ByteArray new:80. PLplotLibrary default cPlgver:buffer. buffer asString. and get the version number. What's up? Why is it ok to pass a byte array but not a string? If there really is a difference, there should be an exception hinting that something is wrong and what it might be - right? Bill

4 8