Design Objectives
The design objectives for Qvc are:
- Provide a consistent, stable and documented API.
- Should be able to allow contribution by multiple distributed developers.
- Must be able to grow, that is add new components, without losing clarity and quality.
- Allow for continuous improvement and exploitation of new QV features. QVC is not meant to cover all scripting tasks and scenarios. QVC is targeted at the “middle range” of scripting tasks.
At the bottom of the complexity stack are trivial simple tasks such as file loading. These tasks would not benefit enough from QVC to justify using library routines. To support tasks at the high end would require increasing complexity in QVC, possibly diminishing its quality and maintainability.