The deal is: if you are a beginner with Catalyst, go to IRC IMMEDIATELY. I'm sorry if this annoys the channel regulars, but that is just my judgement. Posting a question to the group is another option, but frankly I really dislike the interface (ie, sending an email -- I'd much prefer google groups, or phpbb or vbulletin or something), and having to search the group online with google means missing the most recent posts that google hasn't indexed yet. And I've had situations where I couldn't even understand what I really wanted to ask, until I chatted briefly to clear up the terminology.

It's not that the documentation is bad, or that there isn't enough of it -- though for some areas this is true. Just, things are changing so fast, and the whole kit and kaboodle is so overwhelming, that it's better to check in with the developers/groupies and say, "What should I read" than google around.

I bet if enough newbies overwhelmed the channel, the documentation effort would probably accelerate dramatically ;)

In my opinion, the documentation is 50% of the hurdle, the other issue is confusing dependencies, and these two problems are probably interlinked. But yes, things are definitely getting better. Go catalyst.

In reply to Re: Why oh Why oh Whyo (Catalyst Woes) by tphyahoo
in thread Why oh Why oh Whyo (Catalyst Woes) by OverlordQ

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!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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, details, 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, summary, 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.