- Pharo-dev - lists.pharo.org

[Pharo-project] Example of XML SAX Parser usage
by Larry Gadallah Jan. 18, 2011

Jan. 18, 2011

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

2 1

Re: [Pharo-project] [Pharo-users] Where do I find KeyedSet?
by HernÃ¡n Morales Durand Jan. 17, 2011

Jan. 17, 2011

Hi Stef 2011/1/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Jan 14, 2011, at 6:24 PM, HernÃ¡n Morales Durand wrote: > >> Try PluggableSet >> >> http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg22890.ht… >> >> Is there a way for you guys to deprecate deleted classes or mantain a >> record of deleted behaviors? (IIRC VW did this from 2.x versions) > > We try but we do not have the engineers of VW. > Now find somebody that pay us just 3 engineers full time for two years and you will not > recognized pharo and its process. I know we are very few, but what about this idea, instead of just deleting a class we may adopt these simple rules: 1 - If deleting a class add the deleted class name somewhere (in a method?) 2 - If renaming a class, make the class to know its previous names like #previousNames (Norberto Manzanos implemented this for his own package management and I think is a great idea) doesn't require tools, just some consensus and maybe a modified #deleteClass to enforce this "policy" it sounds feasible for you? what do you think? HernÃ¡n

3 5

Re: [Pharo-project] new Cog VMs
by mkobetic＠gmail.com Jan. 17, 2011

Jan. 17, 2011

I'm probably doing something obviously wrong, but I have no luck with the Cog VM. It crashes immediately on startup even with the stock OneClick image. I downloaded the Pharo-1.1.1 OneClick images. Fetched the latest coglinux.tgz (r2340), untarred it into the pharo directory and just trying to run it from the top-level pharo directory as: coglinux/squeak Contents/Resources/pharo.image crashes immediately (with or without the -vm-display-X11 option). This is on latest Fedora 14. The old VM seems to have no problem when I try to run it the same way: Contents/Linux/squeakvm Contents/Resources/pharo.image seems to start just fine. I can copy the stack dump from the crash, but since most seem to be running fine, I suspect I'm just not doing it right. What am I missing ? Thanks, Martin "Eliot Miranda"<eliot.miranda(a)gmail.com> wrote: > there are new versions of both the SimpleStackBasedCogit and the > StackToRegisterMappingCogit Cog VMs in > VM.r2339/<http://www.mirandabanda.org/files/Cog/VM/VM.r2339/> > & VM.r2340/ <http://www.mirandabanda.org/files/Cog/VM/VM.r2340/> respectively. > These contain fixes for rounding bug causing underestimate of openPICSize > and resultant hard crashes, seen e.g. by trying to recover lost changes in a > Pharo 1.2 image installed on c:\pharo. If you're trying to reproduce Cog > crashes please upgrade to one of tthese two VMs.

5 9

[Pharo-project] [update 1.2] #12309
by Marcus Denker Jan. 17, 2011

Jan. 17, 2011

12309 ----- Issue 3542: Add SmalltalkImage>>#gcBiasToGrow: and friends to core -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] pharogenesis
by Max Leske Jan. 17, 2011

Jan. 17, 2011

Hi everyone. For those of you who followed my github repository for pharogenesis, please note that I moved it to github.com/pharogenesis/pharogenesis. I deleted the old repository. Cheers, Max

5 10

[Pharo-project] 502 Bad Gateway
by HwaJong Oh Jan. 17, 2011

Jan. 17, 2011

