Re: [Catalyst] Using Log4perl -- setting caller()

2007-07-04 Thread Bill Moseley
On Tue, Jul 03, 2007 at 03:14:52PM -0700, Quinn Weaver wrote: Now, the problem with that is $c-log-warn uses caller() so errors are reported from that sub, not from where warn was called. So, need a way to use (IIRC) caller(1) instead in that case. Talked to Bill off-list, and this

RE: [Catalyst] Automatic structure creation from form data

2007-07-04 Thread Dami Laurent (PJ)
I was wondering if it possible to construct an HTML form such that the back end automatically creates a hash (or an array) based on the naming scheme. For example... form input name=items[0][name] value=... input name=items[0][description] value=... input

Re: [Catalyst] IDE for use with Catalyst

2007-07-04 Thread Oleg Pronin
:) 2007/7/1, Matt S Trout [EMAIL PROTECTED]: On Sun, Jul 01, 2007 at 06:50:36PM +0400, Oleg Pronin wrote: OptiPerl does. The coolest IDE for perl i ever seen http://xarka.com Wake me up when they release a version for an OS worth doing dev work on. -- Matt S Trout Need help

Re: [Catalyst] Uniform treatment of all parameters (including file uploads)

2007-07-04 Thread Zbigniew Lukasiak
On 7/3/07, Matt S Trout [EMAIL PROTECTED] wrote: No, because this would break the ability to pass the request object to something expecting the CGI.pm API, and break compat for existing app code. I think you meant Apache::Request because the current implementation is not compatible with

Re: [Catalyst] Uniform treatment of all parameters (including file uploads)

2007-07-04 Thread Matt S Trout
On Wed, Jul 04, 2007 at 11:29:12AM +, Zbigniew Lukasiak wrote: On 7/3/07, Matt S Trout [EMAIL PROTECTED] wrote: No, because this would break the ability to pass the request object to something expecting the CGI.pm API, and break compat for existing app code. I think you meant

Re: [Catalyst] Using Log4perl -- setting caller()

2007-07-04 Thread Quinn Weaver
On Tue, Jul 03, 2007 at 11:23:43PM -0700, Bill Moseley wrote: On Tue, Jul 03, 2007 at 03:14:52PM -0700, Quinn Weaver wrote: Now, the problem with that is $c-log-warn uses caller() so errors are reported from that sub, not from where warn was called. So, need a way to use (IIRC)

Re: [Catalyst] accessing ResultSet function from a related object

2007-07-04 Thread Ash Berlin
John Goulah wrote: I am having some trouble in both controller and template code accessing resultset functions off of chained/related objects (because from what I'm seeing they are not ResultSets but of the type MyApp::Model::MyAppDB::Tablename). For example I can create a ResultSet object

Re: [Catalyst] Anyone using ProxyPass?

2007-07-04 Thread Richard Jones
Richard Jones wrote: However, the URLs constructed in the templates from Catalyst.uri_for pick up the port number, thus defeating the idea of ProxyPass. In one of Replying to my own post, but for the benefit of closure, and for anyone else who might stumble over this one in future, I've

Re: [Catalyst] accessing ResultSet function from a related object

2007-07-04 Thread John Goulah
On 7/4/07, Ash Berlin [EMAIL PROTECTED] wrote: John Goulah wrote: I am having some trouble in both controller and template code accessing resultset functions off of chained/related objects (because from what I'm seeing they are not ResultSets but of the type

Re: [Catalyst] Re: How to access current MyApp instance ?

2007-07-04 Thread Jonathan Rockway
On Sunday 01 July 2007 02:27:17 pm A. Pagaltzis wrote: Of course, we’ve known since the ’70s or so how to make better programming languages, but ABW considers templating languages to be totally different from programming languages, so you get to be transported back to the ’60s. I agree that

Re: [Catalyst] accessing ResultSet function from a related object

2007-07-04 Thread Nathaniel Nuss
On Wed, Jul 04, 2007 at 04:09:41PM -0400, John Goulah wrote: I am having some trouble in both controller and template code accessing resultset functions off of chained/related objects (because from what I'm seeing they are not ResultSets but of the type MyApp::Model::MyAppDB::Tablename). Have

Re: [Catalyst] html::prototype syntax in new Cat version

2007-07-04 Thread Jonathan Rockway
On Thursday 28 June 2007 07:33:57 am vb wrote: HTML::Prototype is the Matt's Script Archive of javascript. possible, but don't confuse with prototype.js. Same difference. The Prototype + Scriptaculous javascript framework is junk. It doesn't work very well, the syntax is terrible, it will

Re: [Catalyst] html::prototype syntax in new Cat version

2007-07-04 Thread vb
There is absolutely no reason to use Prototype. The Prototype + Scriptaculous javascript framework is junk. There is absolutely no reason to use... Prototype + Scriptaculous It doesn't work very well, the syntax is terrible, it will break other javascript on the page just by being