OpenCascade/occt
1
0
Fork 0
mirror of https://git.dev.opencascade.org/repos/occt.git synced 2025-08-04 13:13:25 +03:00
Code Activity

0028347: Reuse OCCT implementation for producing end-user documentation for Products

Browse Source 
Updated destination directory for generated by gendoc proc pdf files.

Added additional option "-update_images_size" for gendoc procedure to update width of images in *.md files during pdf generation for @figure alias.

Documentation was updated to use alias @figure instead of outdated @image

Added support of svg image format in procedure OCCDoc_UpdateImagesSize.

Added generation of overview for product components.

Added generation of products refman/chm for each component.
This commit is contained in:
apn
2017-03-30 12:13:19 +03:00
committed by bugmaster
parent b608f6a564
commit 7e3451c7a2
23 changed files with 494 additions and 503 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
dox/dev_guides/contribution_workflow/contribution_workflow.md
View File

@@ -35,8 +35,7 @@ According to his access level, the user can participate in the issue handling pr
@subsection occt_contribution_workflow_general General scheme
<center>
@image html OCCT_ContributionWorkflow_V3_image001.svg "Standard life cycle of an issue"
@image latex OCCT_ContributionWorkflow_V3_image001.svg "Standard life cycle of an issue"
@figure{OCCT_ContributionWorkflow_V3_image001.svg, "Standard life cycle of an issue"}
</center>
@subsection occt_contribution_workflow_issue Issue registration
@@ -281,8 +280,7 @@ Each change is integrated as a single commit without preserving the history of c
This is done to have the master branch history plain and clean.
The following picture illustrates the process:
@image html OCCT_ContributionWorkflow_V3_image002.png "Integration of several branches" width=\textwidth
@image latex OCCT_ContributionWorkflow_V3_image002.png "Integration of several branches" width=\textwidth
@figure{OCCT_ContributionWorkflow_V3_image002.png, "Integration of several branches"}
The new integration branch is tested against possible regressions that might appear due to interference between separate changes.
When the tests are OK, the integration branch is pushed as the new master to the official repository.