- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Improving doc of XMLParser

by stepharo

Monty What would be really gorgeous is to revisite the method comments with the idea that people do not know SAX. characters: aString "This call corresponds to the Java SAX call characters(char[] ch, int start, int length)." was not really useful to me. I got no idea about it. So I started to redefine all the methods and put break put in them.... It was not really welcoming. I think that Pharo internal documentation should really improve because we cannot rely on Stack Overflow. And this means that people in that case prefer to develop in a language where they can find solutions instead of crawling. This is why the example effort should be also pushed further. Stef

March 12, 2016

Re: [Pharo-dev] Improving doc of XMLParser

by stepharo

Le 11/3/16 15:36, monty a Ã©crit : > The class comment (and other) could be better; it assumes you already know SAX-style parsing. I will improve it. > > I have been working on a tutorial that shows the usage of XMLParser and related libs (like XPath or XMLParserStAX). EXCELLENT!!!!!!!! > It is being structured like a chapter and formatted with Pillar, so it could go in one of your books (but not PBE, it's too specific for it). Superb. Yes there will be other books :) It would fit perfectly with the PullParser chapter Could you publish that in the squarebraket github repo? In PharoProgress for example Where can I read it? I'm eager to read it because I want to help this person. I produced a PullXMLParser out of Hernan blog I should add missing examples. https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/XMLP… > > Also, instead of: > >> h := MySAXHandler new >> on: FileSystem workingDirectory / 'FILMS.XML'. >> h parseDocument. > You just want: > > result := MySAXHandler parseFileNamed: 'FILMS.XML'. > > or if you want to configure it before parsing, you can use an on*: constructor + parseDocument: > > result := > (MySAXHandler onFileNamed: 'FILMS.XML') > "...configure the instance here.." > parseDocument. Yes I did it like that because I had to change the onFileNamed: because I do not know why but in the moose version I used there was a DNU related to asXMLHandleFile or something like that. > >> Sent: Friday, March 11, 2016 at 7:55 AM >> From: stepharo <stepharo(a)free.fr> >> To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Subject: [Pharo-dev] Improving doc of XMLParser >> >> Hi monty >> >> Yesterday one student ask me to import in Moose an XML document. >> I spent more than 15 min trying.... >> >> What would have really help is the following (could you add it into the >> class comment): >> Many of the comment do not help because are scarce and not precise enough. >> >> To use a SaxHandler subclass it >> >> >> >> SAXHandler subclass: #MySAXHandler >> instanceVariableNames: '' >> classVariableNames: '' >> category: 'MyXMLImporter' >> >> and redefine the method corresponding the notification you want for example: >> >> MySAXHandler>>startElement: aQualifiedName attributes: aDictionary >> >> self halt. >> >> Then to use it simply do >> >> | h | >> h := MySAXHandler new >> on: FileSystem workingDirectory / 'FILMS.XML'. >> h parseDocument. >> ^ h >> >> Your method startElement: aQualifiedName attributes: aDictionary should >> get invoked. >> >> >> I really think that having a tutorial on XML parser ***use*** is cruelly >> needed. >> >> >> >> Stef >> >> >> >> >> >> >> >

March 12, 2016

Re: [Pharo-dev] feedback from yet another student presentation

by stepharo

Thanks for the proposition. Stef Le 11/3/16 09:22, philippe.back(a)highoctane.be a Ã©crit : > > And that woukd be a nice thing to hack on during PharoDays. > > On Mar 11, 2016 9:22 AM, "philippe.back(a)highoctane.be > <mailto:philippe.back@highoctane.be>" <philippe.back(a)gmail.com > <mailto:philippe.back@gmail.com>> wrote: > > STH can be fixed. This is more like some data problem. > > Who can look at the system to identify issues? Is this a Mongo issue? > > Phil > > On Mar 11, 2016 8:17 AM, "Serge Stinckwich" > <serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com>> > wrote: > > On Fri, Mar 11, 2016 at 8:08 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > > > > > Le 10/3/16 22:14, Alexandre Bergel a Ã©crit : > >>> > >>> - it was reallllly hard to register a project on > smalltalkhub just after > >>> we created an account. > >>> This already happened to me during the open-devs. > >>> So this is a really big show stopper for the mooc. Because > people will > >>> gave up just after the first lecture :( > >> > >> The situation will be much easier I hope once git is well > supportedâ¦ > > > > > > But will we have to answer 100 of problems during the mooc? > > And if people drop after just because they cannot save their > code as we say > > it :( > > Yes this is real annoying problem ... Maybe you can ask > Gemstone to > support the MOOC > with a dedicated ss3 instance (or use ss3). > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >

March 12, 2016

Fwd: How to access XML tag name?

by stepharo

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>

March 11, 2016

New Cog VMs available

by Eliot Miranda

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3643 CogVM binaries as per VMMaker.oscog-eem.1722/r3643 General: Change vm parameter 65 to be a set of flags, not merely the boolean for MULTIPLE_BYTECODE_SETS, and make the flags answer MULTIPLE_BYTECODE_SETS & IMMUTABILITY. Nuke unused named prim primitiveOriginalMillisecondClock so VM can eliminate ioOldMSecs. Nuke ioOldMSecs and ioLowResMSecs to simplify the tiume management and avoid mistakes were we use different versions of clocks for different parts of the same basic io operations. Nuke SqueakUIFlushUseHighPercisionClock preference. Make the leak checker operational in the non-assert (& non-debug) VM. Cogit: Revise the register saving convention for trampoline calls. Instead of passing in a boolean to indicate if all registers should be saved or not (an aproach Ryan correctly notes is bogus), pass in a register mask of registers to be saved. If the trampoline call has a machine code continuation then the argument is usually callerSavedRegMask, and on MIPS and ARM this is empty. Use the above to move the saving of registers in the store-check into the store-check trampoline and out of the call of the trampoline. Further, use genJumpImmediate: in the immediate test, which saves an instruction. 64-bit Cogit: Fix primtive 171 (primitiveImmediateAsInteger) in the Cogit for SmallFloat. The old code only dealt with Characters. The new code replicates the rotatedFloatBitsOf: scheme in Spur64BitMemoryManager. Spur: Resolve the conflict between 32-bit and 64-bit tag assignments. In 32-bits we have 1=even SmallIntegers, 2=Characters, 3=odd SmallIntegers, and in 64-bits we had 1=SmallIntegers, 2=Characters, 3=SmallFloats. Hence we would want SmallFloat64's identityHash to be 3, which conflicts with 32 bits' odd SmallIntegers. Change is for 64-bits to use 1=SmallIntegers, 2=Characters, 4=SmallFloats. This also means single-bit tests in the Cogit, which produces better code, and no scratch registers to hold masked tags. Hence roll the 64-bit Spur image format version number from 68019 to 68021. Delegate to the object memories to determine the image format version number. Fix the bug in markAndTraceClassOf: that causes the first class table page to become a visible array. Plugins: Fix primitiveFFIIntegerAt for signed 4-byte results. Wuth the support for 64-bit results, signed 4-byte results must be sign-extended to 64-bits. Update primitiveFileRead for Spur. It doesn't need the PrimErrObjectMayMove handling since Spur has pinning. Don't use cCode: pointer aliasing for storing/fetching float/double in FFI primitives. Replace with a call to mem:cp:y: - the first one is dangerous with modern C compilers - while the second is optimized away (no call to memcpy) Fix a missing guard in SmartSyntaxPlugin like explained at http://forum.world.st/VM-safety-missing-failing-guards-in-SmartSyntaxPlugin… Fix two missing guards in VM profiling primitives: one should not use the result of stackObjectValue: before checking for success, otherwise a null pointer exception will occur in case of failure. _,,,^..^,,,_ best, Eliot

March 11, 2016

Re: [Pharo-dev] Improving doc of XMLParser

by monty

The class comment (and other) could be better; it assumes you already know SAX-style parsing. I will improve it. I have been working on a tutorial that shows the usage of XMLParser and related libs (like XPath or XMLParserStAX). It is being structured like a chapter and formatted with Pillar, so it could go in one of your books (but not PBE, it's too specific for it). Also, instead of: > h := MySAXHandler new > on: FileSystem workingDirectory / 'FILMS.XML'. > h parseDocument. You just want: result := MySAXHandler parseFileNamed: 'FILMS.XML'. or if you want to configure it before parsing, you can use an on*: constructor + parseDocument: result := (MySAXHandler onFileNamed: 'FILMS.XML') "...configure the instance here.." parseDocument. > Sent: Friday, March 11, 2016 at 7:55 AM > From: stepharo <stepharo(a)free.fr> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Subject: [Pharo-dev] Improving doc of XMLParser > > Hi monty > > Yesterday one student ask me to import in Moose an XML document. > I spent more than 15 min trying.... > > What would have really help is the following (could you add it into the > class comment): > Many of the comment do not help because are scarce and not precise enough. > > To use a SaxHandler subclass it > > > > SAXHandler subclass: #MySAXHandler > instanceVariableNames: '' > classVariableNames: '' > category: 'MyXMLImporter' > > and redefine the method corresponding the notification you want for example: > > MySAXHandler>>startElement: aQualifiedName attributes: aDictionary > > self halt. > > Then to use it simply do > > | h | > h := MySAXHandler new > on: FileSystem workingDirectory / 'FILMS.XML'. > h parseDocument. > ^ h > > Your method startElement: aQualifiedName attributes: aDictionary should > get invoked. > > > I really think that having a tutorial on XML parser ***use*** is cruelly > needed. > > > > Stef > > > > > > >

March 11, 2016

Re: [Pharo-dev] Improving doc of XMLParser

by Sven Van Caekenberghe

Stef, I hope/plan to be able to add that to my talk at the pharo days. Sven > On 11 Mar 2016, at 13:55, stepharo <stepharo(a)free.fr> wrote: > > Hi monty > > Yesterday one student ask me to import in Moose an XML document. > I spent more than 15 min trying.... > > What would have really help is the following (could you add it into the class comment): > Many of the comment do not help because are scarce and not precise enough. > > To use a SaxHandler subclass it > > > > SAXHandler subclass: #MySAXHandler > instanceVariableNames: '' > classVariableNames: '' > category: 'MyXMLImporter' > > and redefine the method corresponding the notification you want for example: > > MySAXHandler>>startElement: aQualifiedName attributes: aDictionary > > self halt. > > Then to use it simply do > > | h | > h := MySAXHandler new > on: FileSystem workingDirectory / 'FILMS.XML'. > h parseDocument. > ^ h > > Your method startElement: aQualifiedName attributes: aDictionary should get invoked. > > > I really think that having a tutorial on XML parser ***use*** is cruelly needed. > > > > Stef > > > > > >

March 11, 2016

Re: [Pharo-dev] feedback from yet another student presentation

by monty

Transport Layer Security, the successor of SSL (both implement https). > Sent: Friday, March 11, 2016 at 2:11 AM > From: stepharo <stepharo(a)free.fr> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] feedback from yet another student presentation > > > > Le 11/3/16 03:22, monty a Ã©crit : > > There's also the option of SS3 skinned to look like STH. We also really need TLS. > > what is TSL? > > > > > > Sent: Thursday, March 10, 2016 at 5:33 PM > > From: "phil(a)highoctane.be" <phil(a)highoctane.be> > > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > Subject: Re: [Pharo-dev] feedback from yet another student presentation > > > > SmalltalkHub looks like to have issues. > > e.g. Hilaire not being able to access the Mold project despite being a contributor. > > Removing/adding him didn't change much to the situation. > > > > We need to have more resources focusing on it as this is now a key part of our infrastructure. > > > > Phil > > > > On Thu, Mar 10, 2016 at 10:14 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:> - it was reallllly hard to register a project on smalltalkhub just after we created an account. > >> This already happened to me during the open-devs. > >> So this is a really big show stopper for the mooc. Because people will gave up just after the first lecture :( > > The situation will be much easier I hope once git is well supportedâ¦ > > > >> - we should really rename Class>>name: into setClassName: > >> students were manipulating object with name such as state of state machine and one wrote > >> > >> State name: 'A' and just rename the class and broke the system. > > I have just created an issue: > > https://pharo.fogbugz.com/f/cases/17798/Rename-Class-name-into-setClassName… > > > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu[http://www.bergel.eu] > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > >

March 11, 2016

[pharo-project/pharo-core] cd0546: 50636

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: cd0546cf067bf729331ded6385f3f1bb58df8a30 https://github.com/pharo-project/pharo-core/commit/cd0546cf067bf729331ded63… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-03-11 (Fri, 11 Mar 2016) Changed paths: M DebuggerActions.package/DebugAction.class/instance/actions/execute.st A DebuggerActions.package/DebugAction.class/instance/actions/notifyDebuggingActionAboutToExecute.st A DebuggerActions.package/DebugAction.class/instance/actions/preAction.st A DebuggerActions.package/DebugActionAboutToExecute.class/README.md A DebuggerActions.package/DebugActionAboutToExecute.class/class/as yet unclassified/forDebuggingAction_.st A DebuggerActions.package/DebugActionAboutToExecute.class/definition.st A DebuggerActions.package/DebugActionAboutToExecute.class/instance/accessing/action.st A DebuggerActions.package/DebugActionAboutToExecute.class/instance/accessing/action_.st M Kernel.package/Context.class/instance/private/isFailToken_.st M Kernel.package/Context.class/instance/private/isPrimFailToken_.st M MonticelloFileTree-Core.package/extension/MCFileRepositoryInspector/instance/refresh.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50635.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50636.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50635.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50636.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Text-Core.package/TextClassLink.class/instance/comparing/=.st A Text-Core.package/TextClassLink.class/instance/comparing/hash.st A Text-Core.package/TextLink.class/instance/comparing/=.st A Text-Core.package/TextLink.class/instance/comparing/hash.st M Text-Core.package/TextMethodLink.class/definition.st A Text-Core.package/TextMethodLink.class/instance/accessing/browseSenders.st A Text-Core.package/TextMethodLink.class/instance/comparing/=.st A Text-Core.package/TextMethodLink.class/instance/comparing/hash.st A Text-Core.package/TextVariableLink.class/instance/as yet unclassified/=.st A Text-Core.package/TextVariableLink.class/instance/as yet unclassified/hash.st Log Message: ----------- 50636 17504 TextLink + subclasses lacks implementation of #= and #hash https://pharo.fogbugz.com/f/cases/17504 17796 Debugger step over basicNew of proxies is not working https://pharo.fogbugz.com/f/cases/17796 17769 The debugger should trigger an event before executing a debugging action https://pharo.fogbugz.com/f/cases/17769 17655 Changes in package loading behavior https://pharo.fogbugz.com/f/cases/17655 http://files.pharo.org/image/50/50636.zip

March 11, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50636 Home: https://github.com/pharo-project/pharo-core

March 11, 2016