Re: [Catalyst] Request for comments: model class for REST queries

On Thu, Dec 07, 2006 at 03:14:19PM -0500, Christopher Heschong wrote: > >My first thought is that you are going to need to support the full > >range of HTTP Methods. At the very least, you will need: GET, POST, > >PUT and DELETE. You probably want to support OPTIONS and HEAD as > >well. > > >

[Catalyst] Re: usign Catalyst::Plugin::Prototype

* Steve Sabljak <[EMAIL PROTECTED]> [2006-12-08 04:25]: > What is the recommended Ajax framework for Catalyst these days > anyway? Is there a DeFacto standard? Take a look at jQuery. I just made two new converts two or three threads next to this one. :-) Regards, -- Aristotle Pagaltzis //

[Catalyst] Re: Request for comments: model class for REST queries

* Adam Jacob <[EMAIL PROTECTED]> [2006-12-07 18:40]: > On Wed, Dec 06, 2006 at 10:08:08AM -0500, Christopher Heschong wrote: > > # Meanwhile in a controller nearby > > $c->stash->{answers} = $c->model('YahooAnswers')->get( 'questionSearch', > > query => $c->req->param('query') > > ); >

Re: [Catalyst] usign Catalyst::Plugin::Prototype

What is the recommended Ajax framework for Catalyst these days anyway? Is there a DeFacto standard? On 12/8/06, Luis Azevedo <[EMAIL PROTECTED]> wrote: Renan, For what I know, there is not so much of a really great Prototype Tutorial. But checkout this one, it might help you (or not): http://ww

Re: [Catalyst] usign Catalyst::Plugin::Prototype

Renan, For what I know, there is not so much of a really great Prototype Tutorial. But checkout this one, it might help you (or not): http://www.petefreitag.com/item/515.cfm Since you might want to easily understand Prototype you must start with this great book: http://www.amazon.com/Pragm

[Catalyst] usign Catalyst::Plugin::Prototype

Hi, There is some examples or tutorials explaining how to use the Prototype? Thanks -- Renan ___ List: Catalyst@lists.rawmode.org Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lis

RE: [Catalyst] Mason configuration in YAML

> -Original Message- > From: Kevin Old [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 07, 2006 8:37 PM > To: The elegant MVC web framework > Subject: Re: [Catalyst] Mason configuration in YAML > > Hi Mark, > > I'm pretty sure you need to do it like this: > > In your YAML file spec

Re: [Catalyst] Request for comments: model class for REST queries

Adam, thanks for the feedback and suggestions! See below for more comments: On Dec 7, 2006, at 12:28 PM, Adam Jacob wrote: On Wed, Dec 06, 2006 at 10:08:08AM -0500, Christopher Heschong wrote: Hi, I've created a simple library to make calls to REST services, along with an associated Cataly

Re: [Catalyst] Mason configuration in YAML

Hi Mark, I'm pretty sure you need to do it like this: In your YAML file specify comp_root and data_dir: comp_root: __path_to(mason/root)__ data_dir: __path_to(mason/data)__ then in Mason.pm you can use it like this: package MyApp::View::Mason; use base 'Catalyst::View::Mason'; __PACKAGE__->c

Re: [Catalyst] Re: AJAX under application/xhtml+xml

On Thursday, Dec 7, 2006, at 07:53 US/Pacific, Daniel McBrearty wrote: i just looked at the tutorial, a lot more clear and to the point than other libs I have looked at. Think I'm gonna go with it. I had a little proof of concept Ajax demo up in about 10 minutes; just as long as it took to skim

Re: [Catalyst] Request for comments: model class for REST queries

On Wed, Dec 06, 2006 at 10:08:08AM -0500, Christopher Heschong wrote: > Hi, I've created a simple library to make calls to REST services, along > with an associated Catalyst model, and wanted to get some feedback. The > class itself is called CRUST and basically it's just some very simple glue > f

[Catalyst] Authorization::ACL - basic question

Hi, sorry if I ask a question that has been answered. How could I block out the whole set of actions instead of setting for each. For example: instead of doing authorization for each of action in books,pm controller such as: __PACKAGE__->deny_access_unless( "/books/delete",

[Catalyst] Mason configuration in YAML

Hi there, I am struggling with the configuration of the Mason view in YAML. I have this: View::Mason: comp_root: __path_to(mason/root)__ data_dir: __path_to(mason/data)__ But as it seems, it is never taken into account. I have also tried forcing an array ref, whithout any succes: View::Mason:

Re: [Catalyst] Re: AJAX under application/xhtml+xml

i just looked at the tutorial, a lot more clear and to the point than other libs I have looked at. Think I'm gonna go with it. On 12/7/06, John Napiorkowski <[EMAIL PROTECTED]> wrote: --- Ashley Pond V <[EMAIL PROTECTED]> wrote: > On Wednesday, Dec 6, 2006, at 21:06 US/Pacific, A. > Pagaltzis

Re: [Catalyst] Re: AJAX under application/xhtml+xml

--- Ashley Pond V <[EMAIL PROTECTED]> wrote: > On Wednesday, Dec 6, 2006, at 21:06 US/Pacific, A. > Pagaltzis wrote: > > * apv <[EMAIL PROTECTED]> [2006-12-07 01:35]: > >> Does anyone have sample code of anything AJAXy > (don't care > >> about the library or if it's hand rolled) that > runs under

Re: [Catalyst] question from tutorial - does creating HTML in a controller using HTML::Widget violate MVC?

On Thu, Dec 07, 2006 at 10:11:42AM +0100, Zbigniew Lukasiak wrote: > There was a long and very constructive discussion on the HTML::Widget > email list about how to make it more MVC compliant. We had some > conclusions - I don't know when and if the maintainer is going to > implement them - but I

Re: [Catalyst] question from tutorial - does creating HTML in a controller using HTML::Widget violate MVC?

There was a long and very constructive discussion on the HTML::Widget email list about how to make it more MVC compliant. We had some conclusions - I don't know when and if the maintainer is going to implement them - but I would not declare HTML::Widget dead yet. At least it has much saner API fo