Project Elegance: Difference between revisions

From KDE Community Wiki
(start cleaning this up...)
Line 10: Line 10:
''Examples of libraries that are reused and provide robust features -- Look here before forking, move an item out of here if you are experimenting with a fork or reimplementation of this code, and put it back here when done''
''Examples of libraries that are reused and provide robust features -- Look here before forking, move an item out of here if you are experimenting with a fork or reimplementation of this code, and put it back here when done''


*[[PE/Notifications]]
*[[Elegance/Notifications]]


== Proposed Opportunities ==
== Proposed Opportunities ==
''These pages have some notes and ideas -- if in doubt add your item here''
''These pages have some notes and ideas -- if in doubt add your item here''


*[[PE/Tooltips]]
*[[Elegance/Tooltips]]
*[[PE/Icon Actions]]
*[[Elegance/Icon Actions]]
*[[PE/Calendar]]
*[[Elegance/Calendar]]
*[[Recent Documents]]
*[[Elegance/Recent Documents]]
*[[Install Missing Functionality]]
*[[Elegance/Install Missing Functionality]]
*[[Plasmoid Settings]] (it would be nice to have some settings be for all plasmoids, that are implemented in each one (like size, and wether it shows up as an icon, or widget)
*[[Elegance/Plasmoid Settings]]
*[[Messaging]] -- There is lot of talk about Kopete, Akondai Quassel, Konversation, kde rss reader, kmail, all providing similar functionality
*[[Elegance/Messaging]]


== Out of scope Opportunities ==
== Out of scope Opportunities ==
''A design decision has been made to duplicate functionality, or functionality has branched at lower level for overriding reasons''
''A design decision has been made to duplicate functionality, or functionality has branched at lower level for overriding reasons''


*[[PE/Plasmoid As XWindow]]
*[[Elegance/Plasmoid As XWindow]]
*[[PE/Panel and Desktop Activity]]
*[[Elegance/Panel and Desktop Activity]]




Line 36: Line 36:
  http://akademy.kde.org/sites/akademy.kde.org/files/video.png
  http://akademy.kde.org/sites/akademy.kde.org/files/video.png


== blah ==
== Template ==
A template for these projects
If you start a new proposal for Project Elegance please use the following template: [[Elegance/Template]]
[[PE/Template]]
 
Orchestrate or avoid individual enhancement forks, and provide consistent  operation and powerful functionality to all KDE programs.
KDE, qt, C++, and our Community.

Revision as of 14:14, 29 August 2010

Place for team collaboration, especially when reimplementing functionality or forking code from another project.

Targeted Opportunities

Senior KDE developers have placed emphasis on reaching goals for release.

Opportunities

List specific feature where code has been forked, or functionality has been duplicated

Mature Practices

Examples of libraries that are reused and provide robust features -- Look here before forking, move an item out of here if you are experimenting with a fork or reimplementation of this code, and put it back here when done

Proposed Opportunities

These pages have some notes and ideas -- if in doubt add your item here

Out of scope Opportunities

A design decision has been made to duplicate functionality, or functionality has branched at lower level for overriding reasons


References

Reaching for Greatness, Aaron Seigo, keynote 2010 Akademy  
http://dot.kde.org/2010/07/05/akademy-day-2
video.png

Template

If you start a new proposal for Project Elegance please use the following template: Elegance/Template