KTp/Components/Accounts KCM Hack Day: Difference between revisions
m (→About) |
m (Drdanz moved page Real-Time Communication and Collaboration/Components/Accounts KCM Hack Day to KTp/Components/Accounts KCM Hack Day: As discussed at IRC meeting Real-Time_Communication_and_Collaboration is too long, we are moving all our pages...) |
||
| (16 intermediate revisions by 4 users not shown) | |||
| Line 4: | Line 4: | ||
Just shout out in #kde-telepathy that you want to help, and we'll see what tasks suit you best. | Just shout out in #kde-telepathy that you want to help, and we'll see what tasks suit you best. | ||
poke d_ed or david_edmundson on IRC for me. I'll be there hopefully 10am GMT onwards. | |||
== Current State of KDE Telepathy == | |||
KDE Telepathy is made up of a lot of components, each of these are at different states of completeness. | |||
Recently there was a large API change between Telepathy Qt0.4 and 0.5, some of these components compile against 0.4, some 0.5. Some parts are nearly done, some need a lot of work. | |||
Everything we need today requires Tp-Qt0.5. For more information see | |||
http://community.kde.org/Real-Time_Communication_and_Collaboration/Current_State | |||
== Who's helping == | == Who's helping == | ||
| Line 9: | Line 20: | ||
If you want to help out, put your name on this list and tell us what you're main skills are: | If you want to help out, put your name on this list and tell us what you're main skills are: | ||
David Edmundson: Knows C++/Qt/Telepathy-Qt4 quite well. | * David Edmundson: Knows C++/Qt/Telepathy-Qt4 quite well. | ||
* Jeffery MacEachern: Knows C++/Qt, learning KDE API. | |||
* Some guy called INIT64 from Reddit - basic C/C++ | |||
* Lasse Liehu: C++/Qt | |||
== Getting Setup == | == Getting Setup == | ||
| Line 16: | Line 30: | ||
=== Prerequisites === | |||
Make sure you have telepathy installed, packages from your distribution should be fine. You'll also need the standard development for any KDE work, kdelibs-dev, a compiler, GCC, qt-designer, git. | |||
You will also need a copy of telepathy installed. Anything provided by your distro should be fine. | |||
Personally I like using qtcreator for my editing but you can choose what you like. | |||
=== Telepathy-Qt4 === | |||
You need to have telepathy Qt-4 > 0.5 installed. It is unlikely your distribution is this up to date. | |||
Download the tarball here: | |||
<code> | |||
wget http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.5.0.tar.gz | |||
tar xfvz telepathy-qt4-0.5.0.tar.gz | |||
cd telepathy-qt4-0.5.0 | |||
mkdir build | |||
cd build | |||
cmake .. -DCMAKE_INSTALL_PREFIX=/usr | |||
make | |||
sudo make install | |||
</code> | |||
There are later versions of Tp-Qt4 however these require a newer version of telepathy than shipped with Ubuntu (and probably other distributions). If you can compile it that's great, if not otherwise 0.5 is fine. | |||
=== KCM Accounts === | |||
We need the very latest versions of the account manager so we have to fetch it from our git repository | |||
<code> | |||
git clone git://anongit.kde.org/telepathy-accounts-kcm | |||
cd telepathy-accounts-kcm | |||
mkdir build | |||
cd build | |||
cmake .. -DCMAKE_INSTALL_PREFIX=/usr | |||
make | |||
sudo make install | |||
</code> | |||
=== KCM Account Plugins === | |||
<code> | |||
git clone git://anongit.kde.org/telepathy-accounts-kcm-plugins | |||
cd telepathy-accounts-kcm-plugins | |||
mkdir build | |||
cd build | |||
cmake .. -DCMAKE_INSTALL_PREFIX=/usr | |||
make | |||
sudo make install | |||
</code> | |||
== Anything Else == | |||
The KDE Telepathy stack is obviously a lot more than just an account configuration page, however a lot is unfinished so I'd like to stay focussed on just one area today. | |||
To get setup with the rest of KDE Telepathy please see: | To get setup with the rest of KDE Telepathy please see: | ||
http://http://community.kde.org/Real-Time_Communication_and_Collaboration/Getting_Set_Up | http://http://community.kde.org/Real-Time_Communication_and_Collaboration/Getting_Set_Up | ||
== Tasks == | == Tasks == | ||
A list of tasks are available here: | A list of tasks are available here: | ||
http://community.kde.org/index.php?title=Real-Time_Communication_and_Collaboration/Components/Accounts_KCM_Tasks | |||
== Testing == | == Testing == | ||
Latest revision as of 00:31, 10 November 2012
About
The goal of today is to try and do as much crazy hacking on the Accounts setup in KDE Telepathy in a day. There are lots of other areas in KDE telepathy, but today is ideally going to be centralised on one thing in order to be more productive.
Just shout out in #kde-telepathy that you want to help, and we'll see what tasks suit you best.
poke d_ed or david_edmundson on IRC for me. I'll be there hopefully 10am GMT onwards.
Current State of KDE Telepathy
KDE Telepathy is made up of a lot of components, each of these are at different states of completeness.
Recently there was a large API change between Telepathy Qt0.4 and 0.5, some of these components compile against 0.4, some 0.5. Some parts are nearly done, some need a lot of work.
Everything we need today requires Tp-Qt0.5. For more information see http://community.kde.org/Real-Time_Communication_and_Collaboration/Current_State
Who's helping
If you want to help out, put your name on this list and tell us what you're main skills are:
- David Edmundson: Knows C++/Qt/Telepathy-Qt4 quite well.
- Jeffery MacEachern: Knows C++/Qt, learning KDE API.
- Some guy called INIT64 from Reddit - basic C/C++
- Lasse Liehu: C++/Qt
Getting Setup
The following will get you set up enough in order to hack on just the system settings part of KDE telepathy:
Prerequisites
Make sure you have telepathy installed, packages from your distribution should be fine. You'll also need the standard development for any KDE work, kdelibs-dev, a compiler, GCC, qt-designer, git.
You will also need a copy of telepathy installed. Anything provided by your distro should be fine.
Personally I like using qtcreator for my editing but you can choose what you like.
Telepathy-Qt4
You need to have telepathy Qt-4 > 0.5 installed. It is unlikely your distribution is this up to date.
Download the tarball here:
wget http://telepathy.freedesktop.org/releases/telepathy-qt4/telepathy-qt4-0.5.0.tar.gz
tar xfvz telepathy-qt4-0.5.0.tar.gz
cd telepathy-qt4-0.5.0
mkdir build
cd build
cmake .. -DCMAKE_INSTALL_PREFIX=/usr
make
sudo make install
There are later versions of Tp-Qt4 however these require a newer version of telepathy than shipped with Ubuntu (and probably other distributions). If you can compile it that's great, if not otherwise 0.5 is fine.
KCM Accounts
We need the very latest versions of the account manager so we have to fetch it from our git repository
git clone git://anongit.kde.org/telepathy-accounts-kcm
cd telepathy-accounts-kcm
mkdir build
cd build
cmake .. -DCMAKE_INSTALL_PREFIX=/usr
make
sudo make install
KCM Account Plugins
git clone git://anongit.kde.org/telepathy-accounts-kcm-plugins
cd telepathy-accounts-kcm-plugins
mkdir build
cd build
cmake .. -DCMAKE_INSTALL_PREFIX=/usr
make
sudo make install
Anything Else
The KDE Telepathy stack is obviously a lot more than just an account configuration page, however a lot is unfinished so I'd like to stay focussed on just one area today.
To get setup with the rest of KDE Telepathy please see:
http://http://community.kde.org/Real-Time_Communication_and_Collaboration/Getting_Set_Up
Tasks
A list of tasks are available here: http://community.kde.org/index.php?title=Real-Time_Communication_and_Collaboration/Components/Accounts_KCM_Tasks
Testing
launch with "kcmshell4 kcm_telepathy_accounts" this will show you all the debug output as it runs.
One of the easiest ways to verify it all worked ok is simply to install empathy (the gnome IM client) all accounts created in the KDE telepathy setup should appear and work here.
If you have succesfully tested configuring an account and had it logged in successfully, please record that here.
Alternatives
Install the plasma applet + dataengine listed in the Getting Setup link. Note we don't have a working contact list right now, so it's going to be hard to really test anything.