A few of us discussed this at YAPC, and a few of the talking points
included:
- Who is really our target audience? Do we want to compete with
Catalyst and Rails publicly? Or are we content with developing tools
to make our own lives easier. Which feeds into....
- What's in a name? If we're developing for ourselves, who gives a
damned what it's named? It could be called
Big::Stinking::Pile::Of::Poo and as long as it works, why change?
That being said, if we are going to outwardly compete with Rails/
Catalyst/$framework, I can see some sort of name change being
beneficial. Like Michael Peter's wrote, a lot of people have a sour
taste in their mouth when it comes to CGI programming. And even know
we know the framework is useful for much more than that, the name
will make it hard for some people to get past.
So if we change the name, we have some options. Do we pick a cool
name for the module/suite of modules? Do we come up with a cool name
for the CAF project (given magog and rdice's blessing)? Do we rename
C::A to Web::Application, rename CAF, and say CAF is based on
Web::Application? So many choices!
Anyway, that's all I got.
Jason
On Jul 6, 2006, at 8:51 AM, Robert Hicks wrote:
Mark Stosberg wrote:
I've started on porting CGI::Application to Perl6.
The current state is that I've made a number of code adjustments,
but the module still doesn't compile. I haven't started
converting any of the tests.
I don't think the replacement for Class::ISA is even implemented
yet, so
the line that includes "$app_class.meta.class_precedence_list"....
will current fail.
I'm sharing the code here in case anyone else wants to hack on it.
It's a darcs archive:
darcs get http://mark.stosberg.com/darcs_hive/CGI-Application-p6/
# hack
darcs record
darcs send
I consider this a "blue sky" project where we should feel free to
make API improvements in non-backwards compatible ways.
For example, I think it's worth considering moving load_tmpl() to
a plugin, and considering whether to keep both header_add() and
header_props(). ( header_props() could accidentally clobber
headers set a plugin... header_add() is almost always a better
choice. ).
Also, some might like a complete decoupling with CGI.pm.
Even the name could be changed. :) ( It seems the DateTime module
will be just "Date" in Perl6 ).
For that matter, there's no reason that I need to be an official
maintainer of this new project. Anyone else is welcome to publish
another repository of a CGI::App that is equally as authoritative
as my work.
For the moment, I'm mostly interested in this project as an excuse
to learn more about Perl6.
Mark
There was a thread about a possible rebranding of CA a while ago.
Doing that for Perl6 would be the best opportunity.
Just a thought...
:Robert
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@lists.erlbaum.net/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@lists.erlbaum.net/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
