September 2015 - Pharo-users

Re: [Pharo-users] Remember the math sequence ?

by Ben Coman

Interesting to watch, but it wasn't clear if there was a particular "named" sequence you were using (too long since high school to remember) cheers -ben On Fri, Sep 18, 2015 at 8:25 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Remember the mathemactic sequence in senior hight? > > https://plus.google.com/+DrgeoEu/posts/fBh8fGPzUK4 > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > http://google.com/+DrgeoEu > > >

Sept. 18, 2015

Remember the math sequence ?

by Hilaire

Remember the mathemactic sequence in senior hight? https://plus.google.com/+DrgeoEu/posts/fBh8fGPzUK4 Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu

Sept. 18, 2015

Re: [Pharo-users] XML Viewer and XML syntax highlighting

by Tudor Girba

Indeed, you need a parser and afterwards you can use the same approach as I used for the styling Pillar in Rubric: http://www.humane-assessment.com/blog/writing-pillar-books-with-the-gtinspe… Cheers, Doru On Fri, Sep 18, 2015 at 12:20 AM, monty <monty2(a)programmer.net> wrote: > What's needed is a highlight/styling widget that works with GT that can > also be treated like an ordinary write stream. Then you subclass > XMLPrettyPrintingWriterFormatter and override the formatting messages to > style the stream differently at certain points (like before a start tag, > after a start tag). Then change the GT "Source" pane XMLParser method to > use "self writeXMLOn: (XMLWriter on: highlightStream formatter: > highlightFormatter)". > > The one drawback (besides performance) is that XMLWriter formatting > support is just before/after tags, comments, and other markup elements. You > can't add formatting within a start tag, which would be an issue if you > want to style text in attr/xmlns values differently. I could fix this by > adding more formatting messages to XMLWriter for before/after string values. > > Does anyone (Doru?) have more info on the GT aspects? > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 18, 2015

Re: [Pharo-users] XPath (was String vs Symbol use cases)

by monty

I understand the problem and I'm studying possible fixes while reviewing the specs, but I need more time. if you could work around it for now, that would be good. I will update you by mail.

Sept. 18, 2015

Re: [Pharo-users] XML Viewer and XML syntax highlighting

by monty

What's needed is a highlight/styling widget that works with GT that can also be treated like an ordinary write stream. Then you subclass XMLPrettyPrintingWriterFormatter and override the formatting messages to style the stream differently at certain points (like before a start tag, after a start tag). Then change the GT "Source" pane XMLParser method to use "self writeXMLOn: (XMLWriter on: highlightStream formatter: highlightFormatter)". The one drawback (besides performance) is that XMLWriter formatting support is just before/after tags, comments, and other markup elements. You can't add formatting within a start tag, which would be an issue if you want to style text in attr/xmlns values differently. I could fix this by adding more formatting messages to XMLWriter for before/after string values. Does anyone (Doru?) have more info on the GT aspects?

Sept. 17, 2015

XPath (was String vs Symbol use cases)

by Peter UhnÃ¡k

Hi monty, thanks for your answers. The original question wasn't really aimed at XPath, it was just an example, however you raise some important points which I should keep in mind. Now for the XPath itself, I seem to have run into a bug Imagine xml ~~~~~~~~~ <?xml version="1.0" encoding="UTF-8"?> <root> <node id="a"> <node id="a.1" /> <node id="a.2" /> </node> <node id="b"> <node id="b.1" /> <node id="b.2" /> </node> </root> ~~~~~~~~~~~~~~~~ and an xpath '//node[position()=2]' This should return collection containing nodes "b","a.2","b.2", however in Pharo it returns collection with "a.1" Is this something that can be easily fixed? If not I would prefer to work around it than wait for fix. Thanks, Peter

Sept. 17, 2015

Re: [Pharo-users] String vs Symbol use cases

by monty

Hernan maintained the old lib. The PharoExtras/XPath lib you get from the catalog or config browsers was rewritten and questions/bugs should be sent to me. Note it is incompatible with Pastell, so you can't have both in the same image. > Sent: Thursday, September 17, 2015 at 4:07 PM > From: "Alexandre Bergel" <alexandre.bergel(a)me.com> > To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] String vs Symbol use cases > > Ah okay! > > Alexandre > > > > On Sep 17, 2015, at 2:55 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > You are here defining a small api to formulate xpath queries, which is great. > > > > Nono, this is XPath library by Hernan (available from Catalog Browser), I'm just using it. > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Sept. 17, 2015

Re: [Pharo-users] String vs Symbol use cases

by monty

> Remember the xPath: usage gives access to full XPath syntax (not just axis and nametests), including predicates, functions, and variables. XPath is really a different language so mapping it all to a ST DSL is tricky. For example, XPath 1.0 is weakly typed so "1" = 1 = "1.0" but clearly this is false in ST. Be aware of the differences when you go from one to the other. By this I mean XPath has many JavaScript style implicit conversions. for example, if an XPath predicate evaluates to a node set, it's converted to a boolean: true if non-empty, false otherwise. Collections in ST obviously aren't converted automatically to true or false when used with ifTrue:ifFalse:.

Sept. 17, 2015

Re: [Pharo-users] String vs Symbol use cases

by monty

Peter, the XPath lib was rewritten not long ago to provide full XPath 1.0 support + extensions, so feel free to mail me with questions or bugs. The old lib didn't implement the whole spec and would crash or infinite loop on valid input, so I felt a rewrite was needed. > myDocument xPath: #'entity/@name' I think treating Symbols as Strings is a bad idea. On GS, Symbols aren't Strings, and #foo = 'foo' is false, so in the XPath lib itself (which now supports GS), I NEVER use Symbols as Strings. But on Squeak/Pharo, this won't hurt you. if you don't need porting, do what you like. > myDocument / 'entity' @ 'name' This is the "DSL" syntax. There are binary messages for each XPath axis: // for "descendant", //~ for "descendant-or-self", ~ for "self" and more in the "enumerating - axis" category. The XPath compiler actually generates sends of these but with block arguments that don't need parsing (string arguments are treated as NameTests and can have wildcard or type tests like '*', '*:foo', or 'text()'). Because the string args are parsed every time, using xPath: can be faster if you save the compiled XPath (like in an inst/class var: "savedXPath := 'some/path' asXPath") and reuse it (with "aNode xPath: savedXPath"). There's also a global compiled XPath cache that's checked before compiling an expression, so xPath: can still be faster even if you don't bother saving. Remember the xPath: usage gives access to full XPath syntax (not just axis and nametests), including predicates, functions, and variables. XPath is really a different language so mapping it all to a ST DSL is tricky. For example, XPath 1.0 is weakly typed so "1" = 1 = "1.0" but clearly this is false in ST. Be aware of the differences when you go from one to the other.

Sept. 17, 2015

Re: [Pharo-users] String vs Symbol use cases

by Alexandre Bergel

Ah okay! Alexandre > On Sep 17, 2015, at 2:55 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > You are here defining a small api to formulate xpath queries, which is great. > > Nono, this is XPath library by Hernan (available from Catalog Browser), I'm just using it. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 17, 2015