AIM client written in Qt - Historical code, do not use or reference, it is bad
C++ Shell C Python Perl
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Kinkatta is an instant messenger for AOL. Kinkatta is released under the GPL and LGPL license. Kinkatta's uses the QT and KDE libraries. There is a QT branch for those that wish to only use QT. 

<h3>What are the goals?</h3><p>&nbsp;&nbsp;&nbsp;&nbsp;Kinkatta's top priority (the reason it was started) was to be a chat client and nothing more.  There are a number of chat clients out there that allow you to do everything under the sun in there client, but are still lacking in some basic "chat" features.  The only real thing you use the clients for is to chat.  For the beginning we have followed this goal by spending almost a month developing the chatwindow outside of the client's environment.  Each area has been thought out, decided upon and then implemented. (with the occasional additions that were forgotten).  This leads to each area being fully developed and fully tested at the same time, rather then doing a little from one area and a little from another and back to the first.  After using sub 1.0 software for a long time Kinkatta will release a 1.0 version that will incorporate all chat features that are needed, fully tested.  Post 1.0 will have other wanted feature, all of which are not core chat related.  Kinkatta also takes a heavy look at the ui side of things.  Every little things is looked at and asked, "How can this be better understood by the user?"  The options dialog for example is clearly laid out and has icon representations of each category.  Another example would be in the main window how you can edit the user name (and alias) directly within the window.  Little things like this were put into Kinkatta because they can and should be there.

<h3>What is Kinkatta's history?</h3><p>&nbsp;&nbsp;&nbsp;&nbsp;In fall of  1999 I was using Gaim as my primary client.  The only problem was the the client at that point was in a very sad state.  The UI had too many issues to count, the icons looked like they were made with paint and so forth.  The development tree wasn't being worked on and all of these annoying things were getting to be too much.  I started to look through the source, but found it lacking of all but a tiny few comments.  (As of the latest release a lot of those issues have been resolved and the ones that haven't been I hear they are working on.) I kept finding so many things wrong with Gaim that I though hey why not just write one myself.
<p>&nbsp;&nbsp;&nbsp;&nbsp;That fall I also wrote an app called megadrink.  In the app learned how to use network and the QT widget set.  I didn't actually start Kinkatta until about February of 2000.  A lot of time was spent on most of the graphics that are used in Kinkatta.  I found several other people who had started (and stopped) an app called kaim, it was just the basics, but it gave me the ambition to start my project.  Taking there code I started planning out how I would make my application.  Unfortunately the original Kinkatta's code wasn't any good.  All of it had to be re-written which was done.  One of the original guys (Dimi) from the other team joined me in my endeavor and is still here to this day.  About that time I got in touch with Neil of Kit.  We worked together a bunch and I ended up putting Kit's network code into Kinkatta.  The two aren't the same now, but they are both from the same thing. April 25 2000 Kinkatta .25 was released and put on sourceforge.  It no longer runs because of a network issue, but it is cool to look at :).  In June of 2001 AOL sent a notice of infringment to the Kinkatta telling them that they had to change their name.  Up until this point the name of the application was Kaim, but sense then it has been changed to Kinkatta.
<h3>What Now?</h3><p>&nbsp;&nbsp;&nbsp;&nbsp;I have gotten Kinaktta to a stable state and so I really haven't worked on this project very much at all sense then.  One day I might upgrade it to use newer KDE features.  We shale see.  For those who want to hack on it check out the code which is much farther beyond what is presented in 1.01.