KTp/Tasks/ProperLibrary: Difference between revisions
Appearance
No edit summary |
No edit summary |
||
(7 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
This is a list of all the classes in KTp. | This is a list of all the classes in KTp library. I want everyone to hack on making it ready for public release. When you deem a component to be ready, message the ML where it will have a proper review. | ||
Each entry must be signed off by DrDanz or George K | Each entry must be signed off by DrDanz or George K | ||
Line 6: | Line 6: | ||
To count as ABI "safe" it must comply with http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++ | To count as ABI "safe" it must comply with http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++ | ||
Also check everything is namespaced, and the header guard is correct KTP_classname | |||
{| border="1" | {| border="1" | ||
!Class !! ABI safe !! Documentation !! Tests !! Notes | !Class !! ABI safe !! Documentation !! Tests !! Notes | ||
|- | |- | ||
|circular-countdown || || || || | |circular-countdown || || || || Not KTp related, we should move it | ||
|- | |- | ||
|debug || || || || | |debug || || || || | ||
Line 30: | Line 32: | ||
|service-availability-checker || || || || | |service-availability-checker || || || || | ||
|- | |- | ||
| | |telepathy-handler-application || || || || Needs major re-writing, see Later | ||
|- | |- | ||
|text-parser || || || || | |text-parser || || || || | ||
|- | |- | ||
|wallet-interface || || || || | |wallet-interface || || || || | ||
Line 54: | Line 54: | ||
|contact-grid-widget || || || || | |contact-grid-widget || || || || | ||
|- | |- | ||
|join- | |join-chat-room-dialog || || || || | ||
|- | |- | ||
|notificationconfigdialog || || || || | |notificationconfigdialog || || || || | ||
|} | |} | ||
== TelepathyHandlerApplication == | |||
* Needs Renaming to KTp::HandlerApplication or to KTp::Application | |||
* Should have a method to retrieve the account manager() | |||
* We should have a KTp::Applet class for plasma widgets that shares part of the API with KTp::Application | |||
* We should investigate again if we can use KUniqueApplication instead of KApplication as a base class, otherwise check if we can set "bool s_kuniqueapplication_startCalled" = true somehow so that we can register a well known name instead of a generated name | |||
* I think that kappliation has some api that can replace newJob and jobFinished, we should find out what is that and replace these methods |
Latest revision as of 14:45, 21 January 2013
This is a list of all the classes in KTp library. I want everyone to hack on making it ready for public release. When you deem a component to be ready, message the ML where it will have a proper review.
Each entry must be signed off by DrDanz or George K
(note that model classes that are due to be replaced are not listed here)
To count as ABI "safe" it must comply with http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++
Also check everything is namespaced, and the header guard is correct KTP_classname
Class | ABI safe | Documentation | Tests | Notes |
---|---|---|---|---|
circular-countdown | Not KTp related, we should move it | |||
debug | ||||
error-dictionary | ||||
global-contact-manager | ||||
global-presence | ||||
ktp-export | ||||
logs-importer | ||||
pending-wallet | ||||
presence | ||||
service-availability-checker | ||||
telepathy-handler-application | Needs major re-writing, see Later | |||
text-parser | ||||
wallet-interface | ||||
wallet-utils | ||||
accounts-filter-model | Needs Rename | |||
accounts-list-model | ||||
rooms-model | ||||
accounts-combo-box | ||||
add-contact-dialog | ||||
contact-grid-dialog | ||||
contact-grid-widget | ||||
join-chat-room-dialog | ||||
notificationconfigdialog |
TelepathyHandlerApplication
- Needs Renaming to KTp::HandlerApplication or to KTp::Application
- Should have a method to retrieve the account manager()
- We should have a KTp::Applet class for plasma widgets that shares part of the API with KTp::Application
- We should investigate again if we can use KUniqueApplication instead of KApplication as a base class, otherwise check if we can set "bool s_kuniqueapplication_startCalled" = true somehow so that we can register a well known name instead of a generated name
- I think that kappliation has some api that can replace newJob and jobFinished, we should find out what is that and replace these methods