Source documentation/ru: Difference between revisions

From FreeCAD Documentation
(Updating to match new version of source page)
(Updating to match new version of source page)
 
(48 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<languages/>
FreeCAD source is commented to allow automatic html documentation generation with [http://www.doxygen.org Doxygen].


<div class="mw-translate-fuzzy">
For those wanting to follow closely the latest svn versions of FreeCAD, and who try to have a look at the c++ part, the first insight in the sources can give the feeling you're looking at an hedgehog: you can't discriminate head from tail and don't really know how to catch it!
{{Docnav/ru
|[[Extra python modules/ru|Дополнительные модули Python]]
|[[List of Commands/ru|Список комманд]]
}}
</div>


{{TOCright}}
In complement to the Wiki, ''source documentation'' can hopefully alleviate this feeling, providing an entry point, and allowing for easy browsing through the dozens of files and directories.


== Обзор ==
==== Build source documentation ====
Исходный код FreeCAD снабжен комментариями, что позволяет автоматически создавать документацию по программированию с использованием [[Doxygen/ru|Doxygen]], популярной системы документирования исходного кода. Doxygen может документировать написанные как на C ++, так на и Python части FreeCAD, в результате чего создаются HTML-страницы с гиперссылками на каждую задокументированную функцию и класс.


The documentation is hosted online at the [https://freecad.github.io/SourceDoc/ FreeCAD API website]. Please note that this documentation may not always be up to date; if you need more details, download FreeCAD's latest source code and compile the documentation yourself. If you have pressing questions about the code please ask in the developer section of the [https://forum.freecadweb.org/index.php FreeCAD forum].
If you have Doxygen installed, it's very easy to build the doc. Go to your FreeCAD build directory, configure your sources with CMake, issue
<syntaxhighlight>
make DevDoc
</syntaxhighlight>
and consult the resulting html files starting from Doc/SourceDocu/html/index.html
(note: the DevDoc target is not valid for autotools builds)


Compiling the API documentation follows the same general steps as compiling the FreeCAD executable, as indicated in the [[Compile_on_Linux|Compile on Linux]] page.
By nature, source doc is, and will ever be, work in progress. Don't hesitate to rebuild as often as needed. If you fall upon blatant inadequacies, feel free to post on the forum (note: It is really fully checked with cMake build process only).


[[File:FreeCAD_documentation_compilation_workflow.svg|800px]]
As an alternative, the doc is generated from time to time and accessible on sourceforge [http://free-cad.sf.net/SrcDocu/index.html here]


{{Caption|General workflow to compile FreeCAD's programming documentation. The Doxygen and Graphviz packages must be in the system, as well as the FreeCAD source code itself. CMake configures the system so that with a single make instruction the documentation for the the entire project is compiled into many HTML files with diagrams.}}
==== Integrate Coin3D documentation ====


== Сборка документации исходных кодов ==
On unix systems, it is possible to link Coin3D source documentation with FreeCAD's.
It allows easier navigation and complete inheritance diagrams for Coin derived classes.


=== Complete documentation ===
* On Debian and derived systems:
: - Install the package libcoin60-doc
: - Uncompress the file /usr/share/doc/libcoin60-doc/html/coin.tag.gz
: - Regenerate source documentation
: You are up for offline browsing.


Если у вас установлен Doxygen, то собрать документацию очень просто. Также установите [https://www.graphviz.org/ Graphviz], чтобы иметь возможность создавать диаграммы, показывающие отношения между различными классами и библиотеками в коде FreeCAD. Graphviz также используется FreeCAD [[Std_DependencyGraph | графом зависимостей]] для отображения взаимосвязей между различными объектами.
* If you don't want to or can't install Coin doc package, the links will be generated to access coin doc online at doc.coin3D.org, if doxygen tag file can be downloaded at configure time (wget).
{{Code|code=
sudo apt install doxygen graphviz
}}


Then follow the same steps you would do to compile FreeCAD, as described on the [[Compile_on_Linux|compile on Linux]] page, and summarized here for convenience.
{{docnav|Extra python modules|List of Commands}}
* Get the source code of FreeCAD and place it in its own directory {{incode|freecad-source}}.
* Create another directory {{incode|freecad-build}} in which you will compile FreeCAD and its documentation.
* Configure the sources with {{incode|cmake}}, making sure you indicate the source directory, and specify the required options for your build.
* Trigger the creation of the documentation using {{incode|make}}.
{{Code|code=
git clone https://github.com/FreeCAD/FreeCAD.git freecad-source
mkdir freecad-build
cd freecad-build
cmake -DBUILD_QT5=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 ../freecad-source
}}


While you are inside the build directory issue the following instruction to create only the documentation.
[[Category:Developer Documentation]]
{{Code|code=
make -j$(nproc --ignore=2) DevDoc
}}
Как упоминалось в [[Compiling (Speeding up)/ru|компиляция (ускорение)]], параметр {{incode|-j}} устанавливает количество ядер ЦП, используемых для компиляции. Полученные файлы документации появятся в каталоге
{{Code|code=
freecad-build/doc/SourceDocu/html/
}}

The point of entrance to the documentation is the {{incode|index.html}} file, which you can open with a web browser:
{{Code|code=
xdg-open freecad-build/doc/SourceDocu/html/index.html
}}

The {{incode|DevDoc}} target will generate a significant amount of data, around 5 GB of new files, particularly due to the diagrams created by Graphviz.

=== Reduced documentation ===

The complete documentation uses around 3Gb of disk space. An alternative, smaller version of the documentation which takes only around 600 MB can be generated with a different target. This is the version displayed on the [https://freecad.github.io/SourceDoc/ FreeCAD API website].
{{Code|code=
make -j$(nproc --ignore=2) WebDoc
}}

The documentation on the [https://freecad.github.io/SourceDoc/ FreeCAD API website] is produced automatically from https://github.com/FreeCAD/SourceDoc . Anyone can rebuild it and submit a pull request:

* Fork the repo at https://github.com/FreeCAD/SourceDoc
* on your machine: clone the FreeCAD code (if you haven't yet), create a build dir for the doc, and clone the above SourceDoc repo inside. That SourceDoc will be updated when you rebuild the doc, and you'll be able to commit & push the results afterwards:
{{Code|code=
git clone https://github.com/FreeCAD/FreeCAD
cd FreeCAD
mkdir build
cd build
mkdir -p doc/SourceDocu/html
cd doc/SourceDocu/html
git clone your-fork-url
cd ../../..
cmake -DBUILD_QT5=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 ..
make WebDoc
cd doc/SourceDocu/html
git commit
git push
}}
* Go to your fork online, and create a pull request.

<div class="mw-translate-fuzzy">
== Другие версии ==
[http://free-cad.sf.net/SrcDocu/index.html Документация FreeCAD 0.12], размещенная на Sourceforge.
</div>

== Объединение с документацией Coin3D ==

В системах UNIX возможно связать документацию исходников Coin3D с FreeCAD-овской. Это даёт упрощение навигации и завершение диаграммы наследования для классво, производных от Coin.

* Установите {{incode|libcoin-doc}}, {{incode|libcoin80-doc}} или аналогично названный пакет
* Распакуйте архив {{incode|coin.tar.gz}}, расположенный на {{incode|/usr/share/doc/libcoin-doc/html}}, файлы уже могут быть распакованы в Вашей системе.
* Повторите генерацию документации по исходным кодам.

* Если вы установили пакет документации Coin, ссылки будут сгенерированы для доступа онлайновой документации по адресу [https://coin3d.bitbucket.io/Coin/ BitBucket]. Это произойдет, если файл тега Doxygen можно загрузить во время настройки с помощью {{incode|wget}}.

== Using Doxygen ==

See the [[Doxygen|Doxygen]] page for an extensive explanation on how to comment C++ and Python source code so that it can be processed by Doxygen to automatically create the documentation.

Essentially, a comment block, starting with {{incode|/**}} or {{incode|///}} for C++, or {{incode|##}} for Python, needs to appear before every class or function definition, so that it is picked up by Doxygen. Many [[Doxygen#Doxygen markup|special commands]], which start with {{incode|\}} or {{incode|@}}, can be used to define parts of the code and format the output. [[Doxygen#Markdown support|Markdown syntax]] is also understood within the comment block, which makes it convenient to emphasize certain parts of the documentation.
{{Code|code=
/**
* Returns the name of the workbench object.
*/
std::string name() const;

/**
* Set the name to the workbench object.
*/
void setName(const std::string&);

/// remove the added TaskWatcher
void removeTaskWatcher(void);
}}


<div class="mw-translate-fuzzy">
{{Docnav/ru
|[[Extra python modules/ru|Дополнительные модули Python]]
|[[List of Commands/ru|Список комманд]]
}}
</div>

{{Userdocnavi{{#translation:}}}}
[[Category:Developer Documentation{{#translation:}}]]
{{clear}}
{{clear}}
<languages/>

Latest revision as of 21:51, 12 November 2021

Обзор

Исходный код FreeCAD снабжен комментариями, что позволяет автоматически создавать документацию по программированию с использованием Doxygen, популярной системы документирования исходного кода. Doxygen может документировать написанные как на C ++, так на и Python части FreeCAD, в результате чего создаются HTML-страницы с гиперссылками на каждую задокументированную функцию и класс.

The documentation is hosted online at the FreeCAD API website. Please note that this documentation may not always be up to date; if you need more details, download FreeCAD's latest source code and compile the documentation yourself. If you have pressing questions about the code please ask in the developer section of the FreeCAD forum.

Compiling the API documentation follows the same general steps as compiling the FreeCAD executable, as indicated in the Compile on Linux page.

General workflow to compile FreeCAD's programming documentation. The Doxygen and Graphviz packages must be in the system, as well as the FreeCAD source code itself. CMake configures the system so that with a single make instruction the documentation for the the entire project is compiled into many HTML files with diagrams.

Сборка документации исходных кодов

Complete documentation

Если у вас установлен Doxygen, то собрать документацию очень просто. Также установите Graphviz, чтобы иметь возможность создавать диаграммы, показывающие отношения между различными классами и библиотеками в коде FreeCAD. Graphviz также используется FreeCAD графом зависимостей для отображения взаимосвязей между различными объектами.

sudo apt install doxygen graphviz

Then follow the same steps you would do to compile FreeCAD, as described on the compile on Linux page, and summarized here for convenience.

  • Get the source code of FreeCAD and place it in its own directory freecad-source.
  • Create another directory freecad-build in which you will compile FreeCAD and its documentation.
  • Configure the sources with cmake, making sure you indicate the source directory, and specify the required options for your build.
  • Trigger the creation of the documentation using make.
git clone https://github.com/FreeCAD/FreeCAD.git freecad-source
mkdir freecad-build
cd freecad-build
cmake -DBUILD_QT5=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 ../freecad-source

While you are inside the build directory issue the following instruction to create only the documentation.

make -j$(nproc --ignore=2) DevDoc

Как упоминалось в компиляция (ускорение), параметр -j устанавливает количество ядер ЦП, используемых для компиляции. Полученные файлы документации появятся в каталоге

freecad-build/doc/SourceDocu/html/

The point of entrance to the documentation is the index.html file, which you can open with a web browser:

xdg-open freecad-build/doc/SourceDocu/html/index.html

The DevDoc target will generate a significant amount of data, around 5 GB of new files, particularly due to the diagrams created by Graphviz.

Reduced documentation

The complete documentation uses around 3Gb of disk space. An alternative, smaller version of the documentation which takes only around 600 MB can be generated with a different target. This is the version displayed on the FreeCAD API website.

make -j$(nproc --ignore=2) WebDoc

The documentation on the FreeCAD API website is produced automatically from https://github.com/FreeCAD/SourceDoc . Anyone can rebuild it and submit a pull request:

  • Fork the repo at https://github.com/FreeCAD/SourceDoc
  • on your machine: clone the FreeCAD code (if you haven't yet), create a build dir for the doc, and clone the above SourceDoc repo inside. That SourceDoc will be updated when you rebuild the doc, and you'll be able to commit & push the results afterwards:
git clone https://github.com/FreeCAD/FreeCAD
cd FreeCAD
mkdir build
cd build
mkdir -p doc/SourceDocu/html
cd doc/SourceDocu/html
git clone your-fork-url
cd ../../..
cmake -DBUILD_QT5=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 ..
make WebDoc
cd doc/SourceDocu/html
git commit
git push
  • Go to your fork online, and create a pull request.

Другие версии

Документация FreeCAD 0.12, размещенная на Sourceforge.

Объединение с документацией Coin3D

В системах UNIX возможно связать документацию исходников Coin3D с FreeCAD-овской. Это даёт упрощение навигации и завершение диаграммы наследования для классво, производных от Coin.

  • Установите libcoin-doc, libcoin80-doc или аналогично названный пакет
  • Распакуйте архив coin.tar.gz, расположенный на /usr/share/doc/libcoin-doc/html, файлы уже могут быть распакованы в Вашей системе.
  • Повторите генерацию документации по исходным кодам.
  • Если вы установили пакет документации Coin, ссылки будут сгенерированы для доступа онлайновой документации по адресу BitBucket. Это произойдет, если файл тега Doxygen можно загрузить во время настройки с помощью wget.

Using Doxygen

See the Doxygen page for an extensive explanation on how to comment C++ and Python source code so that it can be processed by Doxygen to automatically create the documentation.

Essentially, a comment block, starting with /** or /// for C++, or ## for Python, needs to appear before every class or function definition, so that it is picked up by Doxygen. Many special commands, which start with \ or @, can be used to define parts of the code and format the output. Markdown syntax is also understood within the comment block, which makes it convenient to emphasize certain parts of the documentation.

/**
 * Returns the name of the workbench object.
 */
std::string name() const;

/**
 * Set the name to the workbench object.
 */
void setName(const std::string&);

/// remove the added TaskWatcher
void removeTaskWatcher(void);