mplementation).
> ___
> montyos.wordpress.com
>
>
>> Sent: Monday, June 18, 2018 at 1:34 AM
>> From: "Sven Van Caekenberghe"
>> To: "Any question about pharo is welcome"
>> Subject: Re: [Pharo-users] Lost in stream
>>
>>
>&
Recorded https://bugs.launchpad.net/drgeo/+bug/1777991
Le 21/06/2018 à 08:11, Hilaire a écrit :
I should, but there were changes in the API impacting its use in Dr.
Geo, and I have to concentrate on other matter first. Pavel did a port
on Github[1], but I failed to track on-line the changes to
I should, but there were changes in the API impacting its use in Dr.
Geo, and I have to concentrate on other matter first. Pavel did a port
on Github[1], but I failed to track on-line the changes to the code
related to Dr. Geo's use of XML. I will need time, or helps. I don't use
GitLab, so I h
https://ci.inria.fr/pharo-contribution/job/XMLParser/
You should be able to upgrade regardless of your Pharo version.
___
montyos.wordpress.com
> Sent: Wednesday, June 20, 2018 at 8:39 AM
> From: Hilaire
> To: pharo-users@lists.pharo.org
> Subject: Re: [Pharo-users] Lost in stream
No with Pharo, and pretty old XML parser version. But still this one was
always capable to parse entity
Le 18/06/2018 à 02:43, monty a écrit :
Are you developing in Squeak? I ask because the XML parser in the default Squeak image is very old.
You can download the latest Pharo XMLParser lib fr
Caekenberghe"
> To: "Any question about pharo is welcome"
> Subject: Re: [Pharo-users] Lost in stream
>
>
>
> > On 18 Jun 2018, at 02:18, monty wrote:
> >
> > Also consider using XMLParser's built-in file reading support:
> > #
> On 18 Jun 2018, at 02:18, monty wrote:
>
> Also consider using XMLParser's built-in file reading support:
> #parseFileNamed:/#onFileNamed:. They work cross platform (Squeak, GS), and
> handle character decoding.
Monty, do these (already) work with all the latest changes in Pharo 7, I mean
users@lists.pharo.org
> Subject: Re: [Pharo-users] Lost in stream
>
> Sometime you just need a good sleep, which I was fortunate to have.
>
> My newer code append contents to existing file, so it lead to corrupted
> files at the end. Ensuring it is deleted first solved th
work cross platform (Squeak, GS), and
handle character decoding.
___
montyos.wordpress.com
> Sent: Saturday, June 16, 2018 at 4:27 AM
> From: Hilaire
> To: pharo-users@lists.pharo.org
> Subject: Re: [Pharo-users] Lost in stream
>
> Sometime you just need a good sleep, which
Sometime you just need a good sleep, which I was fortunate to have.
My newer code append contents to existing file, so it lead to corrupted
files at the end. Ensuring it is deleted first solved the problem:
(location asFileReference / filename) ensureDelete binaryWriteStreamDo:
[ :fileStream
Le 15/06/2018 à 20:40, Sven Van Caekenberghe a écrit :
I don't see anything wrong with Toto-Wrong.png.
When loading like this I have space low detection:
PNGReadWriter formFromStream: 'Toto-Wrong.png' asFileReference
binaryReadStream
As for the XML part, the following seemed to work:
xmldo
I don't see anything wrong with Toto-Wrong.png.
As for the XML part, the following seemed to work:
xmldoc := (FileLocator desktop / 'Toto-ok.fgeo') readStreamDo: [ :in |
XMLDOMParser parse: in ].
(FileLocator desktop / 'drgeo.xml') writeStreamDo: [ :out | xmldoc writeXMLOn:
(XMLWriter on: out)
I investigated a bit more the other issue, and it looks like XML
entities are not correctly decoded when read from the newer File API.
Somehow it is related to stream I guess.
For example, drgeo document starting like:
are correctly decoded with DrGeo 17.07, but not with the newer one.
Whe
13 matches
Mail list logo
