Something went wrong during your upgrade with class initialization.
Installing the latest versions of these projects into a clean image would work,
and so would installing the latest XMLParserHTML and XMLParserStAX into the
newest Moose-6.1 image (which has the latest XMLParser and XPath).
But
Monty
As an update, I have rebuilt from the Moose 6.0 download. The version of
XML-Parser in that was dated 18 July 2016 (configuration monty.233), so I
installed versions of XML-Parser-HTML and XML-Parser-StAX contemporary with
that. (The respective configurations are monty.48 and monty.39). W
Monty
I have just started trying to use the StAX parsers, and I have found that the
update has introduced a problem, which means that XMLHTMLParser no longer works
on examples I have used before. I updated to
ConfigurationOfXMLParser(monty.302), which is the latest version on the
smalltalkhub
Monty
Many thanks for this. My original purpose was just to answer Paul deBruicker's
query, namely to parse an html file and stop reading at the end of the
section. I solved this by trial and error using the code shown below ( which
actually stops at the opening tag of the body). This was not
Is there a bind key to jump to the next argument slot? After using TAB for
method completion, I wonder if there's a key/command to jump to the next
argument slot. I checked the keymap browser and either it isn't there or I
missed it.
The closest I've done so far is Meta + Right, but this needs to
Heya folks,
I have a laptop with a 3K screen. Is it possible to tell Pharo to render
everything at a double resolution or something? I feel like this ought
to have been a solved problem already, sorry if it's really obvious and
I just haven't found it.
I use Debian if that matters; I suspect this
Hello,
At Synectique a client reported us a problem that we cannot reproduce.
The vm crash and the error displayed is:
stack page bytes 4096 available headroom 3300 minimum unused headroom 1880
launchServer.sh: line 2: 34556 Aborted (core dumped)
pharo-linux-vm/pharo Pharo.image
For that kind of incremental parsing, you could also use XMLParserStAX, a
pull-parser that parses a document as a stream of event objects you control
with #next, #peek, and #atEnd. It also supports pull-DOM parsing with messages
like #nextNode, #nextElement, and #nextElementNamed:, which return
