31 mouse buttons via kde's 'qt-copy'

(A Project Elegance Template. )

Problem Statement

What is our code /user interface/ providing

Think of the problem you are trying to solve, and what interface and use scenarios are appropriate

Affected Modules

Where is this used

User Customization

How will you let users customize behavior

global options

Which options should be changed for all instances of this, regardless of program

per application options

when should a program manage an option, what should default behavior be, should an application turn something off, or turn it on.

per instance options

when should a developer be able to force specific behavior



When adding features, can you do so without increasing dependancies? can you use a macro to turn off functionality if a dependancy is net met?

Case studies

Feature rich
Sparsity needed


give your WikiSignature and your application

This page was last edited on 9 March 2016, at 09:17. Content is available under Creative Commons License SA 4.0 unless otherwise noted.