March 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] How to access XML tag name?

by Alexandre Bergel

Pastell is an implementation of XPath. But I had a look at it many years ago (when I was extracting data from srcML xml files, you remember? :-) Alexandre > On Mar 13, 2016, at 1:39 PM, stepharo <stepharo(a)free.fr> wrote: > > Alex > > what Pastell brings compared to XPath? > > Stef > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 13, 2016

Re: [Pharo-users] Roassal2 on Ubuntu 64

by Peter UhnÃ¡k

> > $ sudo apt-get install libcairo2:i386 > This is sufficient for both Ubuntu and Debian (and probably their forks, such as Mint). Peter

March 13, 2016

Re: [Pharo-users] Beginner's question on morphs

by Stephan Eggermont

http://ws.stfx.eu/4I40UQDA50U0 shows how to add scaling. Stephan

March 13, 2016

Re: [Pharo-users] Beginner's question on morphs

by Henrik Nergaard

http://ws.stfx.eu/1RCNV18R5J7E Best regards, Henrik -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Markus Stumptner Sent: Sunday, March 13, 2016 2:49 PM To: pharo-users(a)lists.pharo.org Subject: [Pharo-users] Beginner's question on morphs Hi, I'm trying to refamiliarize with Pharo again after a few years... trying to set up a simple game window that uses a very large scrollable game board with a huge image as the background, so that game pieces placed on that background would scroll in and out of view. Any hints as how to best set that up in Morphic? Thanks Markus

March 13, 2016

Beginner's question on morphs

by Markus Stumptner

Hi, I'm trying to refamiliarize with Pharo again after a few years... trying to set up a simple game window that uses a very large scrollable game board with a huge image as the background, so that game pieces placed on that background would scroll in and out of view. Any hints as how to best set that up in Morphic? Thanks Markus

March 13, 2016

Re: [Pharo-users] How to access XML tag name?

by Tudor Girba

XPath is better than Pastell. That is why in Moose we now have XPath. Doru > On Mar 13, 2016, at 1:49 PM, stepharo <stepharo(a)free.fr> wrote: > > Alex > > I saw that Pastell is only tagged for Pharo30 and has not metadata. > It would be good to revise it. > > Stef > -- www.tudorgirba.com www.feenk.com "Every successful trip needs a suitable vehicle."

March 13, 2016

Re: [Pharo-users] How to access XML tag name?

by Tudor Girba

