in reply to CGI::Prototype leverages objects for web app control

Thanks for "getting it" about why I did CGIP.

And yes, had I started today, I would have done it all with Moose... a lot of things that I had to lean pretty heavily on Class::Prototyped for, almost to the point of breaking it, would have been simpler in Moose. In fact, I remember asking for prototype-style inheritance in Moose, to be told "it's possible, but we haven't done it yet". But that was two years ago.

If I wasn't so busy pushing Seaside for my newest web apps, I'd still be building on CGIP.

-- Randal L. Schwartz, Perl hacker

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

  • Comment on Re: CGI::Prototype leverages objects for web app control

Replies are listed 'Best First'.
Re^2: CGI::Prototype leverages objects for web app control
by Anonymous Monk on Aug 08, 2009 at 09:47 UTC
    Wow, Seaside website is so messed up, they broke scrolling with javascript
[reply]
Re^2: CGI::Prototype leverages objects for web app control
by Anonymous Monk on Oct 19, 2009 at 14:03 UTC
    When can you release new version?
[reply]
      I have forked CGI::Prototype and wrote a Moose version that I wanted merged back into the distro, but merlyn refuses to have a standard Moose-based CGI version of CGIP in the distro - he said it had to use prototype OO.

      As such, I have reserved the namespace CGI::Class but not released anything to CPAN.

[reply]
        Please don't misquote me.

        I never said that a Moose-based CGIP was out of the question.

        I said a non-prototype-Moose base class would not be acceptable.

        All you have to do is use a prototype-Moose base class, which either exists already, or is just a small matter of programming.

        Or, you can go off and do what you want. Just don't call it CGI::Prototype until it's prototype-based.

        -- Randal L. Schwartz, Perl hacker

        The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

[reply]
        I can see merlyns point to some degree, however I've not used Moose (and have no immediate plans so to do) but surely, implementing CGI::Prototype as you suggest would introduce previously unneeded dependencies, on the part of existing code, on Moose i.e. removing any backward compatibility ... or have I, not for the first time, missed something otherwise obvious ?

        Surely you should be reserving/creating a new namespace e.g. CGI::Prototype::Moose, to make the provenance abundantly clear to all and sundry - in a manner that the namespace CGI::Class doesn't.

        A user level that continues to overstate my experience :-))
[reply]

In Section Meditations