Re: [Catalyst] New Catalyst Book?
On 06/02/2009, at 1:20 PM, Ashley wrote: On Feb 5, 2009, at 3:28 PM, Kieren Diment wrote: On 06/02/2009, at 9:14 AM, Kevin Monceaux wrote: On Thu, 5 Feb 2009, Jason Gottshall wrote: Just out of curiosity, who is authoring it? It looks like the book is already listed on apress.com: http://www.apress.com/book/view/1430223650 Oh shit, that means we've actually got to finish it :o Sidebar: not to steal anyone's thunder but it's on point so... I'm back working on an online manual which I started a year ago. It's a project walk-through from start to finish. Not sure when it'll start getting posted -- it'll be a chapter every couple days for a month or two. I've got a lot done lately so I'm optimistic it'll start going up pretty soon. As it'll be a living doc, I'll roll critiques, corrections, or good comments into it. That's great! We're doing nothing like a project work through, just trying to get developers up to speed on catalyst, and associated things as quickly as possible. Yeah there's best practices, deployment details, details about the dispatcher and lots of other things, and hopefully a substantial perl cookbook like section at the end. ___ 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] New Catalyst Book?
On Feb 5, 2009, at 3:28 PM, Kieren Diment wrote: On 06/02/2009, at 9:14 AM, Kevin Monceaux wrote: On Thu, 5 Feb 2009, Jason Gottshall wrote: Just out of curiosity, who is authoring it? It looks like the book is already listed on apress.com: http://www.apress.com/book/view/1430223650 Oh shit, that means we've actually got to finish it :o Sidebar: not to steal anyone's thunder but it's on point so... I'm back working on an online manual which I started a year ago. It's a project walk-through from start to finish. Not sure when it'll start getting posted -- it'll be a chapter every couple days for a month or two. I've got a lot done lately so I'm optimistic it'll start going up pretty soon. As it'll be a living doc, I'll roll critiques, corrections, or good comments into it. -Ashley ___ 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] New Catalyst Book?
You can at least be assured that I'll buy the book... Bob Kieren Diment wrote: On 06/02/2009, at 9:14 AM, Kevin Monceaux wrote: On Thu, 5 Feb 2009, Jason Gottshall wrote: Just out of curiosity, who is authoring it? It looks like the book is already listed on apress.com: http://www.apress.com/book/view/1430223650 Oh shit, that means we've actually got to finish it :o ___ 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/ ___ 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] New Catalyst Book?
On 06/02/2009, at 9:14 AM, Kevin Monceaux wrote: On Thu, 5 Feb 2009, Jason Gottshall wrote: Just out of curiosity, who is authoring it? It looks like the book is already listed on apress.com: http://www.apress.com/book/view/1430223650 Oh shit, that means we've actually got to finish it :o ___ 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] New Catalyst Book?
kd and mst are authoring it, me thinks. On Thu, Feb 5, 2009 at 3:14 PM, Kevin Monceaux wrote: > > On Thu, 5 Feb 2009, Jason Gottshall wrote: > > Just out of curiosity, who is authoring it? >> > > It looks like the book is already listed on apress.com: > > http://www.apress.com/book/view/1430223650 > > > > Kevin > http://www.RawFedDogs.net > http://www.WacoAgilityGroup.org > Bruceville, TX > > Si hoc legere scis nimium eruditionis habes. > Longum iter est per praecepta, breve et efficax per exempla!!! > > > > ___ > 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/ > -- Devin Austin http://www.dreamhost.com/r.cgi?326568/hosting.html - Host with DreamHost! ___ 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] New Catalyst Book?
On Thu, 5 Feb 2009, Jason Gottshall wrote: Just out of curiosity, who is authoring it? It looks like the book is already listed on apress.com: http://www.apress.com/book/view/1430223650 Kevin http://www.RawFedDogs.net http://www.WacoAgilityGroup.org Bruceville, TX Si hoc legere scis nimium eruditionis habes. Longum iter est per praecepta, breve et efficax per exempla!!! ___ 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] New Catalyst Book?
Kieren Diment wrote: The next book will be published by Apress and we're producing the first draft at the moment. It should be out in time for OSCON in june. Just out of curiosity, who is authoring it? -- Jason Gottshall jgottsh...@capwiz.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] Catalyst::View::Email tests failing
J. Shirley wrote on 2009-02-05: > On Thu, Feb 5, 2009 at 11:10 AM, Robert L Cochran > wrote: >> Dangerous? Well I don't think this module runs around with a Uzi >> spraying everyone. >> >> I don't think it is a good practice to force an install on errors. You >> should always get to the bottom of why the errors are happening to >> start with. Once you do and have applied a fix, it should install >> cleanly, and you will be a better programmer for having investigated >> the cause. >> >> Bob >> >> > > Hi Bob, > > As a matter of etiquette, please don't top-post. Put your reply below > in the thread to keep things consistent. > > In this case, the test failures are actually a problem that was resolved > in Email::MIME::Creator and while it certainly doesn't carry firearms, > it can break your application under certain circumstances. > > I think, relatively speaking, that counts as dangerous. > > However, I'm just totally going crazy and senile. I misread the test > failure, as I already have a fixed version that never made it to CPAN > though I would have sworn under oath it actually did. > > Catalyst::View::Email 0.12 just shipped to CPAN, that should resolve the > error and had the fixed version of Email::MIME::Creator listed as a > dependency. > > Thanks, > -J Thanks for the quick fix, J. My Email::MIME::Creator is up to date at v1.455. I grabbed ftp://ftp.funet.fi/pub/languages/perl/CPAN/modules/by-module/Catalyst/Catalyst-View-Email-0.12.tar.gz and the tests worked. Thanks Byron ___ 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] New Catalyst Book?
The next book will be published by Apress and we're producing the first draft at the moment. It should be out in time for OSCON in june. Kieren On 06/02/2009, at 6:03 AM, Robert L Cochran wrote: Is a new Catalyst book being written? I have the original Rockway book, my interest is in a new work-in-progress book. If so, is there an early-access electronic version available? Thanks Bob Cochran Greenbelt, Maryland, USA ___ 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/ ___ 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::View::Email tests failing
On Thu, Feb 5, 2009 at 11:10 AM, Robert L Cochran wrote: > Dangerous? Well I don't think this module runs around with a Uzi > spraying everyone. > > I don't think it is a good practice to force an install on errors. You > should always get to the bottom of why the errors are happening to start > with. Once you do and have applied a fix, it should install cleanly, and > you will be a better programmer for having investigated the cause. > > Bob > > Hi Bob, As a matter of etiquette, please don't top-post. Put your reply below in the thread to keep things consistent. In this case, the test failures are actually a problem that was resolved in Email::MIME::Creator and while it certainly doesn't carry firearms, it can break your application under certain circumstances. I think, relatively speaking, that counts as dangerous. However, I'm just totally going crazy and senile. I misread the test failure, as I already have a fixed version that never made it to CPAN though I would have sworn under oath it actually did. Catalyst::View::Email 0.12 just shipped to CPAN, that should resolve the error and had the fixed version of Email::MIME::Creator listed as a dependency. Thanks, -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/
Re: [Catalyst] Catalyst::View::Email tests failing
Dangerous? Well I don't think this module runs around with a Uzi spraying everyone. I don't think it is a good practice to force an install on errors. You should always get to the bottom of why the errors are happening to start with. Once you do and have applied a fix, it should install cleanly, and you will be a better programmer for having investigated the cause. Bob Byron Young wrote: > Hi J Shirley > > I'm trying to install your neat C::V::Email package but I'm running into some > test failures. I thought you might like to know about them. The test > failures look benign to me so I'm going to force install, but let me know if > you think that the errors could be dangerous. > > Let me know if you want me to try out a test patch. > > Thanks > Byron > > > CPAN.pm: Going to build J/JS/JSHIRLEY/Catalyst-View-Email-0.11.tar.gz > > Cannot determine perl version info from lib/Catalyst/View/Email.pm > *** Module::AutoInstall version 1.03 > *** Checking for Perl dependencies... > [Core Features] > - Catalyst ...loaded. (5.71000 >= 5.7) > - Class::C3 ...loaded. (0.19) > - Email::Send ...loaded. (2.194 >= 2.185) > - Email::MIME ...loaded. (1.863 >= 1.859) > - Email::MIME::Creator ...loaded. (1.455 >= 1.453) > [Template Toolkit Support] > - Catalyst::View::TT...loaded. (0.26) > [Mason Support] > - Catalyst::View::Mason ...loaded. (0.16) > [Net::SMTP Support] > - MIME::Base64 ...loaded. (3.07) > - Authen::SASL ...missing. > ==> Auto-install the 1 optional module(s) from CPAN? [n] > *** Module::AutoInstall configuration finished. > Checking if your kit is complete... > Warning: the following files are missing in your kit: > t/lib/TestApp/cache/obj/ > Please inform the author. > Writing Makefile for Catalyst::View::Email > cp lib/Catalyst/View/Email.pm blib/lib/Catalyst/View/Email.pm > cp lib/Catalyst/View/Email/Template.pm > blib/lib/Catalyst/View/Email/Template.pm > cp lib/Catalyst/Helper/View/Email.pm blib/lib/Catalyst/Helper/View/Email.pm > cp lib/Catalyst/Helper/View/Email/Template.pm > blib/lib/Catalyst/Helper/View/Email/Template.pm > Manifying blib/man3/Catalyst::View::Email.3pm > Manifying blib/man3/Catalyst::View::Email::Template.3pm > Manifying blib/man3/Catalyst::Helper::View::Email::Template.3pm > Manifying blib/man3/Catalyst::Helper::View::Email.3pm > JSHIRLEY/Catalyst-View-Email-0.11.tar.gz > /usr/bin/make -- OK > Running make test > PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" > "test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/01use.t t/02pod.t > t/04basic.t t/05template.t t/06config.t t/07mason.t > t/01use.ok > t/02pod.skipped: set TEST_POD to enable this test > t/04basic...[warn] DEPRECATION WARNING: TestApp::View::Mason sets the > use_match config variable to a true value. > This has been deprecated. Please see the Catalyst::View::Mason > documentation for details on use_match. > t/04basic...ok > t/05template[warn] DEPRECATION WARNING: TestApp::View::Mason sets the > use_match config variable to a true value. > This has been deprecated. Please see the Catalyst::View::Mason > documentation for details on use_match. > t/05template2/11 > # Failed test 'text/plain part ok' > # at t/05template.t line 33. > # got: 'text/plain' > # expected: 'text/plain; charset="us-ascii"' > > # Failed test 'text/html ok' > # at t/05template.t line 36. > # got: 'text/html' > # expected: 'text/html; charset="us-ascii"' > # Looks like you failed 2 tests of 11. > t/05template Dubious, test returned 2 (wstat 512, 0x200) > Failed 2/11 subtests > t/06config..[warn] DEPRECATION WARNING: TestApp::View::Mason sets the > use_match config variable to a true value. > This has been deprecated. Please see the Catalyst::View::Mason > documentation for details on use_match. > t/06config..1/13 > # Failed test 'text/plain ok' > # at t/06config.t line 37. > # got: 'text/plain' > # expected: 'text/plain; charset="us-ascii"' > > # Failed test 'text/html ok' > # at t/06config.t line 39. > # got: 'text/html' > # expected: 'text/html; charset="us-ascii"' > # Looks like you failed 2 tests of 13. > t/06config.. Dubious, test returned 2 (wstat 512, 0x200) > Failed 2/13 subtests > t/07mason...[warn] DEPRECATION WARNING: TestApp::View::Mason sets the > use_match config variable to a true value. > This has been deprecated. Please see the Catalyst::View::Mason > documentation for details on use_match. > t/07mason...1/10 > # Failed test 'text/plain ok' > # at t/07mason.t line 32. > # got: 'text/plain' > # expected: 'text/plain; charset="us-ascii"' > > # Failed test 'text/html ok' > # at t/07mason.t line 34. > # got: 'text/html' > # expected: 'text/html; charset="us-ascii"' > # Looks like you failed 2 tests of 10. > t/07mason... Dubious, test returned 2 (wstat 512, 0x200) > F
Re: [Catalyst] Catalyst::View::Email tests failing
On Thu, Feb 5, 2009 at 11:02 AM, Byron Young wrote: > Hi J Shirley > > I'm trying to install your neat C::V::Email package but I'm running into some > test failures. I thought you might like to know about them. The test > failures look benign to me so I'm going to force install, but let me know if > you think that the errors could be dangerous. > > Let me know if you want me to try out a test patch. > > Thanks > Byron > > > CPAN.pm: Going to build J/JS/JSHIRLEY/Catalyst-View-Email-0.11.tar.gz > > Cannot determine perl version info from lib/Catalyst/View/Email.pm > *** Module::AutoInstall version 1.03 > *** Checking for Perl dependencies... > [Core Features] > - Catalyst ...loaded. (5.71000 >= 5.7) > - Class::C3 ...loaded. (0.19) > - Email::Send ...loaded. (2.194 >= 2.185) > - Email::MIME ...loaded. (1.863 >= 1.859) > - Email::MIME::Creator ...loaded. (1.455 >= 1.453) > [Template Toolkit Support] > - Catalyst::View::TT...loaded. (0.26) > [Mason Support] > - Catalyst::View::Mason ...loaded. (0.16) > [Net::SMTP Support] > - MIME::Base64 ...loaded. (3.07) > - Authen::SASL ...missing. > ==> Auto-install the 1 optional module(s) from CPAN? [n] > *** Module::AutoInstall configuration finished. > Checking if your kit is complete... > Warning: the following files are missing in your kit: >t/lib/TestApp/cache/obj/ > Please inform the author. > Writing Makefile for Catalyst::View::Email > cp lib/Catalyst/View/Email.pm blib/lib/Catalyst/View/Email.pm > cp lib/Catalyst/View/Email/Template.pm > blib/lib/Catalyst/View/Email/Template.pm > cp lib/Catalyst/Helper/View/Email.pm blib/lib/Catalyst/Helper/View/Email.pm > cp lib/Catalyst/Helper/View/Email/Template.pm > blib/lib/Catalyst/Helper/View/Email/Template.pm > Manifying blib/man3/Catalyst::View::Email.3pm > Manifying blib/man3/Catalyst::View::Email::Template.3pm > Manifying blib/man3/Catalyst::Helper::View::Email::Template.3pm > Manifying blib/man3/Catalyst::Helper::View::Email.3pm > JSHIRLEY/Catalyst-View-Email-0.11.tar.gz > /usr/bin/make -- OK > Running make test > PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" > "test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/01use.t t/02pod.t > t/04basic.t t/05template.t t/06config.t t/07mason.t > t/01use.ok > t/02pod.skipped: set TEST_POD to enable this test > t/04basic...[warn] DEPRECATION WARNING: TestApp::View::Mason sets the > use_match config variable to a true value. > This has been deprecated. Please see the Catalyst::View::Mason > documentation for details on use_match. > t/04basic...ok > t/05template[warn] DEPRECATION WARNING: TestApp::View::Mason sets the > use_match config variable to a true value. > This has been deprecated. Please see the Catalyst::View::Mason > documentation for details on use_match. > t/05template2/11 > # Failed test 'text/plain part ok' > # at t/05template.t line 33. > # got: 'text/plain' > # expected: 'text/plain; charset="us-ascii"' > > # Failed test 'text/html ok' > # at t/05template.t line 36. > # got: 'text/html' > # expected: 'text/html; charset="us-ascii"' > # Looks like you failed 2 tests of 11. > t/05template Dubious, test returned 2 (wstat 512, 0x200) > Failed 2/11 subtests > t/06config..[warn] DEPRECATION WARNING: TestApp::View::Mason sets the > use_match config variable to a true value. > This has been deprecated. Please see the Catalyst::View::Mason > documentation for details on use_match. > t/06config..1/13 > # Failed test 'text/plain ok' > # at t/06config.t line 37. > # got: 'text/plain' > # expected: 'text/plain; charset="us-ascii"' > > # Failed test 'text/html ok' > # at t/06config.t line 39. > # got: 'text/html' > # expected: 'text/html; charset="us-ascii"' > # Looks like you failed 2 tests of 13. > t/06config.. Dubious, test returned 2 (wstat 512, 0x200) > Failed 2/13 subtests > t/07mason...[warn] DEPRECATION WARNING: TestApp::View::Mason sets the > use_match config variable to a true value. > This has been deprecated. Please see the Catalyst::View::Mason > documentation for details on use_match. > t/07mason...1/10 > # Failed test 'text/plain ok' > # at t/07mason.t line 32. > # got: 'text/plain' > # expected: 'text/plain; charset="us-ascii"' > > # Failed test 'text/html ok' > # at t/07mason.t line 34. > # got: 'text/html' > # expected: 'text/html; charset="us-ascii"' > # Looks like you failed 2 tests of 10. > t/07mason... Dubious, test returned 2 (wstat 512, 0x200) > Failed 2/10 subtests > > Test Summary Report > --- > t/05template (Wstat: 512 Tests: 11 Failed: 2) > Failed tests: 8, 10 > Non-zero exit status: 2 > t/06config (Wstat: 512 Tests: 13 Failed: 2) > Failed tests: 10, 12 > Non-zero exit status: 2 > t/07mason (Wstat: 512 Tests: 10 Failed: 2) > Failed tests: 7, 9 > Non-zero
[Catalyst] Catalyst::View::Email tests failing
Hi J Shirley I'm trying to install your neat C::V::Email package but I'm running into some test failures. I thought you might like to know about them. The test failures look benign to me so I'm going to force install, but let me know if you think that the errors could be dangerous. Let me know if you want me to try out a test patch. Thanks Byron CPAN.pm: Going to build J/JS/JSHIRLEY/Catalyst-View-Email-0.11.tar.gz Cannot determine perl version info from lib/Catalyst/View/Email.pm *** Module::AutoInstall version 1.03 *** Checking for Perl dependencies... [Core Features] - Catalyst ...loaded. (5.71000 >= 5.7) - Class::C3 ...loaded. (0.19) - Email::Send ...loaded. (2.194 >= 2.185) - Email::MIME ...loaded. (1.863 >= 1.859) - Email::MIME::Creator ...loaded. (1.455 >= 1.453) [Template Toolkit Support] - Catalyst::View::TT...loaded. (0.26) [Mason Support] - Catalyst::View::Mason ...loaded. (0.16) [Net::SMTP Support] - MIME::Base64 ...loaded. (3.07) - Authen::SASL ...missing. ==> Auto-install the 1 optional module(s) from CPAN? [n] *** Module::AutoInstall configuration finished. Checking if your kit is complete... Warning: the following files are missing in your kit: t/lib/TestApp/cache/obj/ Please inform the author. Writing Makefile for Catalyst::View::Email cp lib/Catalyst/View/Email.pm blib/lib/Catalyst/View/Email.pm cp lib/Catalyst/View/Email/Template.pm blib/lib/Catalyst/View/Email/Template.pm cp lib/Catalyst/Helper/View/Email.pm blib/lib/Catalyst/Helper/View/Email.pm cp lib/Catalyst/Helper/View/Email/Template.pm blib/lib/Catalyst/Helper/View/Email/Template.pm Manifying blib/man3/Catalyst::View::Email.3pm Manifying blib/man3/Catalyst::View::Email::Template.3pm Manifying blib/man3/Catalyst::Helper::View::Email::Template.3pm Manifying blib/man3/Catalyst::Helper::View::Email.3pm JSHIRLEY/Catalyst-View-Email-0.11.tar.gz /usr/bin/make -- OK Running make test PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/01use.t t/02pod.t t/04basic.t t/05template.t t/06config.t t/07mason.t t/01use.ok t/02pod.skipped: set TEST_POD to enable this test t/04basic...[warn] DEPRECATION WARNING: TestApp::View::Mason sets the use_match config variable to a true value. This has been deprecated. Please see the Catalyst::View::Mason documentation for details on use_match. t/04basic...ok t/05template[warn] DEPRECATION WARNING: TestApp::View::Mason sets the use_match config variable to a true value. This has been deprecated. Please see the Catalyst::View::Mason documentation for details on use_match. t/05template2/11 # Failed test 'text/plain part ok' # at t/05template.t line 33. # got: 'text/plain' # expected: 'text/plain; charset="us-ascii"' # Failed test 'text/html ok' # at t/05template.t line 36. # got: 'text/html' # expected: 'text/html; charset="us-ascii"' # Looks like you failed 2 tests of 11. t/05template Dubious, test returned 2 (wstat 512, 0x200) Failed 2/11 subtests t/06config..[warn] DEPRECATION WARNING: TestApp::View::Mason sets the use_match config variable to a true value. This has been deprecated. Please see the Catalyst::View::Mason documentation for details on use_match. t/06config..1/13 # Failed test 'text/plain ok' # at t/06config.t line 37. # got: 'text/plain' # expected: 'text/plain; charset="us-ascii"' # Failed test 'text/html ok' # at t/06config.t line 39. # got: 'text/html' # expected: 'text/html; charset="us-ascii"' # Looks like you failed 2 tests of 13. t/06config.. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/13 subtests t/07mason...[warn] DEPRECATION WARNING: TestApp::View::Mason sets the use_match config variable to a true value. This has been deprecated. Please see the Catalyst::View::Mason documentation for details on use_match. t/07mason...1/10 # Failed test 'text/plain ok' # at t/07mason.t line 32. # got: 'text/plain' # expected: 'text/plain; charset="us-ascii"' # Failed test 'text/html ok' # at t/07mason.t line 34. # got: 'text/html' # expected: 'text/html; charset="us-ascii"' # Looks like you failed 2 tests of 10. t/07mason... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/10 subtests Test Summary Report --- t/05template (Wstat: 512 Tests: 11 Failed: 2) Failed tests: 8, 10 Non-zero exit status: 2 t/06config (Wstat: 512 Tests: 13 Failed: 2) Failed tests: 10, 12 Non-zero exit status: 2 t/07mason (Wstat: 512 Tests: 10 Failed: 2) Failed tests: 7, 9 Non-zero exit status: 2 Files=6, Tests=40, 3 wallclock secs ( 0.01 usr 0.07 sys + 0.65 cusr 2.12 csys = 2.85 CPU) Result: FAIL Failed 3/6 test programs. 6/40 subtests failed. make: *** [test_dynamic] Error 2 JSHIRLEY/Catalyst-View-Email-0.11.tar.gz /usr/bin/make test -- NOT OK //h
[Catalyst] New Catalyst Book?
Is a new Catalyst book being written? I have the original Rockway book, my interest is in a new work-in-progress book. If so, is there an early-access electronic version available? Thanks Bob Cochran Greenbelt, Maryland, USA ___ 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] Easiest Way To Update Fedora 10 to Catalyst-Runtime-5.71000
My installation of Fedora 10 x86_64 is using Fedora-packaged Perl (perl-5.10.0-53.fc10.x86_64) and the perl-Catalyst-Runtime (perl-Catalyst-Runtime-5.7015-1.fc10.noarch) and it doesn't seem to be maintained; there is no 5.71000 release as an RPM package. I have read the thread from last summer about Red Hat and CentOS releases not having real good Perl installations. I'd like to upgrade to 5.71000, using an RPM package if possible. (perhaps I can get the source RPM for 5.7015 and rebuild it for 5.71000 with any new dependencies added in. I have an RPM build tree on this machine that I've been using to build stuff like avr-gcc.) Any suggestions? Bob Cochran Greenbelt, Maryland, USA ___ 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] IO::Pipe and the Catalyst Server
On Thu, Feb 05, 2009 at 04:28:57PM +0100, Florian Ragwitz wrote:
> On Thu, Feb 05, 2009 at 07:10:07AM -0800, Bill Moseley wrote:
> > Same problem.
>
> Would you mind preparing a testcase for this?
I can try. See attached diff against svn 9215.
$ prove -vl t/live_fork.t
t/live_fork
1..15
TestApp is trying to use NEXT, which is deprecated. Please see the
Class::C3::Adopt::NEXT documentation for details at
/home/moseley/cat_5.8/t/lib/Catalyst/Plugin/Test/Plugin.pm line 23
ok 1 - system
ok 2 - is YAML
ok 3 - exited OK
ok 4 - `backticks`
ok 5 - is YAML
ok 6 - exited successfully
ok 7 - contains ^/bin/ls$
ok 8 - contains two newlines
ok 9 - fork
ok 10 - is YAML
ok 11 - fork's "pid" wasn't 0
ok 12 - fork got a new pid
ok 13 - fork was effective
ok 14 - io_pipe
ok 15 - io_pipe returned data from handle
ok
All tests successful.
Files=1, Tests=15, 1 wallclock secs ( 0.02 usr 0.01 sys + 0.98 cusr 0.06
csys = 1.07 CPU)
Result: PASS
>
> TestApp::Controller::Fork / t/live_fork.t already has similar tests. You
> can run them against the dev server using t/optional_http-server.t.
Should App::Prove be listed as a dependency in test_requires?
(although test_requires doesn't seem to work like I think it should. ;)
Not 100% clear on how to run it but here's my attempt:
(trimmed a bit):
$ TEST_HTTP=1 REMOTE_FORK=1 perl -Ilib t/optional_http-server.t t/live_fork.t
1..1
created "TestApp"
created "TestApp/script"
[...]
Waiting for server to start...
1..15
ok 1 - system
Use of uninitialized value in join or string at t/live_fork.t line 32.
ok 2 - is YAML
ok 3 - exited OK
ok 4 - `backticks`
ok 5 - is YAML
ok 6 - exited successfully
ok 7 - contains ^/bin/ls$
ok 8 - contains two newlines
ok 9 - fork
ok 10 - is YAML
ok 11 - fork's "pid" wasn't 0
ok 12 - fork got a new pid
ok 13 - fork was effective
ok 14 - io_pipe
not ok 15 - io_pipe returned data from handle
# Failed test 'io_pipe returned data from handle'
# at t/live_fork.t line 70.
# got: 'FATAL ERROR: Caught exception in
TestApp::Controller::Fork->io_pipe "Failed read from IO::Pipe handle at
/home/moseley/cat_5.8/t/tmp/TestApp/script/../lib/TestApp/Controller/Fork.pm
line 72."'
# expected: 'ok'
# Looks like you failed 1 test of 15.
not ok 1 - live tests
# Failed test 'live tests'
# at t/optional_http-server.t line 69.
# got: '256'
# expected: '0'
# Looks like you failed 1 test of 1.
--
Bill Moseley
mose...@hank.org
Sent from my iMutt
Index: t/lib/TestApp/Controller/Fork.pm
===
--- t/lib/TestApp/Controller/Fork.pm (revision 9215)
+++ t/lib/TestApp/Controller/Fork.pm (working copy)
@@ -58,4 +58,21 @@
$c->response->body(Dump({pid => $pid, result => $x}));
}
+
+# Test should only call if it knows IO::Pipe exist and
+# /bin/ls is available
+
+sub io_pipe : Local {
+my ($self, $c) = @_;
+
+eval 'require IO::Pipe' || die 'IO::Pipe failed require: ' . $@;
+
+my $pipe = IO::Pipe->new;
+$pipe->reader( '/bin/ls' );
+my $line = <$pipe> || die 'Failed read from IO::Pipe handle';
+$c->response->body( 'ok' );
+}
+
+
+
1;
Index: t/live_fork.t
===
--- t/live_fork.t (revision 9215)
+++ t/live_fork.t (working copy)
@@ -23,7 +23,7 @@
plan skip_all => 'Skipping fork tests: no /bin/ls'
if !-e '/bin/ls'; # see if /bin/ls exists
-plan tests => 13; # otherwise
+plan tests => 15; # otherwise
{
system:
@@ -60,3 +60,12 @@
isnt($result_ref->{pid}, $$, 'fork got a new pid');
is($result_ref->{result}, 'ok', 'fork was effective');
}
+
+SKIP: {
+ io_pipe:
+eval 'require IO::Pipe'
+|| skip "IO::Pipe not installed", 2;
+
+ok(my $result = get( '/fork/io_pipe'), 'io_pipe' );
+is( $result, 'ok', 'io_pipe returned data from handle' );
+}
___
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] Re: Hello, Deployment of Catalyst apps in a shared web hosting account without shell
On Thu, Feb 5, 2009 at 8:42 AM, Anton Katsarov wrote: > В 08:30 -0800 на 05.02.2009 (чт), J. Shirley написа: >> If 5 seconds works for you, cool. >> >> Just as a benchmark, all my apps send full HTML in under .8 seconds >> (or I tune them until they do). It's relatively easy to get FCGI >> support and a lot of cheap hosts provide it. > > I don't want to argue, but HTML loads for about 1 sec. All the other > time is for loading images and flash banners. I can also confess that > the Internet connection in my town is not so good. > > The time to first byte (not HTML processing) in all reporting tools I used shows >3s (anywhere from 3.1 to 4.8). Also, time to start render is a good metric, too (that is is when the HTML document is loaded sufficiently). Look at what Bill posted above as far as metrics. If you want to build an application that scales out, you need to understand these things. If you just build one for yourself, it's up to you. Also, I'm not arguing, it is simply a fact that running a Catalyst application via CGI results in very slow load times. That is why the recommendation is using FastCGI. If it loads fast enough for you, that's awesome. -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/
Re: [Catalyst] Re: Hello, Deployment of Catalyst apps in a shared web hosting account without shell
On Thu, Feb 05, 2009 at 06:09:58PM +0200, Anton Katsarov wrote: > В 13:20 -0800 на 04.02.2009 (ср), J. Shirley написа: > > > It's hideously slow. It took 16 seconds to load, and most of that was > > the first byte. > > I do agree. But that is because of the statics. I did some changes to > my .htaccess to serve the static directly from the webserver and now it > loads for 5 seconds to me. Here are the changes: Here's a tool you can use: http://performance.webpagetest.org:8080/ Will give you some nice charts and a summary. Below is the detail of the report. Obviously, you will ignore much of the report as it won't really apply. Optimization Report : 02/05/09 at 11:35:13 Results for 'http://www.djmag.bg/': Page load time: 17.010 seconds Time to first byte: 3.394 seconds Time to Base Page Downloaded: 3.989 seconds Time to Start Render: 7.036 seconds Time to Document Complete: 17.010 seconds Time to Fully Loaded: 17.010 seconds Bytes sent out: 10.963 KB Bytes received: 519.764 KB DNS Lookups: 1 Connections: 31 Requests: 31 OK Requests: 31 Redirects:0 Not Modified: 0 Not Found:0 Other:0 Base Page Response: 200 Enable browser caching of static assets: FAILED (No max-age or expires) - http://www.djmag.bg/static/banners/1159774171_sait.jpg FAILED (No max-age or expires) - http://www.djmag.bg/static/banners/208781512_160x600.swf FAILED (No max-age or expires) - http://www.djmag.bg/static/banners/266753453_468-60.swf FAILED (No max-age or expires) - http://www.djmag.bg/static/banners/494549063_240x120.jpg FAILED (No max-age or expires) - http://www.djmag.bg/static/banners/655846930_240x120.jpg FAILED (No max-age or expires) - http://www.djmag.bg/static/banners/73159537_Banner_DavidGuetta_728x90.swf FAILED (No max-age or expires) - http://www.djmag.bg/static/css/bg.png FAILED (No max-age or expires) - http://www.djmag.bg/static/css/events.png FAILED (No max-age or expires) - http://www.djmag.bg/static/css/formcheck.css FAILED (No max-age or expires) - http://www.djmag.bg/static/css/forum.png FAILED (No max-age or expires) - http://www.djmag.bg/static/css/header.png FAILED (No max-age or expires) - http://www.djmag.bg/static/css/logo1.png FAILED (No max-age or expires) - http://www.djmag.bg/static/css/logo2.png FAILED (No max-age or expires) - http://www.djmag.bg/static/css/lr.png FAILED (No max-age or expires) - http://www.djmag.bg/static/css/print.css FAILED (No max-age or expires) - http://www.djmag.bg/static/css/screen.css FAILED (No max-age or expires) - http://www.djmag.bg/static/css/title.png FAILED (No max-age or expires) - http://www.djmag.bg/static/css/webface.png FAILED (No max-age or expires) - http://www.djmag.bg/static/images/mag.png FAILED (No max-age or expires) - http://www.djmag.bg/static/images/news/th/1032662367_man_demobaza_icon.jpg FAILED (No max-age or expires) - http://www.djmag.bg/static/images/news/th/1217226378_t21.jpg FAILED (No max-age or expires) - http://www.djmag.bg/static/images/news/th/32663603_636370654_l.jpg FAILED (No max-age or expires) - http://www.djmag.bg/static/images/news/th/363862442_DJMag_BG_logo.jpg FAILED (No max-age or expires) - http://www.djmag.bg/static/images/news/th/405249846_NEWS-17473-be3cbb5737aee381d2bf115571f73d43.jpg FAILED (No max-age or expires) - http://www.djmag.bg/static/images/news/th/648446979_women_demobaza_icon.jpg FAILED (No max-age or expires) - http://www.djmag.bg/static/images/news/th/6589703_J_BTour-One_th.jpg FAILED (No max-age or expires) - http://www.djmag.bg/static/images/news/th/756999078_logo.jpg FAILED (No max-age or expires) - http://www.djmag.bg/static/images/pic.png FAILED (No max-age or expires) - http://www.djmag.bg/static/js/mootools.js FAILED (No max-age or expires) - http://www.djmag.bg/static/js/page.js Cache score : 0 Use one CDN for all static assets: FAILED - http://www.djmag.bg/static/banners/1159774171_sait.jpg FAILED - http://www.djmag.bg/static/banners/208781512_160x600.swf FAILED - http://www.djmag.bg/static/banners/266753453_468-60.swf FAILED - http://www.djmag.bg/static/banners/494549063_240x120.jpg FAILED - http://www.djmag.bg/static/banners/655846930_240x120.jpg FAILED - http://www.djmag.bg/static/banners/73159537_Banner_DavidGuetta_728x90.swf FAILED - http://www.djmag.bg/static/css/bg.png FAILED - http://www.djmag.bg/static/css/events.png FAILED - http://www.djmag.bg/static/css/formcheck.css FAILED - http://www.djmag.bg/static/css/forum.png FAILED - http://www.djmag.bg/static/css/header.png FAILED - http://www.djmag.bg/static/css/logo1.png FAILED - http://www.djmag.bg/static/css/logo2.png FAILED - http://www.djmag.bg/static/css/lr.png FAILED - http://www.djmag.bg/static/css/print.css FAILED - http://www.djmag.bg/static/css/screen.css FA
Re: [Catalyst] Re: Hello, Deployment of Catalyst apps in a shared web hosting account without shell
В 08:30 -0800 на 05.02.2009 (чт), J. Shirley написа: > If 5 seconds works for you, cool. > > Just as a benchmark, all my apps send full HTML in under .8 seconds > (or I tune them until they do). It's relatively easy to get FCGI > support and a lot of cheap hosts provide it. I don't want to argue, but HTML loads for about 1 sec. All the other time is for loading images and flash banners. I can also confess that the Internet connection in my town is not so good. ___ 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] Re: Hello, Deployment of Catalyst apps in a shared web hosting account without shell
2009/2/5 J. Shirley :
> On Thu, Feb 5, 2009 at 8:09 AM, Anton Katsarov wrote:
>> В 13:20 -0800 на 04.02.2009 (ср), J. Shirley написа:
>>
>>> It's hideously slow. It took 16 seconds to load, and most of that was
>>> the first byte.
>>
>> I do agree. But that is because of the statics. I did some changes to
>> my .htaccess to serve the static directly from the webserver and now it
>> loads for 5 seconds to me. Here are the changes:
>>
>> RewriteCond %{REQUEST_URI} !^/?(cgi-bin/test.cgi|static|root)
>> RewriteRule ^(.*)$ /cgi-bin/test.cgi/$1 [PT,L]
>>
>> RewriteRule ^/?static/(.*)$ /root/static/$1 [PT,L]
>> RewriteRule ^/?root/(lib|src).*$ /404 [PT,L]
>>
>> That is not the best decision, but I thins now is fast enough.
>
> If 5 seconds works for you, cool.
>
> Just as a benchmark, all my apps send full HTML in under .8 seconds
> (or I tune them until they do). It's relatively easy to get FCGI
> support and a lot of cheap hosts provide it.
>
> Not using it is just silly.
I agree with what J Shirley is saying, 5s is still "too slow".
If nothing else, it's a question of concurrent load you can handle as
much as of page load times.
You get 5s when you're the only person hitting the box. What's
performance like when the site gets busy? That's when the forking time
of CGI really hurts.
/joel
___
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] Re: Hello, Deployment of Catalyst apps in a shared web hosting account without shell
On Thu, Feb 5, 2009 at 8:09 AM, Anton Katsarov wrote:
> В 13:20 -0800 на 04.02.2009 (ср), J. Shirley написа:
>
>> It's hideously slow. It took 16 seconds to load, and most of that was
>> the first byte.
>
> I do agree. But that is because of the statics. I did some changes to
> my .htaccess to serve the static directly from the webserver and now it
> loads for 5 seconds to me. Here are the changes:
>
> RewriteCond %{REQUEST_URI} !^/?(cgi-bin/test.cgi|static|root)
> RewriteRule ^(.*)$ /cgi-bin/test.cgi/$1 [PT,L]
>
> RewriteRule ^/?static/(.*)$ /root/static/$1 [PT,L]
> RewriteRule ^/?root/(lib|src).*$ /404 [PT,L]
>
> That is not the best decision, but I thins now is fast enough.
If 5 seconds works for you, cool.
Just as a benchmark, all my apps send full HTML in under .8 seconds
(or I tune them until they do). It's relatively easy to get FCGI
support and a lot of cheap hosts provide it.
Not using it is just silly.
-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/
Re: [Catalyst] Re: Hello, Deployment of Catalyst apps in a shared web hosting account without shell
В 13:20 -0800 на 04.02.2009 (ср), J. Shirley написа:
> It's hideously slow. It took 16 seconds to load, and most of that was
> the first byte.
I do agree. But that is because of the statics. I did some changes to
my .htaccess to serve the static directly from the webserver and now it
loads for 5 seconds to me. Here are the changes:
RewriteCond %{REQUEST_URI} !^/?(cgi-bin/test.cgi|static|root)
RewriteRule ^(.*)$ /cgi-bin/test.cgi/$1 [PT,L]
RewriteRule ^/?static/(.*)$ /root/static/$1 [PT,L]
RewriteRule ^/?root/(lib|src).*$ /404 [PT,L]
That is not the best decision, but I thins now is fast enough.
___
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] IO::Pipe and the Catalyst Server
Bill Moseley wrote on 02/05/2009 09:10 AM: > On Thu, Feb 05, 2009 at 01:23:03PM +0100, Florian Ragwitz wrote: >> On Wed, Feb 04, 2009 at 10:25:15PM -0800, Bill Moseley wrote: >>> I have a module that uses IO::Pipe and when I run it under the >>> Catalyst server the pipe doesn't work (see below). >> Please try to reproduce with Catalyst-Runtime-5.8000_06. It has a fix >> related to spawning external processes from the dev server. > > $ PERL5LIB=$HOME/cur_cat script/pipe_server.pl > 5.8000_06 > You can connect to your server at http://bumby2:3000 > about to read from handle > hello > > Same problem. > > is it possible this is related to how Cat can mess with STDOUT and STDIN? I have these lines in SVN::Class: # this trick cribbed from mst's Catalyst::Controller::WrapCGI # we alias STDIN and STDOUT since Catalyst (and presumaly other code) # might be messing with STDOUT or STDIN open( *REAL_STDIN, "<&=" . fileno(*STDIN) ); open( *REAL_STDOUT, ">>&=" . fileno(*STDOUT) ); -- Peter Karman . pe...@peknet.com . http://peknet.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] IO::Pipe and the Catalyst Server
On Thu, Feb 05, 2009 at 07:10:07AM -0800, Bill Moseley wrote: > Same problem. Would you mind preparing a testcase for this? TestApp::Controller::Fork / t/live_fork.t already has similar tests. You can run them against the dev server using t/optional_http-server.t. -- BOFH excuse #86: Runt packets signature.asc Description: Digital signature ___ 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] IO::Pipe and the Catalyst Server
On Thu, Feb 05, 2009 at 01:23:03PM +0100, Florian Ragwitz wrote: > On Wed, Feb 04, 2009 at 10:25:15PM -0800, Bill Moseley wrote: > > I have a module that uses IO::Pipe and when I run it under the > > Catalyst server the pipe doesn't work (see below). > > Please try to reproduce with Catalyst-Runtime-5.8000_06. It has a fix > related to spawning external processes from the dev server. $ PERL5LIB=$HOME/cur_cat script/pipe_server.pl 5.8000_06 You can connect to your server at http://bumby2:3000 about to read from handle hello Same problem. -- Bill Moseley mose...@hank.org Sent from my iMutt ___ 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] Opportunity to submit an article to a leading german computer maagazine
Hi all, I just got a request for an Catalyst article that will be published in a special edition of the iX magazine. I wont have time myself so I thought maybe here might be some folks from Germany interested in taking up the offer to promote Catalyst and earn a few bucks. I've written an article few years back and I'd be happy to provide you with the text as reference (don't know if I am legally allowed to provide it as basis for a new article by another author). You can find the request (in German) below, please contact me for details. Cheers, Sebastian Willert Forwarded Message Subject: Perl-Webframework(s) Date: Thu, 05 Feb 2009 15:15:51 +0100 Hallo zusammen, Wir planen, im Frühjahr (Mai/Juni) ein Sonderheft zum Thema "Web on Rails" zu bringen, dass sich mit Webframeworks für verschiedene Sprachen beschäftigt. Hätten Sie Lust/Zeit, ein Update auf Ihren damaligen Artikel zu verfassen und dabei auf eventuelle Konkurrenz zu Catalyst hinzuweisen? Zum Zeitrahmen: Ich müsste Ihren Artikel im Laufe des April hier haben... Ich würde mich freuen :-) iX - Magazin fuer professionelle Informationstechnik ___ 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] IO::Pipe and the Catalyst Server
On Thu, Feb 05, 2009 at 12:51:18PM +, Peter Edwards wrote: >Was that the change to the catching of signal SIGCHLD ? Exactly. -- BOFH excuse #66: bit bucket overflow signature.asc Description: Digital signature ___ 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] IO::Pipe and the Catalyst Server
> > 2009/2/5 Florian Ragwitz > >> On Wed, Feb 04, 2009 at 10:25:15PM -0800, Bill Moseley wrote: >> > I have a module that uses IO::Pipe and when I run it under the >> > Catalyst server the pipe doesn't work (see below). >> >> Please try to reproduce with Catalyst-Runtime-5.8000_06. It has a fix >> related to spawning external processes from the dev server. >> > Was that the change to the catching of signal SIGCHLD ?I've been meaning to try that out too. Thanks, Peter ___ 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] IO::Pipe and the Catalyst Server
On Wed, Feb 04, 2009 at 10:25:15PM -0800, Bill Moseley wrote: > I have a module that uses IO::Pipe and when I run it under the > Catalyst server the pipe doesn't work (see below). Please try to reproduce with Catalyst-Runtime-5.8000_06. It has a fix related to spawning external processes from the dev server. -- BOFH excuse #311: transient bus protocol violation signature.asc Description: Digital signature ___ 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] template design issue: varibales stand-alone components
I am used to the idea that I can have a parent template (autohandler in Mason), which provides basic navigation and status display for the site; autohandler then invokes another template (a master template for that particual page's content) which itself uses various odd templates for Using Mason with Catalyst does not imply that you have to lose your autohandlers. Actually, we've found the transition from Mason-only sites to Catalyst+Mason sites to work quite smoothly. Also, this makes me cringe a bit: Dear Dr. <% $surname %>! I would think you would hide that in an object (or hash if you like as TT doesn't care), and do: Dear Dr. [% user.surname %] so you don't spend all your coding time populating the stash in your controllers. You're actually comparing apples to oranges here. In your Mason-example you've put the surname into the stash, while your TT-example stashes the entire object. If you stash the object, your Mason-example would look like: Dear Dr. <% $user->surname() %>! which is pure perl, which "user.surname" most decidedly isn't. It's a matter of opininon, but I'd rather use perl than something else with a learning curve. Haven't tried out TT, so this is just my biased opinion. Alex ___ 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] template design issue: varibales stand-alone components
J. Shirley schrieb: On Wed, Feb 4, 2009 at 4:40 PM, Malcolm wrote: On Wednesday 04 February 2009, Gene Selkov wrote: I understood as much. The problem I am grappling with is the complexity of the web pages I have to present, with many different states and transitions. There is no way I can code for that with a single template. I am used to the idea that I can have a parent template (autohandler in Mason), which provides basic navigation and status display for the site; Is there any reason for not using Mason? I've been using it with Catalyst without any problems. I think it is almost like using Emacs as a text editor, versus vi. Emacs users espouse the amazing features and customization, while vi users just sit down and write code because they're using an inferior editor (I use vi.) You already have a framework, so why use Mason? Mason's dhandlers and autohandlers are some of its better features, but they're not really designed to work in conjunction with Catalyst (you can still use them, but... probably more work than you would get unless you had specific goals to reach.) If you simply think of templating languages, I find that Mason's distinguishing advantages disappear if you -only- use is as a templating language. So, it boils down to: Do you know Mason well enough to get the most out of it, while still designing your Catalyst application concisely and in an abstract fashion? If not, probably best to use TT, which is simpler and offers some really neat features that seem to favor better Catalyst applications (WRAPPER, most notably). Hope that helps, and I can avoid any flamewars :) one simple question: i love the autohandlers and use a liddle hack to implement it to TT ... is that not a good feature? I extend the navigation in the autohandles or setting some defaults for all templates in a directory. Perhaps there is already a official Plugin for TT i dont know? ___ 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/ -- Mit freundlichen Grüßen Felix Antonius Wilhelm Ostmann -- Websuche Search Technology GmbH & Co. KG Martinistraße 3 - D-49080 Osnabrück - Germany Tel.: +49 541 40666-0 - Fax:+49 541 40666-22 Email: i...@websuche.de - Website: www.websuche.de -- AG Osnabrück - HRA 200252 - Ust-Ident: DE814737310 Komplementärin: Websuche Search Technology Verwaltungs GmbH - AG Osnabrück - HRB 200359 Geschäftsführer: Diplom Kaufmann Martin Steinkamp -- ___ 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/
