Difference between revisions of "31 mouse buttons via kde's 'qt-copy'"

Jump to: navigation, search
(create/polish template for project elegance)
Line 1: Line 1:
(A [[Project Elegance]] Template. )
+
This page provides a template for Project [[Elegance]] proposals.
  
 +
Parts marked with * are mandatory!
  
 +
= Summary* =
 +
Give a short intro to the problem/idea - 2 or 3 sentences.
  
== Problem Statement ==  
+
= Status* =
''What is our code /user interface/ providing''
+
The current status of this proposal and the date it was created.
  
Think of the problem you are trying to solve, and what interface and use scenarios are appropriate
+
= Drivers* =
 +
List people in charge of this proposal and ways to contact them. They will be the main point of contact from start to finish.
  
==Affected Modules==
+
= Detailed Description and Rationale* =
''Where is this used''
+
Describe in more detail what this proposal is about and why it should be implemented.
  
 +
= Affected Modules* =
 +
Which parts of KDE's software are affected? Which should definitely be part of the implementation process?
  
=== User Customization ===
+
= Research =
How will you let users customize behavior
+
pointers to research that backs up this proposal
  
==== global options ====
+
= Design =
Which options should be changed for all instances of this, regardless of program
+
details about the design ideas behind this proposal
  
==== per application options ====
+
= Implementation =
when should a program manage an option,
+
details about how this proposal should be implemented in code if needed
what should default behavior be, should an application turn something off, or turn it on.
 
  
==== per instance options ====
+
= Participants* =
when should a developer be able to force specific behavior
+
This part will list teams that work on implementing the proposal and ways to contact them.
  
 +
== Currently Implementing ==
 +
a list of teams currently implementing the proposal
  
=== Research  ===
+
== Finished Implementation ==
==== Dependencies ====
+
a list of teams that finished implementing this proposal
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 14:52, 29 August 2010

This page provides a template for Project Elegance proposals.

Parts marked with * are mandatory!

Summary*

Give a short intro to the problem/idea - 2 or 3 sentences.

Status*

The current status of this proposal and the date it was created.

Drivers*

List people in charge of this proposal and ways to contact them. They will be the main point of contact from start to finish.

Detailed Description and Rationale*

Describe in more detail what this proposal is about and why it should be implemented.

Affected Modules*

Which parts of KDE's software are affected? Which should definitely be part of the implementation process?

Research

pointers to research that backs up this proposal

Design

details about the design ideas behind this proposal

Implementation

details about how this proposal should be implemented in code if needed

Participants*

This part will list teams that work on implementing the proposal and ways to contact them.

Currently Implementing

a list of teams currently implementing the proposal

Finished Implementation

a list of teams that finished implementing this proposal


Content is available under Creative Commons License SA 4.0 unless otherwise noted.