* On Wed, Jul 15 2009, ian docherty wrote: > Hi > I have been embracing Moose and Catalyst and I have written a Moose > Role to provide BreadCrumb trail navigation for a web application > written in Catalyst. > > Hopefully there are some Catalyst programmers on here? > > The module allows a Catalyst Controller to do be extended by doing a > with' with the module > > My first thought was to call the module > CatalystX::Controller::BreadCrumb but I am not really aware of any > conventions used by people creating modules using Moose Roles. > > I have found CatalystX::Controller::Tabs on cpan but this is a module > that can be used as a base class for a Catalyst Controller and does > not use Moose. > > Any other suggestions would be welcome.
Your name is fine. There was never any differentiation between "package" or "class" or "mixin" before Moose, so it doesn't really make sense for there to be different conventions for "class" and "role". The name is just something you type in to the computer so it knows what to load. As long as people find your code and are able to read the docs, the name is nearly meaningless. (I am going to start naming my modules after random numbers. "class b692705227284724f695666610836aa8799e9e67 extends a8ee5d67c9fbfcdcd565b4b926154e2f58becbe8". OK, maybe not... ;) Regards, Jonathan Rockway -- print just => another => perl => hacker => if $,=$"