Hi, Yes, exactly. You get a qualified DOM with a hierarchy that you can afterwards visit. Only the current implementation only works only with the XMLDOMParser. It does not work with SAX. Cheers, Doru > On Mar 13, 2016, at 12:55 PM, stepharo <stepharo(a)free.fr> wrote: > > I have the impression that I should also look at > > XMLPluggableElementFactory new handleElement: 'NOM' withClass: AAAName. > > Because it looks like that I inject my nodes inside the dom > > Am I correct? > > > Le 12/3/16 21:59, Tudor Girba a Ã©crit : >> Hi, >> >> My original work only survived for the XMLDOMParser. See this example: >> http://ws.stfx.eu/NK2WLSW99X10 >> (paste this in Spotter :)) >> >> For an XMLDOMParser, you can say that you want to instantiate a node in the DOM with an custom instance. For example, here I instantiate <NOM> with AAAName: >> >> <Mail Attachment.png> >> >> You are looking for something a bit different. In a way you want to associate the triggering of a specific handler when some XPath like expression is being matched for the current element. I think something like this should go in the main implementation. >> >> Cheers, >> Doru >> >> >> >>> On Mar 12, 2016, at 9:33 AM, stepharo <stepharo(a)free.fr> wrote: >>> >>> This is more complex than that. >>> Because I would like to have a visitor generated from the token I give. >>> >>> And this >>> start >>> character >>> end >>> >>> does not really help me. >>> >>> Because in SAXHandler I have >>> start >>> where I should store the properties >>> same in characters: >>> to store the name >>> end >>> where I should invoke the visitor >>> >>> Now it means that I should only store the information for the tag I want. >>> Does anybody already did that and publish it? >>> I know doru did that in the past. >>> I will try. >>> >>> Stef >>> >>> >>> >>> Le 11/3/16 14:17, Blondeau Vincent a Ã©crit : >>>> Hi, >>>> >>>> The qualified name in function startElement: aQualifiedName attributes: aDictionary, will be FILMS and after FILM and after TITRE,...etc... >>>> So, you have to tell to your shouldVisit: method to accept TITRE too and get in and after you should implement characters: to get the content on the tag. >>>> >>>> Vincent >>>> >>>>> -----Message d'origine----- >>>>> De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de >>>>> stepharo >>>>> EnvoyÃ© : vendredi 11 mars 2016 14:04 >>>>> Ã : Any question about pharo is welcome >>>>> Objet : [Pharo-users] How to access XML tag name? >>>>> >>>>> Hi >>>>> >>>>> Yesterday I started to hack a smart SAX handler. The idea is that I want to just >>>>> specify the tags I want to visit and the SAX handler should invoke (generated) >>>>> visit methods. Like that I can easily get visitors on XML domain. >>>>> >>>>> Here is an example of what I did. >>>>> >>>>> | h | >>>>> h := SmartSAXHandler new >>>>> visitor: (MyFilmVisitor new visitTags: #(FILM ROLE)); >>>>> on: FileSystem workingDirectory / 'FILMS.XML'. >>>>> h parseDocument. >>>>> ^ h >>>>> >>>>> >>>>> >>>>> SmartSAXHAndler >> startElement: aQualifiedName attributes: aDictionary >>>>> >>>>> (visitor shouldVisit: aQualifiedName) >>>>> ifTrue: [ >>>>> visitor >>>>> perform: (visitor createdVisitSelector: aQualifiedName) >>>>> with: aQualifiedName >>>>> with: aDictionary >>>>> ] >>>>> >>>>> >>>>> Object subclass: #GenericTagSAXVisitor >>>>> instanceVariableNames: 'visitTag visitTags' >>>>> classVariableNames: '' >>>>> category: 'SmartXMLHandler' >>>>> >>>>> >>>>> GenericTagSAXVisitor>>visitTags: aCollection >>>>> "set the tags that will lead to a call to a visitTag:with: method in the visitor" >>>>> >>>>> visitTags := aCollection collect: [ :each | each asLowercase ]. >>>>> self createVisitMethods. >>>>> >>>>> and in a subclass the visit* methods automatically generated >>>>> >>>>> >>>>> Now I could not get when I have a <TITRE>Vertigo</TITRE> where I can get the >>>>> Vertigo information. >>>>> I redefined several methods of SAXhandler but without success. >>>>> >>>>> >>>>> <?xml version="1.0" encoding="iso-8859-1"?> >>>>> <FILMS> >>>>> <FILM annee="1958"> >>>>> <TITRE>Vertigo</TITRE> >>>>> <GENRE>Drame</GENRE> >>>>> <PAYS>USA</PAYS> >>>>> <MES idref="3"/> >>>>> <ROLES> >>>>> <ROLE> >>>>> <PRENOM>James</PRENOM> >>>>> <NOM>Stewart</NOM> >>>>> <INTITULE>John Ferguson</INTITULE> >>>>> </ROLE> >>>>> <ROLE> >>>>> <PRENOM>Kim</PRENOM> >>>>> <NOM>Novak</NOM> >>>>> <INTITULE>Madeleine Elster</INTITULE> >>>>> </ROLE> >>>>> </ROLES> >>>>> <RESUME>Scottie Ferguson, ancien inspecteur de police, est sujet >>>>> au vertige depuis qu'il a vu mourir son >>>>> collegue. Elster, son ami, le charge de surveiller sa femme, >>>>> Madeleine, ayant des tendances >>>>> suicidaires. Amoureux de la jeune femme Scottie ne remarque pas le >>>>> piege qui se trame autour >>>>> de lui et dont il va etre la victime... </RESUME> >>>>> </FILM> >>>> >>>> !!!************************************************************************************* >>>> "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. >>>> >>>> This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!" >>> >>> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "We can create beautiful models in a vacuum. >> But, to get them effective we have to deal with the inconvenience of reality." >> > -- www.tudorgirba.com www.feenk.com "Reasonable is what we are accustomed with."

March 13, 2016

Re: [Pharo-users] Re RFC Minecraft Server

by stepharo

One guy told me that he is using with his kids http://www.minetest.net/ Le 13/3/16 13:44, Andy Burnett a Ã©crit : > Ben said > >>> > Which one? > <<< > > The one people seem to use is called pocket mine. > (https://www.pocketmine.net) There may be others. > > >>> > I was thinking of the standard PC version since I understood the PE > version was not so amenable to mods. Actually my kids have been > playing PE edition on iPads, and I bought them second hand laptops to > run the PC edition to do modding. Still discovering how it all works. > <<< > > The PE (iPad etc) version seems to be catching up in terms of > features, and it does allow some level of mods. However, I agree that > the full PC version is probably the better target. > > I wonder if there are any docs that list the Api we need to support. >

March 13, 2016

Re: [Pharo-users] How to access XML tag name?

by stepharo

Alex I saw that Pastell is only tagged for Pharo30 and has not metadata. It would be good to revise it. Stef

March 13, 2016

Re: [Pharo-users] How to access XML tag name?

by stepharo

Le 13/3/16 13:33, stepharo a Ã©crit : > Hi alex > > I do not know :) > I like visitor because they are better than a series of if. > So I will see. I would like to help people to extract their > information easily. > May be inside the visitNode I could use XPath (do you know what is the > constraint to use XPath) > does it work on dom objects? > > I would like to have something like that (being able to use some node > to perform custom actions) > Now I do not see how from one visit method I can access the other. and > if I do not do it in the visit > what is the information I should store (like parent link) to be able > to identify that a given role is associated to a given film. > > visitFilm > title := self extractFromChildren: #Titre. > pays := self extractFromChildren: #Pays. > self newFilm: title from: pays. in fact for subnodes like role I should just continue the visit flow and get But I will keep in mind XPath. It would be grtea to have tutorial on all these XML technologies - SAX - DOM - PullParser - XPath queries / Pastell - Opax It could be XML in Pharo a nice book > > > visitRole > > <FILM annee="1958"> > <TITRE>Vertigo</TITRE> > <GENRE>Drame</GENRE> > <PAYS>USA</PAYS> > <MES idref="3"/> > <ROLES> > <ROLE> > <PRENOM>James</PRENOM> > <NOM>Stewart</NOM> > <INTITULE>John Ferguson</INTITULE> > </ROLE> > <ROLE> > <PRENOM>Kim</PRENOM> > <NOM>Novak</NOM> > <INTITULE>Madeleine Elster</INTITULE> > </ROLE> > > > > Stef > > > Le 13/3/16 11:26, Alexandre Bergel a Ã©crit : >> Hi Stef, >> >> I have the impression that a visitor is not the ideal solution to >> query XML tree. It works well in some case, and it is disastrous in >> some other. >> XPath is the way to query XML data. As far as I know, there is no >> complete support. Pastell was a nice try however... >> >> Alexandre >> >> >>> On Mar 12, 2016, at 8:11 AM, stepharo <stepharo(a)free.fr> wrote: >>> >>> Thanks >>> >>> Ok it was characters: I will try it >>> What a bad name! >>> >>> I will probably have to build a stack or dictionary of dictionary of >>> the part that I will not want to visit but this is another story :) >>> >>> Stef >>> >>> >>> Le 11/3/16 14:17, Blondeau Vincent a Ã©crit : >>>> Hi, >>>> >>>> The qualified name in function startElement: aQualifiedName >>>> attributes: aDictionary, will be FILMS and after FILM and after >>>> TITRE,...etc... >>>> So, you have to tell to your shouldVisit: method to accept TITRE >>>> too and get in and after you should implement characters: to get >>>> the content on the tag. >>>> >>>> Vincent >>>> >>>>> -----Message d'origine----- >>>>> De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De >>>>> la part de >>>>> stepharo >>>>> EnvoyÃ© : vendredi 11 mars 2016 14:04 >>>>> Ã : Any question about pharo is welcome >>>>> Objet : [Pharo-users] How to access XML tag name? >>>>> >>>>> Hi >>>>> >>>>> Yesterday I started to hack a smart SAX handler. The idea is that >>>>> I want to just >>>>> specify the tags I want to visit and the SAX handler should invoke >>>>> (generated) >>>>> visit methods. Like that I can easily get visitors on XML domain. >>>>> >>>>> Here is an example of what I did. >>>>> >>>>> | h | >>>>> h := SmartSAXHandler new >>>>> visitor: (MyFilmVisitor new visitTags: #(FILM >>>>> ROLE)); >>>>> on: FileSystem workingDirectory / 'FILMS.XML'. >>>>> h parseDocument. >>>>> ^ h >>>>> >>>>> >>>>> >>>>> SmartSAXHAndler >> startElement: aQualifiedName attributes: >>>>> aDictionary >>>>> >>>>> (visitor shouldVisit: aQualifiedName) >>>>> ifTrue: [ >>>>> visitor >>>>> perform: (visitor createdVisitSelector: >>>>> aQualifiedName) >>>>> with: aQualifiedName >>>>> with: aDictionary >>>>> ] >>>>> >>>>> >>>>> Object subclass: #GenericTagSAXVisitor >>>>> instanceVariableNames: 'visitTag visitTags' >>>>> classVariableNames: '' >>>>> category: 'SmartXMLHandler' >>>>> >>>>> >>>>> GenericTagSAXVisitor>>visitTags: aCollection >>>>> "set the tags that will lead to a call to a visitTag:with: >>>>> method in the visitor" >>>>> >>>>> visitTags := aCollection collect: [ :each | each asLowercase ]. >>>>> self createVisitMethods. >>>>> >>>>> and in a subclass the visit* methods automatically generated >>>>> >>>>> >>>>> Now I could not get when I have a <TITRE>Vertigo</TITRE> where I >>>>> can get the >>>>> Vertigo information. >>>>> I redefined several methods of SAXhandler but without success. >>>>> >>>>> >>>>> <?xml version="1.0" encoding="iso-8859-1"?> >>>>> <FILMS> >>>>> <FILM annee="1958"> >>>>> <TITRE>Vertigo</TITRE> >>>>> <GENRE>Drame</GENRE> >>>>> <PAYS>USA</PAYS> >>>>> <MES idref="3"/> >>>>> <ROLES> >>>>> <ROLE> >>>>> <PRENOM>James</PRENOM> >>>>> <NOM>Stewart</NOM> >>>>> <INTITULE>John Ferguson</INTITULE> >>>>> </ROLE> >>>>> <ROLE> >>>>> <PRENOM>Kim</PRENOM> >>>>> <NOM>Novak</NOM> >>>>> <INTITULE>Madeleine Elster</INTITULE> >>>>> </ROLE> >>>>> </ROLES> >>>>> <RESUME>Scottie Ferguson, ancien inspecteur de police, est >>>>> sujet >>>>> au vertige depuis qu'il a vu mourir son >>>>> collegue. Elster, son ami, le charge de surveiller sa femme, >>>>> Madeleine, ayant des tendances >>>>> suicidaires. Amoureux de la jeune femme Scottie ne remarque pas le >>>>> piege qui se trame autour >>>>> de lui et dont il va etre la victime... </RESUME> >>>>> </FILM> >>>> !!!************************************************************************************* >>>> >>>> "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã >>>> l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre >>>> protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par >>>> erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le >>>> dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur >>>> Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e >>>> quant au contenu de ce message. Bien que les meilleurs efforts >>>> soient faits pour maintenir cette transmission exempte de tout >>>> virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa >>>> responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage >>>> rÃ©sultant d'un virus transmis. >>>> >>>> This e-mail and the documents attached are confidential and >>>> intended solely for the addressee; it may also be privileged. If >>>> you receive this e-mail in error, please notify the sender >>>> immediately and destroy it. As its integrity cannot be secured on >>>> the Internet, the Worldline liability cannot be triggered for the >>>> message content. Although the sender endeavours to maintain a >>>> computer virus-free network, the sender does not warrant that this >>>> transmission is virus-free and will not be liable for any damages >>>> resulting from any virus transmitted.!!!" >>> > > >

March 13, 2016