[doc] Rewrite Mainpage

[erikbgithub]

Problem

The documentation still talks about Hidav's integration layer.

Solution

Rewrite the layer to tell readers about what MONK should help them with and a small example/tutorial, as well as a TOC.

Notes

• changes are tracked in f-docs-overhaul

[erikbgithub]

from Monday, Feb 11 2013:

1. Started with learning reST Syntax
2. created the first pages
3. Didn't push because installation isn't clear yet.
4. Try to get installation with requirements working

[erikbgithub]

Found that the installation problem should actually be part of the Getting Started Doc Page in issue #27. Further description there

[erikbgithub]

I totally forgot to describe things like the github page, the mailing list and the stammtisch until now. I am still thinking about putting it into the main page or the dev process (#28). Probably the result should be a very short description on the main page and the details on the dev page.

[erikbgithub]

Only consider the last 2 commits in review:

• aa8d98e updating conf.py
• d89f6f4 complete rewrite of index.rst

[DfePeterWinkler]

Figure 1 shows a simplification of that what really is planned and what is described above the picture. For a better illustration "Target System 1" till "Target System n" should be shown to be connected to the Development System or Test Server.

[DfePeterWinkler]

In chapter "What Using MONK Might Like Soon" a usage of MONK is described which is extremely differnt to that one which is corrently used. It is offered or planned to be compatible to the old version or it is expected that all already written test cases have to be changed to the new usage?

[DfePeterWinkler]

The way to work with log files in the prepare method seems not to be practicable for a lot of test cases. Most of the target devices have a wrapping mechanism to work with log files (dual-ring, quad-ring or date-time files). If in iteratively something is searched on such a device to detect any event on the target system the line to be found might be missed due to a file wrapping which happened betweeen two iterations. Furthermore there are test cases which needs a long time of iterating on log file due to the fact that the initiated process (e.g. a firmware update) takes a long time. That kind huge log files will be generated which are not usefull for later analysis of a detected error.