To solve this problem you can do 3 differnt things. You try to handle every possible coding pratice, which is almost impossible, since the language itself has a very open structure. You can tell your user to coding in a specific way, which can be quite anyoing if its isent your way. Finally you can forget all about analyzing the code and rely 100% on the javadoc tags.
I choose the last solution. This means that you have to add slightly more javadoc tags to your code. Actualy, you have to add tags thats not even javadoc tags.
Non javadoc tags
If your 'classes' is structured in some namespace alike hieracy, you add a namespace tag. You can also use it for simulation a folder or trre structure for you files.
Any function is a method.
A variable that is accesable through a object.
Although you dont define wich datatype your variable is, you usually expects that it is of a certain type. You use the curly brackets to tell the datatype of your, property, method parameter and return value.
>> How to do it - look at the example
The following javadoc tag are supported for 'classes'
The following javadoc tag are supported for methods
The following javadoc tag are supported for properties
Besides that it supports the generel description in the beginning of a javadoc comment.
Javadoc is not just for Ortelius
Javadoc is a general standard. So if you decide to use another documentation generating tool than Ortelius, you can switch right away.