Re: Need a contractor for HTML::Mason::Critic work
"C.J. Adams-Collier" <[email protected]> Sat, 13 Oct 2007 16:51:20 -0700
| Newsgroups | gmane.comp.web.mason.devel |
|---|---|
| Message-ID | <[email protected]> |
(cc'ing list, as it is on topic and material to the thread) only by proxy. look at Perl::Critic. It addresses the issues you've raised. It is easy to indicate the "policies" applied to a codebase. when it is appropriate for a component to return() a data structure, disable the policy which produces the violation message. Jon and I discussed offline, which is why you have not heard of the project :) On 10/13/07, Gareth Kirwan <[email protected]> wrote: > > On Sat, 2007-10-13 at 11:21 -0700, C.J. Adams-Collier wrote: > > Hey folks, > > > > I need someone who can help me make HTML::Mason::Critic (ie, > > Perl::Critic for Mason components) a reality. Jon and I have mumbled > > back and forth about it, but I want to flesh it out. This is a part > > of a larger project to build infrastructure around Mason as a "RAD" > > and "Agile" development system. > > > > As it stands, it is very easy to do it /wrong/ with Mason. There is > > little feedback to let new developers know that it is /not/ okay to > > put logic inside templates. When compiling, there is no feedback > > about things like using $m->print() instead of having the templating > > system interpolate variables, etc. > > > > If any of you know someone who would be interested in working on such > > a contract that is not on this list, please forward the information. > > Feel free to call me on my cell to make recommendations or (oh, > > please) offer to help: > > > > +1 206 226 5809 > > > > Seattle area is preferred, but we /may/ be able to work something out > for the right remote person. > > I haven't seen this thread bounced around, but it's quite an interesting > one. > > Whilst some of my more successful web applications are pure mason/perl; > our latest generations are all catalyst and mason. > > In this context the notion of auto critic would be very useful, even if > just to stop me shouting "This is catalyst" at my staff! > > Part of what I see as the problem is the versatility of mason > components. > What is completely wrong in a rendering component might be find in the > right context of a component that's always scomp'd and chooses to return > print $answer; > > Do you have much fleshed out in terms of a plan for this? > > Regards > > -- > Gareth Kirwan > Technical Director > Thermeon Europe Ltd, > [email protected] > Tel: +44 (0) 1293 864 303 > > -- moo. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Mason-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-devel