I have this error while copying mcz file from my directory repo to pharoInbox. It was working well a minute ago. 'HTTP/1.1 502 Bad Gateway Date: Mon, 17 Jan 2011 02:20:01 GMT Server: Apache/1.3.41 (Darwin) mod_jk/1.2.6 mod_ssl/2.8.31 OpenSSL/0.9.7l PHP/4.4.9 Last-Modified: Fri, 22 Dec 2006 12:14:34 GMT ETag: "ee86f-a68-458bcc2a" Accept-Ranges: bytes Content-Length: 2664 Connection: close Content-Type: text/html<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <link rel="stylesheet" type="text/css" href="/squeaksource/style.css" /> <meta name="verify-v1" content="aYJ5chz2x0fRQuxMBS4pW+Ikb7hgtaBsysf18Fbt3q8=" /> <title>SqueakSource</title> </head> <body> <div id="container"> <div id="top"> </div> <div id="sstoolbar"> http://www.squeaksource.com/ Home http://www.squeaksource.com/ Projects http://www.squeaksource.com/ Tags http://www.squeaksource.com/ Members http://www.squeaksource.com/ Groups http://www.squeaksource.com/ Help </div> <div id="page"> <div id="navigation"> <div class="title"> Actions </div> <div class="item"> http://www.squeaksource.com/ Refresh </div> </div> <div id="contents"> <h1>SqueakSource Down</h1> <p style="font-weight: bold; margin-left: 20px; margin-right: 220px; line-height: 1.5em"> SqueakSource is currently down. We are sorry for the inconvenience and working on the problem. In the meantime you can still commit to a directory repository on your disk and later copy the versions to SqueakSource.</p> <p>This service is brought to you for free: it is backed up daily. Still, please make sure that you have your own proper backups and note that we cannot give any accessibility guarantees. However, if you wish you can set up your own SqueakSource server. It is self-hosted and can be downloaded from SqueakMap.</p> <p>Please report any problems or suggestions to the Squeak http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/squeak-dev Mailing-List . Enjoy!</p> <p>We gratefully acknowledge the support of the http://www.iam.unibe.ch/%7Escg/ Software Composition Group and the http://www.unibe.ch/ University of Bern for hosting this service.</p> </div> <div id="bottom"> <table width="100%" border="0" cellspacing="0" cellpadding="0"> <tr> <td align="left"> http://validator.w3.org/check/referer XHTML | http://jigsaw.w3.org/css-validator/check/referer CSS </td> <td align="right">It''s a sad day</td> </tr> </table> </div> </div> </body> </html> ' -- View this message in context: http://forum.world.st/502-Bad-Gateway-tp3220636p3220636.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 2

[Pharo-project] Pharo issues on Google
by Gary Chambers Jan. 17, 2011

Jan. 17, 2011

Is the Pharo issues google site not working? Regards, Gary

3 5

[Pharo-project] [ANN 1.2] pre-build core 1.2#12308
by Marcus Denker Jan. 17, 2011

Jan. 17, 2011

https://gforge.inria.fr/frs/download.php/28154/PharoCore-1.2beta-12308.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [update 1.2] #12308
by Marcus Denker Jan. 17, 2011

Jan. 17, 2011

12308 ----- Issue 3541: TextConverter should take into account iso Issue 3498: remove:ifAbsent: in linked list leads to interruption/sync problems -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3541 in pharo: TextConverter should take into account iso
by pharo＠googlecode.com Jan. 17, 2011

Jan. 17, 2011

Status: Accepted Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3541 by stephane...(a)gmail.com: TextConverter should take into account iso http://code.google.com/p/pharo/issues/detail?id=3541 After loading ConfigurationOfXML try to parse it: |fs| fs := FileStream fileNamed: 'test.xml'. XMLDOMParser parseDocumentFrom: fs. => gives an error: 'Invalid utf8 input detected' => it works if you remove the CDATA section Looks like UTF8TextConverter is used independent from the encoding of the XML... -------------- Torsten, what you are trying to do is not incorrect and should work as you expected it to. The reason why it didn't has less to do with XMLSupport per se and more to do with its reliance on Pharo's TextConverter system. The problem is faulty matching of the "encoding" attribute value to the appropriate subclass of TextConverter. The code responsible for this in XMLSupport is: converterClass := (Smalltalk at: #TextConverter ifAbsent: [^ self]) defaultConverterClassForEncoding: anEncodingName asLowercase. But as you can see, the matching is actually done by TextConverter and its class-side #defaultConverterClassForEncoding: method, which works by sending #encodingNames to all subclasses and testing the array returned to see if it includes the specified encoding name. If you browse Latin1TextConverter, the right class for the encoding you specified, and look at its #encodingNames message, you will see the array it returns does not include "ISO-8859-1": ^ #('latin-1' 'latin1') copy. Change it to this (note the lowercase): ^ #('latin-1' 'latin1' 'iso-8859-1') copy. and everything now works. So this is really a bug in TextConverter and its Latin1TextConverter subclass, not XMLSupport. Also, the #allSubclassesDo: test in #defaultConverterClassForEncoding: should probably be augmented with a Dictionary cache to speed-up lookups for known encoding-converter pairs. Can someone forward this message to whoever maintains TextConverter?

1 4