Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
So, I played around with Catalyst for just over 3 hours yesterday.

I was pleasantly suprised how quickly I was able to tie in my own CDBI stuff and make a CRUD screen.

Next up is porting a small piece of a internal webapp to catalyst -- I'll post comments on how that goes, along with any observations about stumbling blocks and/or 'wow!' moments.

Minor startup / documentation quibbles: it would've been easier if...

  • the movies had voice-over soundtrack (english would be helpful for me!)
  • the movies provided context -- "here's what we're going to do and why"
  • the docs made it clearer which part of the helper scripts were essential, vs. just fast scaffolding
  • the docs made it clear you could indeed park these dirs anywhere -- until you bring apache into the picture, the bundlded server means no apache config, no apache dirs, etc. i didn't get that at first.
  • the docs didn't note there was a Mason scaffolding module, just referencing TT (the default) and HTML:Template.
  • Would've liked more in the cookbook on authentication
  • Wasn't clear if the best way to structure a major web app is one Catalyst tree (App, App.pm, etc), or whether each major subcomponent should be its own tree
  • I found the wiki subsite (the old homepage?) http://dev.catalyst.perl.org/ hard to make sense of...
  • I liked these doc links: http://search.cpan.org/dist/Catalyst/lib/Catalyst/Manual.pod
  • The docs were stronger on the M and V then on the C -- I couldn't find doc sample code on controllers and still have some vagueness on the concept...

Anyway, high praise from someone who's a couple hours into catalyst. Results encouraging enuff to forge ahead!

water


In reply to Re^2: Seeking help learning Catalyst -- the obvious links left me befuddled by water
in thread Seeking help learning Catalyst -- the obvious links left me befuddled by water

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others browsing the Monastery: (5)
    As of 2015-07-06 23:49 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









      Results (85 votes), past polls