Thursday, January 10. 2008KMess 1.5 released!Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
Congrats, I use to update from svn weekly and you are doing a great work. I can't wait to have the qt4 interface
Thanks
Do you plan to integrate it/share some code with a more generic framework (I am thinking of Tapioca/Telephaty) ? Otherwise it seems a duplication of efforts (and another icon in the taskbar
> Do you plan to integrate it/share some code with a more generic framework (I am thinking of Tapioca/Telephaty) ?
Yes, we do want to look at this. I can't promise if it will actually work out for us. We constantly push for new MSN features (iirc there are "msn extensions" in Telepathy), so we'll have to find a way to make that work with Telepathy as well. One other option I've been thinking about it keeping KMess linked to it's own protocol code, and release a telepathy connection manager separately. > Otherwise it seems a duplication of efforts > (and another icon in the taskbar It doesn't yet feel like this at all. Sometimes you need an alternative route to get things done faster. If KMess gives developers the necessairy environment / breeding ground to work on the MSN protocol faster - e.g. compared to a project where developers are limited by certain constraints like project vision, user interface rules or architecture - everyone benefits. You can analyse our progress in the source and commit logs after all. If we were far behind that would be a different story, but I don't think that's the case here.
Sounds nice!
Can I use this in Kopete so I can see the msn goodies in the same interface as my Jabber/ICQ goodies?
No, sorry. KMess is purely MSN client with it's own protocol code. My mid-term plans are migrating to a more library-based architecture or even telepathy. Also because I feel more for leveraging a library from a tested application (which has users, feature requests and bug reports) then visa versa.
The reason I simply didn't start on this yet is because.. we needed a stable release first. For the time being we'll have fun again implementing new stuff (compared to bugfixing) and slowly clear the way to work on mid-term goals. So far this is only vision, but I want to see how we can make that a win-win situation. Nobody bennefits if we loose momentum by shooting ourselves in the foot.
I'd love to see such a library indeed, so I don't have to run different apps for IMing.
Again congrats on the release; and I hope you have lots of fun coding Qt4/KDE4 soon
No offense, but it saddens me a bit to see so much work go into a single-protocol app when Kopete exists. If you applied to Kopete all the effort that's gone into KMess's own MSN support, Kopete would be even better, and the fruit of the effort would be much more useful. What's the point of a single-protocol app nowadays? And what's the point of KMess when we have Kopete?
I'm not knocking your work; you're free to work on whatever you want. But I just don't understand it, and I groan at yet another reinvention of the wheel.
> If you applied to Kopete all the effort that's gone into KMess's own MSN support,
> Kopete would be even better, and the fruit of the effort would be much more useful. Back in 2003 I actually filed some Kopete bugs because I wanted Kopete to improve. From a "msn messenger" point of view it was hard to figure out who you're actually chatting with, and what your online status was. I figured some bug reports could fix that, but this resulted in long discussions about whether a ~48 pixel sidebar would take too much space, and a 4x4 pixel indicator (on a 16x16 image) was good enough to see your status. That turned me off and I fell in love with KMess because it had exactly what I was looking for. > What's the point of a single-protocol app nowadays? I use MSN only so I want an application that does this the best for me. I want specialized features, no compromises because of other protocols. All-in-one applications are not always the solution here (think Dolphin vs Konqueror). > And what's the point of KMess when we have Kopete? Have a breeding ground where people can implement MSN support because they're totally free to do so. So in the end, my work could still benefit Kopete. KMess allowed me to unravel the MSN protocol faster. The code is there. Our mid-term plans include trying to make a library from our protocol code, and look at Decibel if possible.
Cool, thanks for the explanation.
|
QuicksearchArchivesCategoriesLinksPowered by |