# Quick

API documentation

## Overview

tbw

## Components

QuickWidgets
DesktopWindows
Dialogs
Hotlists

## Coding standards

Quick doesn't have a nazi code regime, but please consider the following basic guidelines:

- All new code needs to be documented. The minimum level of documentation for new code is
  - Short introduction in header files (what the code does and how the classes should be used)
  - Documentation of all functions/methods and non obvious member variables
- When working with existing code: If you invested some time in figuring out how code works, please document it.
- Limit the amount of ifdef _MYPLATFORM_. Ifdefs make code error prone and unreadable, try not always to go for the easy hack.
- Keep Quick Out Of Memomory safe
- Keep Quick quick: spend some time on optimization. Speed is the number 1 reason for users to use Opera

Last updated November 20, 2006