- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Metacello Help book in Pharo-Dev

by StÃ©phane Ducasse

The problem is that we have 25 pages of metacello explanation before that blog (which will be added to the book chapter). So the help should be small but not too much and not that long. This is all the question of how to manage it (especially with duplication). I suggest to have a synthetic help description of a couple of pages and pointers to the chapter. Stef On Jan 18, 2011, at 9:48 AM, Torsten Bergmann wrote: > Should we add the Metacello Help book to Pharo-dev? > See > > http://gemstonesoup.wordpress.com/2011/01/17/metacello-1-0-beta-28-unearthe… > -- > Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! > Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail >

Jan. 18, 2011

[Pharo-project] Metacello Help book in Pharo-Dev

by Torsten Bergmann

Should we add the Metacello Help book to Pharo-dev? See http://gemstonesoup.wordpress.com/2011/01/17/metacello-1-0-beta-28-unearthe… -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

Jan. 18, 2011

[Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3545 by sean.p.d...(a)gmail.com: FEATURE: Multiple Worlds http://code.google.com/p/pharo/issues/detail?id=3545 Pharo image: 1.2 Allow users to have multiple worlds

Jan. 18, 2011

Re: [Pharo-project] Issue 3179 in pharo: Failing Tests for Monticello

by pharo＠googlecode.com

Comment #2 on issue 3179 by marcus.d...(a)gmail.com: Failing Tests for Monticello http://code.google.com/p/pharo/issues/detail?id=3179 see Issue 2294

Jan. 18, 2011

Re: [Pharo-project] Is there a http server that understands PUT?

by Philippe Marschall

On 01/17/2011 09:22 PM, Norbert Hartl wrote: > While trying to consume some PUT urls with Seaside-REST I noticed that the transmitted content is missing. I tried Comanche as well as swazoo. At this moment I'm not sure if I did something wrong but I seems that only GET and POST are treated. > > Does anyone has some experience on this? Comanche should work because uploading a Monticello version to SqueakSource is a PUT. Note that Seaside applications (WAApplication) only support GET and POST but request handlers support everything. That's in Seaside 3.0 at least. Cheers Philippe

Jan. 18, 2011

Re: [Pharo-project] Was not able to update with #12304

by Igor Stasenko

On 18 January 2011 07:51, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > On Mon, Jan 17, 2011 at 4:21 AM, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> Looks like a Cog issue, I was able to reproduce it: >> >> When I download "PharoCore-1.2.zip" from >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/126/ >> >> (which is a Pharo 1.2 Core #12303 image) and I directly start the image >> Â with the latest Win32 Cog VM from Eliot then I'm not able >> Â to go through update #12304 via the update mechanism >> Â as I already wrote in [1]. I get this error: >> >> Â => ClassBuilder(Object)>>doesNotUnderstand: #reshapeClass:toSuper: > > Thanks,Â Torsten! > Yes, the StackToRegisterMappingCogit gets confused by the initial assignment > of nil in > oldClass subclasses do: [:oldSubclass | | newSubclass | > copyOfOldTraitComposition := copyOfOldClassTraitComposition := nil. > assuming the nil is a temp initialization rather than merely an operand, and > hence gets confused about the stack layout (is off by one) and ends up > sendingÂ reshapeClass:toSuper: to the first temp (which is nil) instead of > the receiver. Â The fix is probably to duplicate the implementation > ofÂ BlockLocalTempCounter in the block scanning part of the code generator > and hence to accurately count the number of temps in a block. Â This will > have to wait for the weekend :/ -1 bug. which is good :) > By the way it looks to me that makingÂ copyOfOldTraitComposition & > copyOfOldClassTraitComposition local temps in each of the do: blocks won't > change the semantics and will remove the need to initialize them explicitly. > >> >> When I use the standard VM I'm able to update correctly >> to the latest version pharo core 1.2 #12307 >> >> Maybe Eliot is able to reproduce and fix it. Until then I switch >> to standard VM. >> >> Thx >> Torsten >> >> >> [1] >> http://lists.gforge.inria.fr/pipermail/pharo-project/2011-January/039747.ht… >> -- >> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir >> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > -- Best regards, Igor Stasenko AKA sig.

Jan. 18, 2011

Re: [Pharo-project] Was not able to update with #12304

by Eliot Miranda

On Mon, Jan 17, 2011 at 4:21 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Looks like a Cog issue, I was able to reproduce it: > > When I download "PharoCore-1.2.zip" from > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/126/ > > (which is a Pharo 1.2 Core #12303 image) and I directly start the image > with the latest Win32 Cog VM from Eliot then I'm not able > to go through update #12304 via the update mechanism > as I already wrote in [1]. I get this error: > > => ClassBuilder(Object)>>doesNotUnderstand: #reshapeClass:toSuper: > Thanks, Torsten! Yes, the StackToRegisterMappingCogit gets confused by the initial assignment of nil in oldClass subclasses do: [:oldSubclass | | newSubclass | copyOfOldTraitComposition := copyOfOldClassTraitComposition := nil. assuming the nil is a temp initialization rather than merely an operand, and hence gets confused about the stack layout (is off by one) and ends up sending reshapeClass:toSuper: to the first temp (which is nil) instead of the receiver. The fix is probably to duplicate the implementation of BlockLocalTempCounter in the block scanning part of the code generator and hence to accurately count the number of temps in a block. This will have to wait for the weekend :/ By the way it looks to me that making copyOfOldTraitComposition & copyOfOldClassTraitComposition local temps in each of the do: blocks won't change the semantics and will remove the need to initialize them explicitly. > > When I use the standard VM I'm able to update correctly > to the latest version pharo core 1.2 #12307 > > Maybe Eliot is able to reproduce and fix it. Until then I switch > to standard VM. > > Thx > Torsten > > > [1] > http://lists.gforge.inria.fr/pipermail/pharo-project/2011-January/039747.ht… > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de >

Jan. 18, 2011

Re: [Pharo-project] Example of XML SAX Parser usage

by HernÃ¡n Morales Durand

Hi Larry, I renamed the class to GTBLASTResultsParser. To try it you may evaluate GTBLASTResultReader new results: ( FileStream readOnlyFileNamed: 'K9W70UJU014-Alignment.xml' ); hitNodes which takes about 50 seconds on my machine over an alignment file of a nucleotide BLAST with 500 target sequences (a 18 Mb file). I suspect a considerable time is spent adding strings to a result collection, and improvements may be possible by choosing carefully the collections, it happens I haven't started to think about optimizations (just use it as a sample to see how it works). If anyone wants the sample alignment just drop me an e-mail. Cheers, 2011/1/17 Larry Gadallah <lgadallah(a)gmail.com>: > Hi all: > > I'm reviving a thread from long ago now that I've gotten a few minutes > to look at this question again: How is XML data best parsed using a > SAX parser in Pharo Smalltalk? > > I tried to look at the GenomeTools project that Miguel references > below, but it seems that the class he mentions (GTNCBIBlastParser) is > no longer in it. Perhaps there's a newer, better example of how to > drive the SAX parser somewhere? > >> Message: 4 >> Date: Tue, 20 Jul 2010 12:25:29 -0500 >> From: Miguel Enrique Cob? Mart?nez <miguel.coba(a)gmail.com> >> Subject: Re: [Pharo-project] Markup Builder in Smalltalk (XMLWriter) >> To: Pharo-project(a)lists.gforge.inria.fr >> Message-ID: <1279646729.2450.13.camel(a)laptop.localdomain> >> Content-Type: text/plain; charset="UTF-8" >> >> This good summary should go directly to the collaboractive book. >> >> >> El mar, 20-07-2010 a las 14:11 -0300, Hern?n Morales Durand escribi?: >>> A XML parser just creates a representation of a XML document according >>> to a parsing model. Ideally you should choose a XML parser >>> specifically for your needs. You have different parsing models: >>> >>> -Tree Parser: This is what you will read everywhere as the "DOM parser" >>> -Event Parser: This is denoted Â by S*X and could be >>> --SAX Parser: Known as the "Push parser" >>> --StAX Parser: Known also too as the "Pull parser" >>> -VTD Parser : This is known as "Virtual Token Descriptor" >>> >>> Now there are several classifications depending of the parser >>> characteristics and what you want to do or how. You may be interested >>> in: >>> >>> Making modifications or just processing? >>> -For modifications: The parser creates long-lived representations from >>> the XML document (necessary for modifications): You should choose DOM >>> or VTD >>> --Do you *need* to query or modify the objects (parser creates nodes): DOM >>> --You do not need the objects (parser creates integers and locations >>> caches): VTD >>> -For processing: The parser doesn't creates long-lived objects: SAX or StAX. >>> >>> Type of Access >>> -Back-and-forth: Access the data after the parsing is complete: DOM or VTD >>> --Massive or very frequent access: Choose DOM >>> --Rare or simple access: Choose VTD >>> -Sequential: Access the data while you're processing the document: SAX or StAX >>> --Processing all tokens: SAX >>> --Processing interested tokens (allows skipping forward): StAX >>> >>> Briefly >>> -Streaming applications (very large documents): SAX or StAX >>> -Database applications: DOM or VTD >>> -Hardware acceleration?: VTD >>> >>> For the S*X parsers you need to know the XML token types because, for >>> example in the case of XMLParser in Pharo/Squeak, you probably would >>> subclass SAXHandler and override one or several methods in the content >>> category to do your own processing. See GTNCBIBlastParser in >>> http://www.squeaksource.com/GenomeTools.html for an example of a SAX >>> Parser. >>> >>> XML token types: >>> Start element: <Hit>.... >>> End element: ...</Hit> >>> Text: <...>Text value</...> >>> etc. >>> >>> For DOM usage examples you may see >>> http://community.ofset.org/index.php/Les_bases_de_XML_dans_Squeak (it >>> is in french but is a good document) >>> >>> What we have in Pharo/Squeak >>> >>> Parsers: >>> 1) XMLParser : Supports SAX and DOM. http://www.squeaksource.com/XMLSupport.html >>> 2) VWXML Parser : Supports SAX and DOM (AFAIK) >>> http://www.squeaksource.com/VWXML.html >>> 3) XMLPullParser : Supports StAX. http://www.squeaksource.com/XMLPullParser.html >>> >>> XML Query tools >>> 1) Pastell : Supports X-Path like queries. Requires XMLParser. >>> http://www.squeaksource.com/Pastell.html >>> 2) XPath library : Supports XPath partially. Requires XMLParser. >>> http://www.squeaksource.com/XPath.html >>> >>> There are several additional tools in SqueakSource but I haven't reviewed yet. >>> A VTD parser would be ideal for Smalltalk because it uses integer >>> arrays reducing the object allocation overhead in memory. I haven't >>> found implementations of a XML VTD parser in Smalltalk as of today. >>> Cheers, >>> > > Thanks, > -- > Larry Gadallah, VE6VQ/W7Â Â Â Â Â Â Â Â Â Â Â Â Â lgadallah AT gmail DOT com > PGP Sig: 917E DDB7 C911 9EC1 0CD9Â C06B 06C4 835F 0BB8 7336 > > -- HernÃ¡n Morales Information Technology Manager, Institute of Veterinary Genetics. National Scientific and Technical Research Council (CONICET). La Plata (1900), Buenos Aires, Argentina. Telephone: +54 (0221) 421-1799. Internal: 422 Fax: 425-7980 or 421-1799.

Jan. 18, 2011

Re: [Pharo-project] Is there a http server that understands PUT?

by Norbert Hartl

On 17.01.2011, at 23:09, Sven Van Caekenberghe wrote: > > On 17 Jan 2011, at 22:10, Adrian Lienhard wrote: > >> Hi Norbert, >> >> I suggest to have a look at Zink: http://homepage.mac.com/svc/Zinc-HTTP-Components/index.html >> >> Cheers, >> Adrian > > The Zinc Seaside adaptor should support PUT, if not I would be happy to help figure out what goes wrong (please provide a standalone test case that we can run). Indeed. It was easy to set up and all my tests ran quite well. I didn't know it does proper mime structuring of data. Well done! As far as I can see this deserves the role of an important component. But now I have the problem that I have to port it to gemstone :) thanks, Norbert

Jan. 17, 2011

Re: [Pharo-project] Is there a http server that understands PUT?

by Norbert Hartl

On 17.01.2011, at 21:52, Janko MivÅ¡ek wrote: > Hi Norbert, > > On 17. 01. 2011 21:22, Norbert Hartl wrote: >> While trying to consume some PUT urls with Seaside-REST I noticed that the transmitted content is missing. I tried Comanche as well as swazoo. At this moment I'm not sure if I did something wrong but I seems that only GET and POST are treated. >> Does anyone has some experience on this? > > Swazoo certainly supports PUT, because it is used in Aida WebDAV support. > That is strange. I did test several things but now luck so far. In Comanche I have a body stream left with the mime data but in swazoo everything's consumed but no additional data created. Norbert

Jan. 17, 2011