forked from enlightenment/efl
8e3fa3a97f
In the EFL API we have several objects with the same name in different namespaces. Thus it is important to use fully-qualified names throughout the docs, to avoid confusion. However, the default DocFX templates prefer using only simple class names. The default templates have already been modified to use full names everywhere except in the list of derived classes in the hierarchy section, where a DocFX bug was hit. This commit is a workaround to that bug (see https://github.com/dotnet/docfx/issues/3769#issuecomment-485616064 ) so full names (with links) are used in the whole hierarchy. |
||
|---|---|---|
| .. | ||
| api | ||
| default_efl | ||
| .gitignore | ||
| README | ||
| docfx.json | ||
| e-logo-title.png | ||
| filterConfig.yml | ||
| gendoc.sh | ||
| index.md | ||
| setup.sh | ||
| toc.yml | ||
README
EFL DocFX SUPPORT ----------------- DocFX (https://dotnet.github.io/docfx/) generates documentation HTML pages directly from source code and Markdown files for C# projects. Although significantly slow, it is a simple alternative while our own documentation generator for C# is being written. The scripts in this folder create a documentation site which contains the API reference guide and articles with tutorials and guides. The API guide is generated from the EFL mono sources, which are generated as part of the normal build process. The articles are fetched from the EFL www-content repository and adapted to DocFX syntax. USAGE ----- First off, build EFL with C# support enabled so the C# sources are generated (you will need to have mono 5 installed for this). Then, from this folder, run the `setup.sh` script to download and extract the DocFX binaries to the `bin` folder, fetch the articles from the `www-content` repository and adapt them to the DocFX syntax. Finally, run the `gendoc.sh` script (also from this folder) to produce the HTML files. First run can take a long time (from 10' to 1h), subsequent runs use cached results and take about 5 minutes.