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

Re: [Pharo-project] Cleaning WriteBarrier (as used in Magma)

by StÃ©phane Ducasse

What is missing to make it work in Pharo? Stef On Jul 6, 2010, at 8:16 PM, Chris Muller wrote: > Thanks, I will look for your updated WriteBarrier package to include > with the next Magma. I have just copied my own latest WriteBarrier to > the MagmaTester project of squeaksource. > > ------- > Name: WriteBarrier-cmm.27 > Author: cmm > Time: 19 June 2010, 4:41:13.886 pm > UUID: 84945d10-b0eb-419b-a6bc-2de227aac87a > Ancestors: WriteBarrier-pmm.26 > > Removed PseudoContext extension for compatibility with Squeak 4.2+. > ---------- > > WriteBarrier unfortunately doesn't work in either of Pharo or Squeak > 4.1+. I am tempted to remove it from the suite altogether, but to do > so would break backward compatibility with 3.9 who may be using > WriteBarrier, because the implementation requires the handler > (MaTransaction) to inherit from the WriteBarrier class itself.. :-( > > Thanks, > Chris > > > On Tue, Jul 6, 2010 at 4:44 AM, Torsten Bergmann <astares(a)gmx.de> wrote: >> Hi Avi, >> >> how is life at Twitter ;) >> >> Would it be possible that you add me as a developer on >> >> http://www.squeaksource.com/WriteBarrier >> >> so I can clean up underscore assignment in the package. >> >> WriteBarrier is used in Magma (see ConfigurationOfMagma) >> which is installable right from a workspace in the >> upcoming Pharo 1.1 release. Currently this fails since >> by default underscore assignment is not allowed in Pharo. >> >> Thanks >> Torsten >> -- >> GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. >> Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl >> >> _______________________________________________ >> 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

July 6, 2010

Re: [Pharo-project] [SPAM] should we move pharo to use webclient?

by StÃ©phane Ducasse

I agree and this is why I asked. I'm not good in network but the code of network always made me nearly faint because it was clearly not designed. Now why interested people would not do a little task forces to bullet proof the integration and we prepare together its integration... remember pharo is also your smalltalk :) On Jul 6, 2010, at 3:04 PM, Sven Van Caekenberghe wrote: > Yes!! > > It now loads without patches into Pharo 1.1 rc2 > I used its client and server part, seaside adaptor, it all works. > > The code is quite readable/understandable/malleable. > > I did not yet test the WebClient-HTTP package which patches HTTPSocket to replace the old code, > which is obviously important (it then gets used by MC and the rest of Smalltalk). > > The unit tests also have to be double checked. > > What do others, like Lukas and other Seaside people think of it ? > > The basic point it: it can only be better than the older code. > But on the other hand, maybe the leap could be even bigger still ? > Having a facade for a pluggable http client is one step. > > Having a good basic HTTP client and server is very important. > > Sven > > On 06 Jul 2010, at 09:30, StÃ©phane Ducasse wrote: > >> to replace the old code? >> >> Stef >> >> _______________________________________________ >> 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

July 6, 2010

Re: [Pharo-project] Pharo on OLPC XO kid notebook

by StÃ©phane Ducasse

On Jul 6, 2010, at 6:24 PM, Hilaire Fernandes wrote: > OLPC moto is based from day one on the use of dynamic language to design the content coming with their notebook. > > It is to write content but also to allow kids to examine source code, edit it and test it ; as we are doing continuously in Smalltalk. > They even think about a source-code key in the keyboard to instantaneously open a source code browser exposing the code of a running application. > > Now that Pharo 1.1 is in good sigh and as we are not ashame any more to show how Smalltalk looks like we could also produce a release of Pharo for OLPC XO Sugar environment. It is definitely a good opportunity to bring an interesting tool to neutral mind (kids). In the other hand, it will definitely help to bring awareness about Pharo. For example, without any action of my part, DrGeoII was downloaded about 180'000 times in one year for XO. > > Any takers? any idea of the task? what does it implies? > Hilaire > > PS: I have a couple of XO machines for testing purpose. I gave mine to richie for SqueakNOS :) > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 6, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11406-rc3dev10.07.1

