Wade wrote:
I do not get what you are pushing for -- from what I have seen normal
catalyst code acts like normal perl code, except when the type of engine
you are using requires its own stdio redirects -- in which case it must
handle these in/outputs differently.
If you want to have full
On Wed, Mar 12, 2008 at 06:35:38AM -0700, Bill Moseley wrote:
If I make an XMLRPC request to an invalid XMLRPC endpoint $c-action
is not set. (For a normal 404 request I end up with a default
action).
I have plugins and other code that calls methods on $c-action so those
don't work so well
I've been playing with jrockway's Jemplate example and when I create the
view using script/myapp_create.pl view Jemplate the app will no longer
render the TT view. It seems to overwrite template rendering and will
print a few lines of javascript to the screen, no matter what screen I
try to
On Fri, Mar 21, 2008 at 2:29 PM, Stephen Sykes [EMAIL PROTECTED] wrote:
I've been playing with jrockway's Jemplate example and when I create the
view using script/myapp_create.pl view Jemplate the app will no longer
render the TT view. It seems to overwrite template rendering and will
print
I think you have to specify the view in some cases. I know I had to do
that for JSON views like this.
# At the end of the controller method
$c-stash-{current_view} = 'JSON';
Maybe jtemplate becomes the default. Are you specifying a TT template by
the way?
Thanks,
J. Shirley wrote:
On Fri, Mar 21, 2008 at 2:29 PM, Stephen Sykes [EMAIL PROTECTED] wrote:
I've been playing with jrockway's Jemplate example and when I create the
view using script/myapp_create.pl view Jemplate the app will no longer
render the TT view. It seems to overwrite template
On Mar 17 2008, Aristotle Pagaltzis wrote:
Yes, he told me the same on IRC and I was actually planning to go
that route. Except that the set of `clinicXY`, `clinicYZ` etc
strings come from the database and can change at runtime. So I’d
need to create and destroy controller classes on the fly…
* On Thu, Mar 20 2008, Peter Karman wrote:
Perhaps the best approach would be to warn and not decode when
flagged data is seen, that way the data should never be deformed and
the author can see that something else is decoding too early and
they can fix it.
I like this proposal. Doesn't break
