l have to be added to
> ZnUrl or to a helper class, but that will take some time. Luckily there are
> test cases in the document.
>
> Thanks for the feedback.
>
> Sven
>
>> Hope this helps.
>>
>> Peter Kenny
>>
>> -Original Message-
Hello All
Just a follow-up to this query posted three weeks ago. I was e-mailed a week
ago by Monty telling me about an alternative approach to my problem:
"Hi Peter. I'm writing you because of your post on the Pharo users list two
weeks ago on problems with Todd Blanchard's HTML/CSS parser
o:pharo-users-boun...@lists.pharo.org] On Behalf Of
> Sven Van Caekenberghe
> Sent: 10 January 2015 22:56
> To: Any question about pharo is welcome
> Subject: Re: [Pharo-users] Problem due to deprecation of class Url in Pharo
> 3 and Moose 5.0
>
> Peter,
>
>> On 10 Jan
nuary 2015 16:36
To: Any question about pharo is welcome
Subject: Re: [Pharo-users] Problem due to deprecation of class Url in Pharo
3 and Moose 5.0
On 10 Jan 2015, at 16:45, stepharo wrote:
Le 10/1/15 11:41, PBKResearch a écrit :
Hello
I have run into a problem in moving some existing wor
Peter,
> On 10 Jan 2015, at 23:30, PBKResearch wrote:
>
>> Yes change the code of the Parser not to use old code.
> As I pointed out, the Parser is a large and complex package, and I am not
> the author, so this is easier said than done. It seems a bit odd to dismiss
> code which worked OK in Mo
: Any question about pharo is welcome
Subject: Re: [Pharo-users] Problem due to deprecation of class Url in Pharo
3 and Moose 5.0
> On 10 Jan 2015, at 16:45, stepharo wrote:
>
>
> Le 10/1/15 11:41, PBKResearch a écrit :
>> Hello
>>
>> I have run into a problem
> On 10 Jan 2015, at 16:45, stepharo wrote:
>
>
> Le 10/1/15 11:41, PBKResearch a écrit :
>> Hello
>>
>> I have run into a problem in moving some existing work from earlier versions
>> of Pharo/Moose. I have found a work around, but I wonder if there is a
>> tidier way of handling it.
>>
Le 10/1/15 11:41, PBKResearch a écrit :
Hello
I have run into a problem in moving some existing work from earlier
versions of Pharo/Moose. I have found a work around, but I wonder if
there is a tidier way of handling it.
I make frequent use of Todd Blanchard’s HTML parser and validator,
H
