Skip to content
Snippets Groups Projects
Commit ac68d8f8 authored by Stefan E. Funk's avatar Stefan E. Funk
Browse files

added google java eclipse style format.

parent 5b6417d5
No related branches found
No related tags found
No related merge requests found
......@@ -9,30 +9,20 @@ author:
# Purpose
This guideline should help you getting started a new software
development project (or improving an existing one!) in the Research and
Development Department of the Göttingen State and University Library.\
Our goal is to establish better software quality by following standards
the developer team has mutually agreed upon. Roughly basing on the
[DARIAH Technical
Reference](https://dariah-eric.github.io/technical-reference/), these
standards are discussed, worked out, and decided in the Software Quality
Working Group, which meets biweekly on Tuesdays at 12:30-13:30. However,
they aren't cast in stone, so in case you have a good idea for a better
standard, feel free to contribute!
This guideline should help you getting started a new software development project (or improving an existing one!) in the Research and Development Department of the Göttingen State and University Library.
Our goal is to establish better software quality by following standards the developer team has mutually agreed upon. Roughly basing on the [DARIAH Technical Reference](https://dariah-eric.github.io/technical-reference/), these standards are discussed, worked out, and decided in the Software Quality Working Group, which meets biweekly on Tuesdays at 12:30-13:30. However, they aren't cast in stone, so in case you have a good idea for a better standard, feel free to contribute!
# Status
This document is a living document and will be extended as soon as the
Software Quality Working Group has agreed upon a new standard for
software projects in RDD.
This document is a living document and will be extended as soon as the Software Quality Working Group has agreed upon a new standard for software projects in RDD.
# Guidelines
## Do you stick to our style guides?
## Do you stick to our code style guides?
### General
......@@ -47,24 +37,21 @@ you can set 2 space indentation as default by editing `/db/apps/eXide/src/prefer
### Specific for programming languagues
For the more prominent programming languages we have formatting and general style guides we ask you to follow:
For the more prominent programming languages we have formatting and
general style guides we ask you to follow:
- **Java**: The Java style guide can be found [here](./styles/rdd-eclipse-java-google-style.xml). It's based on the [Google style guide for Java](https://github.com/google/styleguide) with some minor RDD specific setting. You can configure Eclipse to use it automatically at *Eclipse > Preferences > Java > Code Style > Formatter*. Just load the RDD Eclipse Java Google Style in the formatter preferences and use it in your RDD projects.
- **Java**: The style guide can be found
[here](https://wiki.de.dariah.eu/download/attachments/64951939/FEGoogleStyle.xml?version=2&modificationDate=1522158497617&api=v2).
It's based on the Google style guide for Java with some RDD specific
setting. You can configure Eclipse to use it automatically at
Eclipse > Preferences > Java > Code Style > Formatter.
- **JavaScript**: For JS we use the [Airbnb JavaScript Style
Guide](https://github.com/airbnb/javascript). @TODO: How to use in
editor?
- **HTML/CSS**: For HTML/CSS we agreed upon the [Google HTML/CSS Style
Guide](https://google.github.io/styleguide/htmlcssguide.html). .
@TODO: How to use in editor?
- **XQuery**: We use the [xqdoc style guide](http://xqdoc.org/xquery-style.pdf) with the following addenda:
- use double quotes instead of single quotes
- **XSLT**: @TODO
- **SPARQL**: @TODO
- **SPARQL**: @TODO
This diff is collapsed.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment