 |
Studies of software maintainers have shown that approximately 50% of their time
is spent in the process of understanding the code that they are to maintain.*
 |
In other words: Software developers spend 50% of their time by reading and looking at
the source code!
|
A clear formatted and documented source code can help to reduce this task a lot.
For that reason we have developed Jindent.
Please read 'Benefits of Jindent' to get to know all advantages of Jindent.
*Fjeldstad, R. & Hamlen, W. (1983). "Application program maintenance-report to to our respondents".
Tutorial on Software Maintenance, 13-27. Parikh, G. & Zvegintzov, N. (Eds.). IEEE Computer Soc. Press.
|
|
|
Jindent is a great support in multiple areas of software development:
- Following your corporate code convention.
- Transforming foreign code to your coding style.
- Sell your source code and apply to your customers code convention.
- Formatting source code for presentations, articles, web publishing or books.
- Easy to use programmer's API for automatic code generation process.
You simply generate your Java tokens, Jindent cares about its formatting.
- Automatic generation and checking of Javadoc templates and tags.
- Template supported comment generation for code headers and footers. Write one template - use it for different projects.
- Customizable templates through self defined text variables.
- More efficient use of diff-tools.
Reformat both sources with Jindent and your diff-tool reports only the actual code differences.
- Use Jindent in combination with version control systems: only real code differences will be checked in.
- Finding bugs easier by indenting correct scope levels and by inserting new braces, brackets on places programmers may forget them.
- Gets rid of tabulator incompatibilities.
- Don't waste time by formatting code by hand!
|
|
|
