gmane.comp.lang.perl.modules.cgi-prototype.user

Re: Prototyping CGI versus CGI::Prototype

Randal L. Schwartz — 2009-08-30T23:16:03

Terrence> I dont want to fork and start a separate distro, just add
Terrence> CGI::Prototype::Moose to the CGIP distro.

And I'm saying that's the wrong name for that, if it's not about replacing all
of what CGIP already does, including prototype inheritance.  Feel free
to release it as CGI::Moose or something.

Re: Prototyping CGI versus CGI::Prototype

Terrence Brannon — 2009-08-30T23:02:08


Randal L. Schwartz wrote:
Right. I'm not suggesting an heir apparent. I'm suggesting an additional 
module in the distribution, along with associated test suite.
This module would extend on the other concept of "CGI Prototype" - 
prototyping the CGI process. Not using CGI with prototyped objects.
Also, people tend to look down on modules whose release date is more 
than 6 months old. It starts to look unmaintained.

I dont want to fork and start a separate distro, just add 
CGI::Prototype::Moose to the CGIP distro.
right and a toy example exemplifying the need for non classical 
class-instance structures in the standard docs or a magazine article would
help greatly. I did talk to Jason Purdy above his negative CPAN ratings 
review of CGIP <http://cpanratings.perl.org/dist/CGI-Prototype>.

He wrote his 'review' after skimming the docs. Now, I dont think that 
what he did was fair or thoroughly researched, but I think a section in 
the docs like "Why Another Framework" or "How is CGIP Different" would 
go a long way towards stamping out superficial inspection of the module.


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

Re: Prototyping CGI versus CGI::Prototype

Randal L. Schwartz — 2009-08-30T22:46:40

The heir apparent to the CGI::Prototype namespace should support
Class::Prototype-styled objects.  Under the licensing terms of CGIP, you're
free to derive whatever you want and call it whatever you want, but please
reserve CGI::Prototype (or names close to it) for something that supports
prototype-inheritance objects.  I have customers that are making use of the
Class::Prototyped features that are not classical class-instance structures,
so any "replacement" of CGIP with something new must be carefully considered.

Prototyping CGI versus CGI::Prototype

Terrence Brannon — 2009-08-30T22:41:15

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july_______________________________________________
cgi-prototype-users mailing list
cgi-prototype-users< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cgi-prototype-users

Re: Moose implementation of CGI::Prototype

Randal L. Schwartz — 2009-08-23T19:18:48

Terrence> Randal wants to maintain prototype-based OOP for a Moose-based version 
Terrence> of CGI::Prototype. I'm wondering if such a Moose class could be as 
Terrence> simple as:


Terrence> package CGI::Prototype::Moose;

Terrence> use Moose;
Terrence> extends 'Class::Prototyped';

Not really.  The prototype stuff of Moose is where you want to start, and it
has a different interface.  If you just pulled in Class::Prototyped, you'd
have a lot of potential conflicts, especially around anonymous classes.

Moose implementation of CGI::Prototype

Terrence Brannon — 2009-08-23T19:03:28

Randal wants to maintain prototype-based OOP for a Moose-based version 
of CGI::Prototype. I'm wondering if such a Moose class could be as 
simple as:


package CGI::Prototype::Moose;

use Moose;
extends 'Class::Prototyped';

...

1;

Links:
------
* There is a sample prototype OO moose in this test example:
http://github.com/nothingmuch/moose/blob/0bb2cc8a6a2e4b967b5d8efbcf1ab27f5d95e990/t/200_examples/006_example_Protomoose.t

but I dont fancy breaking with the Class::Prototyped API.

* My current fork of CGI::Prototype which uses Moose:
http://github.com/metaperl/perl-module-cgi-prototype/blob/f3c71299cd98de7b4c4d2b291d95623a761db548/lib/CGI/Prototype/Moose.pm


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

Re: Moose implementation of CGI::Prototype

Randal L. Schwartz — 2009-08-23T19:18:48

Terrence> Randal wants to maintain prototype-based OOP for a Moose-based version 
Terrence> of CGI::Prototype. I'm wondering if such a Moose class could be as 
Terrence> simple as:


Terrence> package CGI::Prototype::Moose;

Terrence> use Moose;
Terrence> extends 'Class::Prototyped';

Not really.  The prototype stuff of Moose is where you want to start, and it
has a different interface.  If you just pulled in Class::Prototyped, you'd
have a lot of potential conflicts, especially around anonymous classes.

Moose implementation of CGI::Prototype

Terrence Brannon — 2009-08-23T19:03:28

Randal wants to maintain prototype-based OOP for a Moose-based version 
of CGI::Prototype. I'm wondering if such a Moose class could be as 
simple as:


package CGI::Prototype::Moose;

use Moose;
extends 'Class::Prototyped';

...

1;

Links:
------
* There is a sample prototype OO moose in this test example:
http://github.com/nothingmuch/moose/blob/0bb2cc8a6a2e4b967b5d8efbcf1ab27f5d95e990/t/200_examples/006_example_Protomoose.t

but I dont fancy breaking with the Class::Prototyped API.

* My current fork of CGI::Prototype which uses Moose:
http://github.com/metaperl/perl-module-cgi-prototype/blob/f3c71299cd98de7b4c4d2b291d95623a761db548/lib/CGI/Prototype/Moose.pm


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

Re: the future of CGI::Prototype

Randal L. Schwartz — 2009-08-07T15:33:15

Terrence> I'm a github fan and would like to put up a repo for CGIP ASAP.

You can just fork mine.  CGIP is already on github.

http://github.com/RandalSchwartz/perl-module-cgi-prototype/tree/master

the future of CGI::Prototype

Terrence Brannon — 2009-08-07T15:13:09

Merlyn is pretty much following other paths in CGI development
<http://perlmonks.org/?node_id=786745>

I personally am interested in a Moose upgrade of CGI::Prototype.

There are a lot of articles out on CGI::Prototype so I think we should
simply augment the current distro.

I'm a github fan and would like to put up a repo for CGIP ASAP.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july