[jira] Commented: (SHINDIG-76) Defining IDE conf files

["Kevin Brown (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SHINDIG-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569732#action_12569732 ] 

Kevin Brown commented on SHINDIG-76:
------------------------------------

Style is still inconsistent at this point, because we haven't yet published a style guide. Once we get a style guide published (and sorted out the debates that are sure to follow on shindig-dev), we'll update all the source for consistency.

Right now it's more or less:

- Java: Sun style rules, but with 2 space indents
- javascript: similar to Java; 

camelCased local and closure variable names and public members

trailingUnderscore_ public members that are meant to be treated as private

LeadingCaps constructors and "enums"

ALL_CAPS "constants"

prototype style objects for things with constructors

closure style for singletons / packages

> Defining IDE conf files
> -----------------------
>
>                 Key: SHINDIG-76
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-76
>             Project: Shindig
>          Issue Type: Task
>            Reporter: Vincent Siveton
>            Assignee: Brian McCallister
>         Attachments: shindig-eclipse-codestyle.xml, shindig-eclipse-codetemplate.xml
>
>
> Shindig needs to have IDE conf files, like codestyle or code template.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.