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

Re: [Pharo-project] Fwd: [squeak-dev] Re: Debug-it and external calls

by StÃ©phane Ducasse

enough half omniscient are enough :) On Jul 20, 2010, at 3:49 AM, Henrik Johansen wrote: > > > Den 19. juli 2010 kl. 23:04 skrev StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> should this be integrated into pharo? >> ifTrue: open a ticket please. >> >> Sorry but I'm not omniscient yet even if I work hard on it >> >> Stef > > That's ok, I am! ;) > The change to use large frames for methods doing performs was integrated in Pharo shortly after Igor initially raised the issue. > I can't remember off-hand if they are part of 1.1 though. > Darn, guess I'm not omnipotent after all. > > Cheers, > Henry > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010

Re: [Pharo-project] help to update actions done in Pharo 1.1

by StÃ©phane Ducasse

ok We will see if this happens before october else we will check that with the guy we will hire. >>> Basically in Squeak, but I'm sure most of them are in the Pharo bugtracker. >> Thanks but >> well... >> tell me that this is too boring to report it which I can understand but not that >> kind of answer because this is certainly not the case since I'm nearly the only one >> to look at squeak fixes. > > The code of HashedCollection and subclasses in Pharo and Squeak are too different now, there are no patches/changesets that can convert one to the other. So a brave soul has to do it by hand. > > > Levente > >> >> Stef >> >>> >>> >>> Levente >>> >>>> >>>> Stef >>>> >>>> On Jul 19, 2010, at 6:18 PM, Levente Uzonyi wrote: >>>> >>>>> On Mon, 19 Jul 2010, Henrik Johansen wrote: >>>>> >>>>> ... >>>>> The wkd in Pharo 1.1 didn't really result in a speedup :) >>>>> Better Identity hashing, encoding conversions, the other collection changes which made it in, plus rendering speedups f.ex through inlining alot of common morph extensions, and using Strike fonts by default, were though! >>>>> >>>>> >>>>> That's a nice euphemism. I didn't check the code thoroughly, but rehashing seems to be O(n^2) in WeakKeyDictionary. This affects it's subclasses and WeakRegistry which affects the whole finalization process. >>>>> >>>>> (Recently I did a benchmark of Seaside 3.0, where Squeak handled 1.28x more requests/second than Pharo under "heavy load" (50 concurrent users flooding the server) with the Kom adaptor.) >>>>> >>>>> >>>>> Levente >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> _______________________________________________ >>> 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

July 20, 2010

Re: [Pharo-project] help to update actions done in Pharo 1.1

by StÃ©phane Ducasse

>>> The code of HashedCollection and subclasses in Pharo and Squeak are too different now, there are no patches/changesets that can convert one to the other. So a brave soul has to do it by hand. >> >> Levente >> > I've been meaning to for the longest time, but work/other bugs/holiday keeps getting in my way :( > > If my friends start leaving me alone, I might finally get some time at the end of this last holiday week though ;) >>> > > > Cheers, > Henry friends are important :) Stef

July 20, 2010

Re: [Pharo-project] Update of Seaside One-Click Experience 3.0RC (development) image fails when using the Software update menu

by Franz Josef Konrad

Thanks for the detailed answer and your suggestions to handle the issue. It would be great if such useful information would be visible in a readme workspace. I guess all newcomers can benefit from it. Regards, Franz Josef Am 19.07.2010 15:09, schrieb Mariano Martinez Peck: > > > On Mon, Jul 19, 2010 at 12:57 PM, Franz Josef Konrad <franzl(a)fjkonrad.de > <mailto:franzl@fjkonrad.de>> wrote: > > I've downloaded the newest development image from > <http://www.seaside.st/download/pharo> (the link of the image is > <http://www.seaside.st/distributions/Seaside-3.0rc.app.zip>). > > If you enable "Show update option in World menu" in the settings > browser and try to bring the image up2date using this menu it fails. > > It seems to me that this image has a wrong version string > 'Pharo-1.1-11406-rc3' instead of 'Pharo1.1rc3'. > > When you evaluate > SystemVersion current version: 'Pharo1.1rc3' > the update of the image works fine via the menu System>Software update. > > > Hi Franz Josef. The system update is disabled in purpose. The Pharo > image cannot be updated anymore. Only PharoCore images can be updated. > So..you have two posibilities: > > - You just update seaside in the same Pharo image > - You just take any new released Pharo image and load Seaside there. > > If you are curious why updates were disable, read: > http://forum.world.st/update-1-1-11371-tp2229126p2231195.html > > Thanks > > Mariano > > Regards, > Franz Josef > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > <mailto:Pharo-project@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 20, 2010

Re: [Pharo-project] about hex

by StÃ©phane Ducasse

thanks! Stef On Jul 20, 2010, at 2:46 AM, Henrik Johansen wrote: > Iirc, it was reintroduced in Pharo in relation to SqueakDBX, might want to check with Mariano that changes will be compatible/SqueakDBX is updated. > > Cheers, > Henry > > Den 19. juli 2010 kl. 23:05 skrev StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> **Tx** >> http://code.google.com/p/pharo/issues/detail?id=2699 >> >> Stef >> >> >> On Jul 19, 2010, at 10:07 PM, Levente Uzonyi wrote: >> >>> On Mon, 19 Jul 2010, StÃ©phane Ducasse wrote: >>> >>>> Levente >>>> Now what hex should returns? >>> >>> If you mean Integer >> #hex then see here: >>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-July/151957.html >>> >>> >>> Levente >>> >>>> >>>> On Jul 19, 2010, at 9:33 PM, stephane ducasse wrote: >>>> >>>>> If I recall hex was removed because it was used for html related thing. >>>>> >>>>> Stef >>>>> >>>>> >>>>> >>>>> Looks like the hex method will be changed in Squeak and >>>>> we should keep track using this issue to see if Pharo has >>>>> to follow to keep compatible (also for Cog). >>>>> >>>>> See >>>>> >>>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-July/151949.html >>>>> >>>>> _______________________________________________ >>>>> 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 >> >> >> _______________________________________________ >> 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 20, 2010

[Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.1r1

by Torsten Bergmann

Hi Mariano, why dont you add: (Scanner class includesSelector: #allowUnderscoreAsAssignment:) ifTrue: [Scanner allowUnderscoreAsAssignment: true] to the #preLoadForPharo ? Bye T. -- 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

July 20, 2010

Re: [Pharo-project] Markup Builder in Smalltalk (XMLWriter)

by HernÃ¡n Morales Durand

http://www.squeaksource.com/XMLPullParser.html If I would going to write a XML parser, I'd go for a VTD parser instead. Cheers, HernÃ¡n 2010/7/19 Norbert Hartl <norbert(a)hartl.name>: > > On 06.07.2010, at 23:04, jaayer wrote: > >> >> >> ---- On Tue, 06 Jul 2010 03:19:48 -0700 Torsten Bergmann Â wrote ---- >> >>> Just check "XMLWriter-tbn.5" which can be found in "http://squeaksource.com/PharoGoodies/" >>> >>> ------------------------------------------------------ >>> |writer| >>> writer := XMLTagWriter xml. >>> writer comment: 'A new xml file'. >>> writer tag: 'package' with: [ >>> Â Â writer cData: 'name' with: 'XMLWriter'. >>> ]. >>> writer contents >>> >>> returns >>> >>> >>> >>> >>> >>> >>> ------------------------------------------------------ >>> >>> You can also access the stream (writer stream). >>> Indenting is not yet working fully but at least >>> it should give you idea. Check out the test cases for >>> more. >>> >>> I once saw such an XMLWriter written by Ernest Micklei >>> in VAST (credits for the idea) and rebuilt it in Pharo. >>> >>> Bye >>> T. >>> -- >>> 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 >>> >> >> The next version of XMLSupport will feature an XMLWriter with an API similar to XMLTagWriter. I had decided a few weeks that any API using explicit start/end methods was unsmalltalk-like and should be replaced with one based on execute-around methods, though I was unaware of XMLTagWriter and instead modeled the API loosely on Seaside's HTML generation. You now send XMLWriter messages that create markup-writing objects for the parts of a document. These objects can then be configured using messages like #attributeAt:put: and written to the document explicitly with a serialization message (which typically accepts content) or implicitly by creating another markup writer after it. The new API looks like this: >> >> Â Â Â | writer | >> Â Â Â ((writer := XMLWriter new) >> Â Â Â Â Â Â Â enablePrettyPrinting; >> Â Â Â Â Â Â Â xmlDeclaration; >> Â Â Â Â Â Â Â tag: 'foo') >> Â Â Â Â Â Â Â Â Â Â Â xmlnsAt: 'foo' put: 'http://foo'; >> Â Â Â Â Â Â Â Â Â Â Â attributeAt: 'a' put: 'one'; >> Â Â Â Â Â Â Â Â Â Â Â attributeAt: 'b' put: 'two'; >> Â Â Â Â Â Â Â Â Â Â Â content: [ >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â writer tag: 'bar' content: [ >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â (writer >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â string: 'test'; >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â tag: 'baz'; >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â tag: 'foobar') >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â content: 'test']] >> which produces: >> <?xml version="1.0" encoding="UTF-8"?> >> <foo xmlns:foo="http://foo" a="one" b="two"> >> Â Â <bar>test<baz /> >> Â Â Â Â <foobar>test</foobar> >> Â Â </bar> >> </foo> >> > Could you elaborate on the usage of xmlns? The one you defined does nothing. The foo in the xml is just the element name. I would like to know > > - how to define a namespace prefix for an element > - how to define a default namespace for an element > > I think I need another look in the xml parser since last time :) Thanks for putting effort into xml parser. Is there a pull parser available or planned? > > thanks, > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.1r1

by Miguel Enrique CobÃ¡ MartÃnez

El sÃ¡b, 10-07-2010 a las 12:14 -0300, GermÃ¡n Arduino escribiÃ³: > I saw that exist a preference, but seems not work. > > Also a closed issue talking about this topic (1544) but really don't > understand how to use this in Pharo 1.0. > > Any clarification will be appreciated. Hola GermÃ¡n, just have the time to check this issue. I found the problem. This configuration was made and tested for PharoCore 1.0 (and maybe Pharo 1.0 but I always test on Pharo Core images). The version I published with support for 1.1r1 was ConfigurationOfMagma-MiguelCoba.31.mcz from 3 June 2010, 7:40:32 pm. Thas was tested, as I said, in PharoCore 1.0. In pharo core 1.0 the underscores are allowed. Also, in PharoCore 1.0 the setting is changed in a preference Preferences class>>allowUnderScoreAssingment. Remember that currently only PharoCore 1.0 is released and stable. 1.1 is frozen and 1.2 is unstable. Now, the configuration was modified in order to work for 1.1 and 1.2. So the method: ConfigurationOfMagma>>preLoadForPharo "Magma extends EventSensor that was replaced by InputEventSensor in Pharo and Magma still has underscore code" Smalltalk at: #EventSensor put: InputEventSensor. got this line added: Scanner allowUnderscoreAsAssignment: true. But this is correct only for Pharo 1.1 and 1.2. In those versions of pharo, is the Scanner class the responsible of allowing or not the underscore in the code. In Pharo 1.0 that method doesn't exist in Scanner class. So the error you saw. So the configuration of magma now loads in 1.1 and 1.2 but is broken on the stable release. fortunately this can be reverted and everything will be ok. But... two things: - If we modify a stable configuration in order to make it work in a RC or unstable version of pharo things will probably broke, because of the many changes of the new version of pharo respect to the old one. - We must decide about the aproach for handle this. One proposal suggested to copy all the configurations tested in a given pharo version to a new repository for the next release. I proposed to use tags in the version methods that specify what versions of pharo they apply to (but didn't provide any code for this so the copy of configuration has more viability :) No matter what option is elected as long as is elected soon. Why, because people understandably want software to run in the newest version of pharo, but if there isn't a specific configuration for the new version, they will modify and possibly broke the stable one. So people, what should we do? Dale, can you please give your opinion. We need to decide now. P.S. I will revert for now the change in ConfigurationOfMagma so it works for 1.0 and will be broken for 1.1 and 1.2. Thanks > > Cheers. > > > El 9 de julio de 2010 20:12, GermÃ¡n Arduino <garduino(a)gmail.com> > escribiÃ³: > I checked a bit and saw that such method is on Scanner class > on PharoCore 1.2, but not on Pharo 1.0. > > What I missed? > > > El 9 de julio de 2010 19:46, GermÃ¡n Arduino > <garduino(a)gmail.com> escribiÃ³: > > > Hi; > > Thanks by the useful configuration. > > I tried today by first time on a Pharo 1.0 image and > get a DNU > > Scanner class(Object)>> > doesNotUnderstand: #allowUnderscoreAsAssignment: > > I need to install some patch before run the > installation? > > Cheers. > GermÃ¡n. > > > > > El 3 de junio de 2010 21:46, Miguel Enrique CobÃ¡ > MartÃnez <miguel.coba(a)gmail.com> escribiÃ³: > > I'm pleased to announce that the > ConfigurationOfMagma now includes > > > support for loading version 1.1r1 of Magma. > > In a Pharo or PharoCore 1.0 image evaluate: > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfMagma'; > load. > > To install the Magma Client evaluate: > > ConfigurationOfMagma project latestVersion > load: 'Client' > > To install the Magma Server evaluate: > > ConfigurationOfMagma project latestVersion > load: 'Server' > > To install the Magma Tester evaluate: > > ConfigurationOfMagma project latestVersion > load: 'Tester' > > Then if you want, run the test suite. Evaluate > in a workspace: > > MagmaTestCase allowWriteBarrier: false. > MagmaTestCase fullSuite maDebug. > > > Enjoy > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Magma mailing list > Magma(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/magma > > > > > -- > ================================================= > GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: > garduino > Arduino Software & Web Hosting > http://www.arduinosoftware.com > PasswordsPro http://www.passwordspro.com > ================================================= > > > > > > -- Miguel CobÃ¡ http://miguel.leugim.com.mx

July 20, 2010

Re: [Pharo-project] Fwd: [squeak-dev] Re: Debug-it and external calls

by Henrik Johansen

Den 19. juli 2010 kl. 23:04 skrev StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > should this be integrated into pharo? > ifTrue: open a ticket please. > > Sorry but I'm not omniscient yet even if I work hard on it > > Stef That's ok, I am! ;) The change to use large frames for methods doing performs was integrated in Pharo shortly after Igor initially raised the issue. I can't remember off-hand if they are part of 1.1 though. Darn, guess I'm not omnipotent after all. Cheers, Henry

July 20, 2010

Re: [Pharo-project] help to update actions done in Pharo 1.1

by Henrik Johansen

Den 20. juli 2010 kl. 02:04 skrev Levente Uzonyi <leves(a)elte.hu>: > On Mon, 19 Jul 2010, StÃ©phane Ducasse wrote: > >> >> On Jul 19, 2010, at 10:08 PM, Levente Uzonyi wrote: >> >>> On Mon, 19 Jul 2010, StÃ©phane Ducasse wrote: >>> >>>> Where is the code that we should check to be included in 1.2? >>> >>> Basically in Squeak, but I'm sure most of them are in the Pharo bugtracker. >> Thanks but >> well... >> tell me that this is too boring to report it which I can understand but not that >> kind of answer because this is certainly not the case since I'm nearly the only one >> to look at squeak fixes. > > The code of HashedCollection and subclasses in Pharo and Squeak are too different now, there are no patches/changesets that can convert one to the other. So a brave soul has to do it by hand. > > > Levente > I've been meaning to for the longest time, but work/other bugs/holiday keeps getting in my way :( If my friends start leaving me alone, I might finally get some time at the end of this last holiday week though ;) >> Cheers, Henry

July 20, 2010