[Catalyst] Catalyst website
Questions!
1) What is the preferred name for the Catalyst website? I thought that at one
point we were leaning toward sticking with catalyst.perl.org, but all the nav
links are for catalystframework.org. One way or another I think the site
should be clear on what it's named, and send a Moved Permanently redirect to
the preferred address when accessed using the nonpreferred address.
2) Will the new wiki go live[1] at its current toeat.com address or at
$answer{'Question 1'} . /wiki/?
3) Can we have a link to thebookerrata on the front page with the book link,
where newbies are likely to find it? Something to the tune of Having
trouble? Click here for important information on the Catalyst book. I will
happily submit patch to the website if this is not shot down.
4) Thoughts on improving the website in general? It's nice, but not very
filling, and I don't think it gets a lot of love. Again, I'd be happy to
help. Maybe this should wait for the new wiki though? I'm thinking that
either we would want to highlight some of the most important wiki articles
from the website, or else the wiki could end up being most of the website,
since it's powered by hierarchical fairy dust.
Thanks,
Andrew
[1] I think the new wiki is live in all but name anyway, and the old wiki is
getting stale, so I do hope that MojoMojo is production-quality soon!
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst website
* On Tue, Apr 29 2008, Andrew Rodland wrote:
2) Will the new wiki go live[1] at its current toeat.com address or at
$answer{'Question 1'} . /wiki/?
Definitely not toeat. But when is this going to happen?
3) Can we have a link to thebookerrata on the front page with the book link,
where newbies are likely to find it? Something to the tune of Having
trouble? Click here for important information on the Catalyst book. I will
happily submit patch to the website if this is not shot down.
+1
Regards,
Jonathan Rockway
--
print just = another = perl = hacker = if $,=$
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] So, what do we want in the -next- book?
On Mon, Apr 28, 2008 at 1:19 PM, Andrew Kornak [EMAIL PROTECTED] wrote: Personally, I would like any book on Catalyst, even if it was only a single chapter in a larger MVC treatment. I bought Jonathan's book and contrary to another poster's opinion found it quite useful. -Andrew This is more of my view as well. It's hard to sell a web framework book, because it's selling a book about a singular tool when many are needed to finish a project. In silly metaphor land, this would be a book on hammers to build a house. That's my view on a Catalyst book. Catalyst is just one tool out of many that deserves detailed mentioning, but if you _only_ used Catalyst you would have a very small and useless app. You need an ORM, view methods (TT, JSON, etc) and preferably a good front-end toolkit (YUI, Ext, Dojo, etc.) In my opinion, this is why book sales are stagnating in regards to _frameworks_. If we could all play nicely and write a book that doesn't have Catalyst in the title, but in the contents, everybody would win. Dare I say, an Enlightened Perl Development book? *prod prod* HEY MST AND MDK I AM LOOKING AT YOU GUYS. *cough* ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] So, what do we want in the -next- book?
Dare I say, an Enlightened Perl Development book? *prod prod* HEY MST AND MDK I AM LOOKING AT YOU GUYS. *cough* Actually a Developers Perl book sounds like a good idea. Perl for Enterprise: A look at Enlightened Perl Development That way you could cover quite a few camps at once, if it took a theme such as bringing an app into existence (as already mentioned here) including all aspects of dev. then it might even elicit some general interest to other language developers who are very confused as to the current state of Perl. Also. J SHIRLEY - you is on the board as well :P -- Mark Keating BA (Hons) | Writer, Photographer, Cat-Herder Managing Director| Shadowcat Systems Limited Board Member | Enlightened Perl Organisation http://www.shadowcat.co.uk | 'Sufficiently Advanced Technology' http://www.enlightenedperl.org | http://linkedin.com/in/markkeating http://www.projectmonkey.vox.com | MSN: mdk at shadowcatsystems.co.uk ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] So, what do we want in the -next- book?
On Tue, Apr 29, 2008 at 8:04 AM, Mark Keating [EMAIL PROTECTED] wrote: Dare I say, an Enlightened Perl Development book? *prod prod* HEY MST AND MDK I AM LOOKING AT YOU GUYS. *cough* Actually a Developers Perl book sounds like a good idea. Perl for Enterprise: A look at Enlightened Perl Development That way you could cover quite a few camps at once, if it took a theme such as bringing an app into existence (as already mentioned here) including all aspects of dev. then it might even elicit some general interest to other language developers who are very confused as to the current state of Perl. I think that is a great idea. There is nothing perl specific about building a good web application, aside from the specific tools. If we describe the tools in a manner that shows their strengths in the specific utilization areas then non-perl folk can benefit greatly as well. Show the strengths by describing the utilization and best practices, without championing OUR WAY IS THE BEST!! Also. J SHIRLEY - you is on the board as well :P Yes, but my available time to JFDI sucks. Evidenced by catwiki.toeat.com not being on catalystframework.org yet :) ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] So, what do we want in the -next- book?
* On Tue, Apr 29 2008, Mark Keating wrote: Dare I say, an Enlightened Perl Development book? Perl for Enterprise: A look at Enlightened Perl Development But first, the EPO needs to create a publishing company called ORLY. -- print just = another = perl = hacker = if $,=$ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] So, what do we want in the -next- book?
On Sun, Apr 27, 2008 at 03:01:47AM -0500, Jonathan Rockway wrote: [...] Anyway, I hate to break this to you... if you want to know every detail of how the code works, you have to read the code. Reading code is the most important skill a programmer can have, so I suggest biting the bullet, opening up your favorite code browser (ECB++), and perusing. Right, and I need to read the entire Linux and libc source code to be able to write a Unix application. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] So, what do we want in the -next- book?
* On Tue, Apr 29 2008, Peter Corlett wrote: On Sun, Apr 27, 2008 at 03:01:47AM -0500, Jonathan Rockway wrote: [...] Anyway, I hate to break this to you... if you want to know every detail of how the code works, you have to read the code. Reading code is the most important skill a programmer can have, so I suggest biting the bullet, opening up your favorite code browser (ECB++), and perusing. Right, and I need to read the entire Linux and libc source code to be able to write a Unix application. It will help, yes. Regards, Jonathan Rockway -- print just = another = perl = hacker = if $,=$ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] So, what do we want in the -next- book?
On Tue, Apr 29, 2008 at 11:34:57AM -0500, Jonathan Rockway wrote: * On Tue, Apr 29 2008, Peter Corlett wrote: [...] Right, and I need to read the entire Linux and libc source code to be able to write a Unix application. It will help, yes. It may well help, but it is not necessarily the best approach. The source code to a library is too low-level for a user of the library to really get a grip on how all the pieces fit together and are intended to be used. Telling people to grub through the source is generally an admission that the doucmentation sucks. Which it does. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] So, what do we want in the -next- book?
On Tue, Apr 29, 2008 at 9:51 AM, J. Shirley [EMAIL PROTECTED] wrote: Dare I say, an Enlightened Perl Development book? Being in the middle of 5 or 6 apps that all use the 'enlightened' stack of perl libraries I can personally say that I would _love_ to have this book to recommend to our developers or to others. I love DBIC, Catalyst, Moose and friends because they don't force me into a particular way of doing things. The problem with this approach is that, for the newb, there are so many choices to make. It's not always clear which is the best. I know I've made -- and continue to make -- bad choices that I later have to undo. A guide into this area of perl would likely be very helpful. -- Cory 'G' Watson http://www.onemogin.com ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] So, what do we want in the -next- book?
On Tue, 2008-04-29 at 12:06 -0500, Cory Watson wrote: On Tue, Apr 29, 2008 at 9:51 AM, J. Shirley [EMAIL PROTECTED] wrote: Dare I say, an Enlightened Perl Development book? Being in the middle of 5 or 6 apps that all use the 'enlightened' stack of perl libraries I can personally say that I would _love_ to have this book to recommend to our developers or to others. I love DBIC, Catalyst, Moose and friends because they don't force me into a particular way of doing things. The problem with this approach is that, for the newb, there are so many choices to make. It's not always clear which is the best. I know I've made -- and continue to make -- bad choices that I later have to undo. A guide into this area of perl would likely be very helpful. ++ I've been using Perl for many years with the last two being professional and I'm just now becoming somewhat aware of what the enlightened libraries are. I stumble in this area a lot. A book into this area as a whole would be very nice. v/r -matt pitts ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] So, what do we want in the -next- book?
On 29. april. 2008, at 19.02, Peter Corlett wrote: On Tue, Apr 29, 2008 at 11:34:57AM -0500, Jonathan Rockway wrote: * On Tue, Apr 29 2008, Peter Corlett wrote: [...] Right, and I need to read the entire Linux and libc source code to be able to write a Unix application. It will help, yes. It may well help, but it is not necessarily the best approach. The source code to a library is too low-level for a user of the library to really get a grip on how all the pieces fit together and are intended to be used. Telling people to grub through the source is generally an admission that the doucmentation sucks. Which it does. We have a bunch of library documentation, manuals and tutorials for Catalyst tho (which we are very happy to accept new contributors to :) Jonathan suggested reading the source if you wanted to learn Catalyst internals, not as a requirement For application development... I'm not sure why that seems so unreasonable? With regards, Marcus Ramberg. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Tutorial update (was: -next- book)
On 30 Apr 2008, at 07:43, Aaron Brown wrote: Marcus Ramberg wrote: We have a bunch of library documentation, manuals and tutorials for Catalyst tho (which we are very happy to accept new contributors to :) Speaking of which... I'm a new Catalyst user, or at least I've been trying, so I naturally worked through the online tutorial to wrap my head around the framework and get some practice with plugins like Authentication and Authorization. I've found that the Authorization chapter of the tutorial is... well, it's broken. It looks to me as if it was written against an older version of Catalyst (and the Authz plugin) which may have employed a completely different config specification, but it's hard for me to say since I'm new to the system. What I *do* know is that, replicated verbatim, the project won't run. Anyway, I managed to make my project work, and I'd be happy to submit my updates to someone for inclusion in the tutorial. How should I go about it, and who should I talk to? Patches (diff -u) to the catalyst-dev mailing list please. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Viewing username in Apache access_log (via FastCGI)
On Tue, Apr 29, 2008 at 2:26 PM, Kutbuddin Doctor [EMAIL PROTECTED] wrote: The Catalyst::Plugin::Authentication::Store::HTTP modules you pointed to seem to be for using Catalyst as a controller to access remote (not my own) web sites that use HTTP authentication (basic, Digest, NTLM). In my case I am using Authenticaiton::Store::DBIC so, the question is: How do I tell Apache who my authenticated user is. I only wish to have this to be a part of the normal Apache access_log (my own). Thanks for that pointer, but I am still looking for a solution. You're confusing the difference between Credentials and Stores. Also, you seem to be using the outdated Catalyst::Plugin::Authentication (but I don't know if Credential::HTTP has been ported, jayk?) -- this may give you some problems if you do any straight cpan install Catalyst::Plugin::Authentication upgrades elsewhere (but hopefully not). A store is where the users exist, and where the password is stored (in most cases, but not always). The credential is how they are authenticated (password, openID). In the case of HTTP Authentication, which is what you are after, you want something like: http://search.cpan.org/~jrobinson/Catalyst-Plugin-Authentication-Credential-HTTP-0.09/lib/Catalyst/Plugin/Authentication/Credential/HTTP.pm That will give you the typical browser popup window to get the user to enter their username and password, and that is the only way that you can have the logging format you are after. You could just have a separate application log, though (Catalyst::Log::Log4perl is my favorite) rather than reworking your credential system. -J ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] C::C::FormBuilder - self-formbuilder-submitted not set
Hello, Please excuse me if this has already been answered somewhere. I searched the archives and Googled quite a bit before turning to the list. I'm building a form with FormBuilder with my controller containing all the firm field definitions instead of using a .fb file. My problem is when I submit the form I see from debug output that $self-formbuilder-submitted is set to 0 and validate is set to 1. What will cause submitted not to be set after the form is submitted and passes validation? I also noticed that validate returns 1 before the form is submitted for the first time too. Is that by design? Thanks, Ryan ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
