When I was writing the git hook I found this
https://github.com/fawek/codepainter which seems pretty cool.

On Tue, Jul 24, 2012 at 12:34:39PM +0100, Nicolaas Matthijs wrote:
> I think it would be great if we could have a code formatter for OAE,  
> at least for our most commonly used IDEs (Aptana and TextMate). I'll  
> make this one of the tickets for the code formatting work that is  
> about to happen.
> 
> Kind regards,
> Nicolaas
> 
> 
> 
> On 11 Jul 2012, at 11:53, Darakananda, Apisak wrote:
> 
> > Nicolaas,
> >  On the note of coding style, is there any effort in the community  
> > to create some kind of automatic source code formatter? I am  
> > currently playing around with an "experimental" language Go 
> > (http://golang.org 
> > ). The standard tool set contains a program called "gofmt" that  
> > parses the source files and re-write them in the "canonical way".  
> > I'm not sure how much work it is though, and it might turn out to be  
> > an overkill.
> >
> > Any thoughts?
> > Michael
> >
> > ----- Original Message -----
> > From: "Nicolaas Matthijs" <[email protected]>
> > To: "OAE Production" <[email protected]>, "oae- 
> > dev [email protected]" <[email protected]>
> > Sent: Wednesday, July 11, 2012 2:25:47 PM
> > Subject: [oae-dev] Code styling issues
> >
> > Hi everyone,
> >
> > At last week's UI dev call, we discussed doing a full sweep over the
> > entire codebase, cleaning up all places that do not adhere to our
> > style guide (spacing issues, double quotes instead of single quotes,
> > CSS not expanded, etc.).
> >
> > In the last weeks, various pull requests have been re-opened and
> > slowed down because of the styling issues they had, and therefore we'd
> > like to do one focussed pass and then continue with a commit hook and
> > unit tests that checks for violations of the style guide.
> >
> > However, before we go ahead, I wanted to check whether the
> > institutions running Sakai OAE in production are fine with this, as
> > there will be an increased likelihood of merge conflicts in areas
> > where custom code is present. The potential merge conflicts should be
> > fairly easy to resolve, but we still wanted to check first.
> >
> > Any objections?
> >
> > Thanks,
> > Nicolaas
> >
> >
> > -- 
> > Apisak "Michael" Darakananda
> > [email protected]
> > "The bus station is where the bus stops. The train station is where  
> > the train stops. On my desk, I have a workstation."
> 
> _______________________________________________
> oae-dev mailing list
> [email protected]
> http://collab.sakaiproject.org/mailman/listinfo/oae-dev

-- 
D. Stuart Freeman
Georgia Institute of Technology

Attachment: signature.asc
Description: Digital signature

_______________________________________________
oae-dev mailing list
[email protected]
http://collab.sakaiproject.org/mailman/listinfo/oae-dev

Reply via email to