Mark.
Thanks for your feedback.
I already did the change you suggested to change "routes_table" to
"routes". But I must to admit that is not clear to me what you mean
with this one.
- Consider having "routes_table()" automatically add every run mode
dispatched to
the "run_modes" hash, if a subroutine with that name exists in the current
scope. (I suppose you can use the "can()" method to test for that? ).
Maybe because I'm not pro-efficient with perl enough, or maybe I'm
missing something?
Also,. I liked this:
Perhaps there should be an option to set a path for which all the routes are
relative to. For example:
$c->routes_root('/app/volunteer/profile');
I definitely going to include that change.
But, about the catalyst style, I didn't liked the approach, and, also,
see something (I think almost) exactly like that in
CAP::Actiondispatch
(http://search.cpan.org/~jaywhy/CGI-Application-Plugin-ActionDispatch-0.96/lib/CGI/Application/Plugin/ActionDispatch.pm)
and I really didn't liked it (or just didn't worked for me).
Thanks.
Julián Porta.
##### CGI::Application community mailing list ################
## ##
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp ##
## ##
## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ##
## Wiki: http://cgiapp.erlbaum.net/ ##
## ##
################################################################
