WAUrl >> #jsonOn:?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

WAUrl >> #jsonOn:?

Philippe Marschall
Hi

WAUrl understands #javascriptOn: but not  #jsonOn:. I have a case
where I would need #jsonOn: with exactly the same semantics as
#javascriptOn:. Would it make sense to add #jsonOn: to WAUrl or is
that not such a good idea?

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Reply | Threaded
Open this post in threaded view
|

Re: WAUrl >> #jsonOn:?

Lukas Renggli
Yeah, it is probably fine to JSON-serialize an URL as a string.

Lukas

On 24 September 2011 11:18, Philippe Marschall
<[hidden email]> wrote:

> Hi
>
> WAUrl understands #javascriptOn: but not  #jsonOn:. I have a case
> where I would need #jsonOn: with exactly the same semantics as
> #javascriptOn:. Would it make sense to add #jsonOn: to WAUrl or is
> that not such a good idea?
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>



--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev