- Introduction
- Main classes
- Obtaining & using
Diagnostics instances
- Obtaining & using Diagnosis instances
- Look-through Diagnosis
- Outro & todo list
|
Outro & todo list
Summing up - to make Diagnostics work properly you need to:
- import diagnostic packages
- Create at least one Diagnostics instance
- call beginWork() for one of instances
- mark some code blocks for analysis, remember about loopBlocks
- call endWork() for instance that you've been working with
- repeat 3, 4, 5 as long as you need.
- get Diagnosis instances from Diagnostics objects
- use setDocumentName() for Diagnosis instances you need to be saved
- use saveToFile() for Diagnosis instances you need to be saved, changing default options map for html instances you want
I hope as for now you have enough
knowledge about how Diagnostics works, that you can use it but
yourself. If anything is unclear, just try - it's always the best way
to learn.
If still there will be any troubles - try asking through SourceForge.
If I made any language mistakes - I apologize. I'm not native english speaker, I'm still learning.
TODO:
- Clean-up the code. Remove unused variables and
constants, move methods as high in inheritating hierarchy as possible,
put some locks and errors for situations of wrong use.
- Work on documentation. Add annotations and package-info's.
- Develop loop blocks further and introduce loop counters.
- Write last part of page 4
|