Re: [Catalyst] Literal elements in uri_for generated paths

2010-06-09 Thread J. Shirley
2010/6/8 Octavian Rasnita : > Hi, > > I have tried to use uri_for() in some parameters of a Java applet, but that > URI should contain chars like { and } which then should be replaced by the > appled with something else: > > > > If I do this , { and } are URI encoded and I don't want that. > > Is

Re: [Catalyst] Literal elements in uri_for generated paths

2010-06-09 Thread Mark A. Stratman
If you're passing a string for the action anyway, why not just append the additional @args to it manually? String paths aren't url encoded, but the additional args will be. That is: c.uri_for('/static/data/eof/{symbol}.txt').path On Jun 8, 2010, at 3:16 AM, Octavian Rasnita wrote: > Hi, > >

[Catalyst] Literal elements in uri_for generated paths

2010-06-08 Thread Octavian Rasnita
Hi, I have tried to use uri_for() in some parameters of a Java applet, but that URI should contain chars like { and } which then should be replaced by the appled with something else: If I do this , { and } are URI encoded and I don't want that. Is it possible to create URIs that contain lite