by StÃ©phane Ducasse

thanks david It would be great to start removing what does not work or rethink then like the smart groups. I love smart groups but you were diving in your PhD and they need a bit love and care. Stef On Jul 6, 2010, at 3:00 PM, David RÃ¶thlisberger wrote: > I fixed O2 to make it work in latest Pharo. > Please test. > > Cheers, > David > > > I vote for fixing O2! > > On 05 Jul 2010, at 11:16, Alexandre Bergel wrote: > > > >> It is not clear what we (or at least I) should do. > >> Maintaining two browsers is clearly not an option. > >> Cheers, > >> Alexandre > >> > >> > >> On 5 Jul 2010, at 16:53, Johan Fabry wrote: > >> > >>> BTW it's even worse than initially thought: no classes are shown when I click on a category, and doing a find class yields a DNU. So the browser is basically broken. > >>> > >>> On 05 Jul 2010, at 10:39, Alexandre Bergel wrote: > >>> > >>>> I can have a look at it within the next few days (I am currently in half-holidays). > >>>> > >>>> Cheers, > >>>> Alexandre > >>>> > >>>> > >>>> On 2 Jul 2010, at 22:27, Mariano Martinez Peck wrote: > >>>> > >>>>> > >>>>> 2010/7/2 Johan Fabry <jfabry(a)dcc.uchile.cl> > >>>>> > >>>>> This RC has problems with 02, I get the below 3 deprecated warnings when opening a new browser. Who do I notify? > >>>>> > >>>>> > >>>>> To the O2 "mainteiners". Alexandre Bergel and David RÃ¶thlisberger as I am aware. I cc'ed them. > >>>>> > >>>>> Cheers > >>>>> > >>>>> Mariano > >>>>> > >>>>> The method Collection asSortedArray has been deprecated. > >>>>> Use asArray sort > >>>>> The method Collection asSortedArray has been deprecated. > >>>>> Use asArray sort > >>>>> The method Boolean and:and:and:and: has been deprecated. > >>>>> Use and: instead > >>>>> > >>>>> On 01 Jul 2010, at 18:29, Mariano Martinez Peck wrote: > >>>>> > >>>>>> Hi folks. I am glad to announce the Pharo 1.1 RC3. It has not too much changes in compare to RC2. The main change is the menu structure. I also updated to newest version of external packages. > >>>>>> Here is the image: > >>>>>> > >>>>>> https://gforge.inria.fr/frs/download.php/27241/Pharo-1.1-11406-rc3dev10.07.… > >>>>>> > >>>>>> We would really appreaciate feedback and help to fix the failing tests. > >>>>>> Cheers > >>>>>> > >>>>>> Mariano > >>>>>> _______________________________________________ > >>>>>> Pharo-project mailing list > >>>>>> Pharo-project(a)lists.gforge.inria.fr > >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>>> -- > >>>>> Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry > >>>>> PLEIAD Lab - Computer Science Department (DCC) - University of Chile > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Pharo-project mailing list > >>>>> Pharo-project(a)lists.gforge.inria.fr > >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>>> > >>>> -- > >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >>>> Alexandre Bergel http://www.bergel.eu > >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >>>> > >>>> > >>>> > >>>> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 6, 2010

Re: [Pharo-project] Issue 2635 - methods recategorization

by StÃ©phane Ducasse

pavel could you chop it and send it piece by piece to the list so that everybody can get a feel about it and discuss if necessary? I'm sorry but I like that we act a group and not a bunch of cool individual and building a mind-share is important for me. Stef On Jul 6, 2010, at 4:43 PM, Pavel Krivanek wrote: > Hi, > > I finished the list of changes for the issue > http://code.google.com/p/pharo/issues/detail?id=2635. > > This issue is the next step after already integrated packages > reorganization and the goal is to have compact package base a the > small headless PharoKernel image. > > Most changes are simple naming unification and some classes I skipped > because they need deeper refactorings. > > I will now check the list once more. > > -- Pavel > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 6, 2010

Re: [Pharo-project] Alien on Pharo 1.2 on Mac

by StÃ©phane Ducasse

you do not have access to the alien repository? can you ask john to gve you access to it? On Jul 6, 2010, at 3:41 PM, Luc Fabresse wrote: > Hi all, > > We provide a usable version of Alien to Pharo 1.2 (all tests green on OSX). > We committed the corrected package on the Ocean squeaksource repository : http://squeaksource.com/Ocean > (Alien-Core-LucFabresse.64.mcz) > > We didn't look in details to the method SystemDictionary>>recreateSpecialObjectsArray introduced by Alien-Core-63. > It is now unsed because Smalltalk points to a SmalltalkImage. > This need to be checked before possibly removal. > > Another point would be to update the metacello configuration ConfigurationOfAlien. > > Luc and Noury > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 6, 2010

Re: [Pharo-project] Markup Builder in Smalltalk

by StÃ©phane Ducasse

There is an interest! Please submit/publish it... Now What is the exact API I found cNode: a bit a bad name. What does it mesn childrenNode: newBldr := XMLBuilder new xmlPreprocessor. newBldr mbAttr: #(âa=â6â³â âb=â7â³â); test: âwelcome to buildersâ why new and xmlPreprocessor mbAttr: sucks also! Could you shine a bit the API to be reader friendly? Stef On Jul 6, 2010, at 12:32 PM, Sudhakar Krishnamachari wrote: > More or less exactly the same..except the syntax.. but includes the CDATA, Comments, plainText, preproc etc.. > > instead of tag: with: .. I went off to.. > > {theTag}: theText cNode: [] > > mbAttr: taking a collection of assocs or strings.. for the attrib. > > > tabs are integrated with valueStringTrimmed dummping it without tabs/crlf.. > > will see if I can check in this too as an alternative to see means of merging the frameworks for best use.. > ***** > > Just check "XMLWriter-tbn.5" which can be found in "http://squeaksource.com/PharoGoodies/" > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 6, 2010

Re: [Pharo-project] Markup Builder in Smalltalk

by StÃ©phane Ducasse

what I often wanted is to be able to generate valid xml without having to load seaside. Just getting the canvas. So may be lighter solution is interesting. On Jul 6, 2010, at 11:20 AM, Lukas Renggli wrote: > Seaside provides that kind of functionality. > > Lukas > > 2010/7/6 Sudhakar Krishnamachari <skrishnamachari(a)gmail.com>: >> Is there any general interest in Markup Builder...a la Groovy..? >> >> http://skrishnamachari.wordpress.com/2010/07/06/markupbuilder-in-smalltalk/ >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 6, 2010

Re: [Pharo-project] Release Core?

by StÃ©phane Ducasse

