MantisBT
Mantis Bug Tracker Workflow

View Revisions: Issue #28087 All Revisions ] Back to Issue ]
Summary 0028087: OCCT Samples Redesign
Revision 2016-11-11 10:13 by jma
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.
Revision 2016-11-11 10:01 by jma
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 samples functionality should be implemented in scope of Draw

The base ideas are described in the attached doc in the related sections.


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker