KTp/Tasks/Active: Difference between revisions

Latest revision as of 00:18, 27 September 2013

Plasma Active

Active client is maintained at https://projects.kde.org/projects/playground/network/telepathy/ktp-active

Getting Set Up

Hacking

It is still in playground so to some extent anything goes; anything that affects ktp-common-internals MUST go through the normal review process.

Anything in the declarative plugin should not be application specific.

TODO

Right now the only focus is on basic text chats.

Things essential for release:

* SASL Auth Handler
* 1-1 text chat.

Tasks

Web accounts

Check whether Plasma-Active is using Online Accounts. (done it is)
Pester afiestas into making the patches he promised to do in the auth handler. (done)
If so we can use the current auth handler (yay!)

Make contact list show last message received, and active conversations at the top

Update TextChannelWatcherProxyModel to keep last message
update ContactsFilterModel to allow sorting by HasChannel
update ContactsFilterModel to take a list of sort roles
then update the ContactsModel to show this

Show presence controls

Export GlobalPresence class to QML
Add a way to control this in the UI

Discuss name

Is it worth coming up with a new fancy name? We should look at what other active apps are called.

@@ Line 1: / Line 1: @@
 == Plasma Active ==
-At some point we should do something for plasma active.
-Mockup available here:
+Active client is maintained at https://projects.kde.org/projects/playground/network/telepathy/ktp-active
-== Tasks Done ==
+====Getting Set Up====
-* Make a declarative plugin that shows a contact list
+====Hacking====
-* Make a declarative plugin that has a message model
-== Tasks ==
+It is still in playground so to some extent anything goes; anything that affects ktp-common-internals MUST go through the normal review process.
-* Make a contact model that is also an approver/observer for unread message counts and stuff (also use this in our plasmoid (and even main CL)
+Anything in the declarative plugin should not be application specific.
-* Make a new plasma component for Text Chat that scales up nicely to a big screen.
+==TODO==
-* Make a sexy plasma app
+Right now the only focus is on basic text chats.
-* Expose video stuff to QML.
+Things essential for release:
+ * SASL Auth Handler
+ * 1-1 text chat.
-== Plasma Declarative Plugins structure==
+===Tasks===
-Eventually I want the following layout
+====Web accounts====
-org.kde.telepathy.core (core stuff: message model, contact list model, avatar imageprovider, accounts model, globalPresence)
+* Check whether Plasma-Active is using Online Accounts. (done it is)
+* Pester afiestas into making the patches he promised to do in the auth handler. (done)
+* If so we can use the current auth handler (yay!)
-org.kde.telepathy.contactlist (entry point for the contact list, very app specific)
+====Make contact list show last message received, and active conversations at the top====
+* Update TextChannelWatcherProxyModel to keep last message
+* update ContactsFilterModel to allow sorting by HasChannel
+* update ContactsFilterModel to take a list of sort roles
+* then update the ContactsModel to show this
-org.kde.telepathy.chatplasmoid (entry point for the chat plasmoid, very app specific i.e (conversations-model))
+====Show presence controls====
+* Export GlobalPresence class to QML
+* Add a way to control this in the UI
+====Discuss name====
+Is it worth coming up with a new fancy name?
+We should look at what other active apps are called.