31 mouse buttons via kde's 'qt-copy': Difference between revisions
a draft or ideas for a project elegance template |
a template suggestion/idea |
||
| Line 1: | Line 1: | ||
(A [[Project Elegance]] Template. ) | (A [[Project Elegance]] Template. ) | ||
== Problem Statement == | == Problem Statement == | ||
''What is our code /user interface/ providing'' | ''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== | ==Affected Modules== | ||
'' Where is this used'' | ''Where is this used'' | ||
=== User Customization === | === User Customization === | ||
How will you let users customize behavior | How will you let users customize behavior | ||
==== global options ==== | ==== 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 ==== | ==== per instance options ==== | ||
when should a developer be able to force specific behavior | |||
=== Research === | === Research === | ||
==== Dependencies ==== | |||
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 ===== | ||
== | == Participants == | ||
''give your [[WikiSignature]] and your application | |||
Revision as of 04:14, 4 August 2010
(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
Research
Dependencies
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
Participants
give your WikiSignature and your application