Archived issue #0028087
OCCT Samples Redesign
Description
There are 2 main ideas behind why OCCT samples must be redesigned:
1. They does not meet OCCT users needs
2. It is a constant OCCT team headache (crashes, broken compilation, obsolete func-s etc.)
There are 2 main steps proposed:
1. OCCT samples should be separated on OCCT feature programming samples and samples demonstrating how to bridge OCCT with GUI frameworks.
2. The feature programming samples functionality should be implemented in scope of Draw
The base ideas are described in the attached doc in the related sections.
1. They does not meet OCCT users needs
2. It is a constant OCCT team headache (crashes, broken compilation, obsolete func-s etc.)
There are 2 main steps proposed:
1. OCCT samples should be separated on OCCT feature programming samples and samples demonstrating how to bridge OCCT with GUI frameworks.
2. The feature programming samples functionality should be implemented in scope of Draw
The base ideas are described in the attached doc in the related sections.
Public activity
No public notes
Participants are labeled by their role within this record.
Related records
- #0028086 · related to · newImprove Usability of Draw
- #0031570 · related to · closedSamples - add Qt samples similar to standard MFC samples
- #0031518 · related to · closedSamples - update QtWidget samples to use AIS_ViewController
- #0031521 · related to · closedSamples - update MFC ImportExport sample to use AIS_ViewController
- #0031622 · related to · closedSamples - update MFC Animation sample with proper frame updates
- #0031732 · related to · closedDocumentation - move Tutorials and Samples into dedicated section