On Jul 6, 2010, at 9:48 AM, Mariano Martinez Peck wrote: > > > 2010/7/6 Adrian Lienhard <adi(a)netstyle.ch> > (moving this thread to pharo-dev) > > Context: green tests for Pharo 1.1 (currently at RC4). > > Thanks Mariano, I went through your list of tests. > > In summary, what needs to be done: > - Fixes for Nile > - Fix one failing Shout test > - Adaptation/fixes of external packages: method wrappers, sound, morphic examples > > In detail: > > Needs fixing > ----------- > SHParserST80Test>>#testNumbers > > See http://forum.world.st/Problem-with-number-parsing-in-Shout-help-needed-td22… > > Nicolas Cieller explains there the reason. I hadn't time to analize it, thus (and I am completly newbie with that). > If someone can directly commit to Shout I would appreaciate it. > > > NSMultiByteBinaryOrTextStreamTest>>#testFileOut > NSSmartRefStreamTest>>#testGlobal > NSMCPseudoFileStreamTest>>#testFileOut > NSMCPseudoFileStreamTest>>#testFileOutFileIn > NSRWBinaryOrTextStreamTest>>#testFileOut > NSRWBinaryOrTextStreamTest>>#testFileOutFileIn > ReleaseTest>>#testUndeclared > > Undeclared classes and variables (these external packages need to be adapted or should not be loaded) > --------- > WatchMorph references ColorPickerMorph > AbstractSound references FillInTheBlank > EnvelopeEditorMorph, MidiInputMorph, and ScorePlayerMorph reference PopUpChoiceMorph > KeyboardMorphForInput, MidiInputMorph, and ScorePlayerMorph reference SimpleSwitchMorph > ArchiveViewer references StandardFileMenu > ObjectAsMethodWrapper has undeclared variable named selector and wrappedClass > > > ufffff what do we do with this stuff? I can have a look. This is why we must change the way we deal with externally managed by maintained packages. We should try to get a special metacello configuration for pharo (pharo-core + packages) and that we work with pahro and not core when we fixe stuff.. Stef > > > Fixed, see attached cs (we had that already in 1.0 but apparently it was lost for 1.1) > ----------- > WeakSetInspectorTest>>#testSymbolTableM6812 > > > > Great. Maybe we can integrate it in 1.0 together with 2547 (explained later) > > > > Workes for me (when running each test alone)(?) > > Most of them. > testOneGigAllocation and > testPositionPastEndIsAtEnd > > fail always for me. > > > ----------- > ObjectAsOneTimeMethodWrapperTest>>#testInstallOnClassCategory > MCInitializationTest>>#testWorkingCopy > WeakRegistryTest>>#testFinalization > FileStreamTest>>#testPositionPastEndIsAtEnd > > This was fixes in 1.2 by the ticket 2547. Maybe we can integrate it in 1.1 also? > > > AllocationTest>>#testOneGigAllocation > > Cheers, > Adrian > > > On Jul 5, 2010, at 22:06 , Mariano Martinez Peck wrote: > > > On Mon, Jul 5, 2010 at 8:00 PM, Adrian Lienhard <alienhard(a)netstyle.ch>wrote: > > > >> I updated the download page. > >> > >> > > thanks > > > > > >> Cheers, > >> Adrian > >> > >> BTW, what is the state of the tests? Last time I run them, there were a lot > >> of failures... > >> > >> > > much better. I fixed a lot of Nile with your suggestion and further > > problems/fixes. > > > > My results so far are these: > > > > 9764 run, 9697 passes, 53 expected failures, 8 failures, 6 errors, 0 > > unexpected passes > > Failures: > > AllocationTest>>#testOneGigAllocation > > NSMultiByteBinaryOrTextStreamTest>>#testFileOut > > SHParserST80Test>>#testNumbers > > ReleaseTest>>#testUndeclared > > FileStreamTest>>#testPositionPastEndIsAtEnd > > WeakRegistryTest>>#testFinalization > > MCInitializationTest>>#testWorkingCopy > > ObjectAsOneTimeMethodWrapperTest>>#testInstallOnClassCategory > > > > Errors: > > WeakSetInspectorTest>>#testSymbolTableM6812 > > NSSmartRefStreamTest>>#testGlobal > > NSMCPseudoFileStreamTest>>#testFileOut > > NSMCPseudoFileStreamTest>>#testFileOutFileIn > > NSRWBinaryOrTextStreamTest>>#testFileOut > > NSRWBinaryOrTextStreamTest>>#testFileOutFileIn > > > > > > > > > > > >> ___________________ > >> http://www.adrian-lienhard.ch/ > >> > >> On Jul 5, 2010, at 18:26 , StÃ©phane Ducasse wrote: > >> > >>> Yes > >>> > >>>> I have just created the image RC4. It is in > >> https://gforge.inria.fr/frs/download.php/27254/Pharo-1.1-11409-rc4dev10.07.… > >>>> > >>>> Adrian, do you think we should update the link of 1.1 from the website > >> to this one? > >>>> > >>>> Cheers > >>>> > >>>> Mariano > >>> > >> > >> > > > _______________________________________________ > 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

July 6, 2010

Re: [Pharo-project] python documentation rocks

by StÃ©phane Ducasse

Hi, > > Python 2.7 has just been released, documentation is up to date. http://docs.python.org/ > > That's so great. I hope we will have a process for Pharo's documentation. Is it possible to automatically generate a changelog for Pharo 1.1 ? Yes. Scriptloader logStream (may be this is broken) Now we can also as lukas mentioned use the code web site y entering date we can generate a list of fixed items. The problems is that we are not enough, even if this is getting better. And we should have started 5 years ago. Stef > Cheers > > Laurent > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 6, 2010