Powered By:
Clearspace
BlatherSource: Because development won't keep quiet

Daniel Henninger's BlatherBlog

5 Posts tagged with the client tag
0

Well I'll tell ya...  Daniel has been busy with a side project that he is not going into here just yet.  I apologize for the lack of work on PyICQt and PyAIMt lately, but don't worry, I'll be back to them at some point.  =)

 

Adium X is looking better and better with every beta release.  Great job guys!  It remains my primary chat client.  Spark, on the other hand, has become my "I don't want to be bothered" client.  ;D  (since it only logs into one place and overall I really like the interface)  Psi by far remains my favorite dev/test client.  Some would argue with me, but if I were to call anything the definitive/most extensive implementation of a Jabber client, it would be Psi.  (especially the dev tree)

 

I've been busy with a lot of personal/home projects as well lately.  So much to do.  =)  Just wanted to assure people that I am not ignoring my other projects.  ;D  They're just on a short break!

0 Comments 0 References Permalink
4

Spark 2.0.0beta

 

Very pretty, works well, still has some mild issues connecting from Mac OS X.  Has sort of become my client of choice at home because Adium X has been very very slow for me lately.  Not sure why.

 

Things I wish it had:

- Better disco interface.  (I was working on one at one point but got sidetracked)

- Ability to register with/interact with components (see previous as it's related)

- Integration with apple address book for names and meta-contacts

- Meta contacts  ;D

- Apple-W to close a chat tab/window.

- More intelligent Growl support.  (right now it gives you a growl notification for every message, whereas other clients tend to only give you notifications on conversations that you are not currently looking at)

 

 

Adium X 1.0b1

 

My typical client of choice because I adore it's look and feel.  This version has so many things done under the surface that I like, but I won't go into them.  On the surface, the interface looks a tad cleaner and it supports Jabber icons now!!! WOOOO!  Unfortunately, it's rather crashy at the moment, but it's beta.  =)  I've been sending off the reports that come from the reporter tool, but I really don't have anything useful to add to the reports as I'm not sure what's causing the crashes.

 

Things I wish it had:

- Better Jabber support.  (things like disco, in-band registration, etc)

 

 

Psi (private build from SVN tree)

 

Psi continues and will likely always be my chosen test client.  I believe it supports many things well and is typically the best to test transport changes with (IMO).  Likewise, those guys are going plum crazy with features lately!  =)  Color me very impressed.

 

Things I wish it had:

- Integration with Apple address book for meta contacts and names.

- Meta-contacts.  ;D  (this is on the roadmap)

 

 

 

Other Stuff

 

On an unrelated note, this will cause my other posts to actually come through to Planet Jabber.  (I had two pending.... I think serendipity's Atom feed support is not very good, and RSS 2.0 support seems to be good, so I've asked that my feed at planet jabber be switched to RSS 2.0)

 

Also, due to a project I'm working on that I don't really want to discuss in my blog right now, the python transports and jwgc are in a sort of statis for a little bit.  Shouldn't be long, but just in case you were wondering why there hasn't been more development or a release lately.

 

Also note that I need to do a few improvements to BlatherCore (see www.blathersource.org) to deal with spam (sigh) and also integrate a couple of other interesting features.  Likewise, need to knock out ScriptRepo and get that bad boy up and running for people to use.  Need to silence the back and forth conversation in my head about how to deal with the various projects and "just do something", you know?  I like the way the interface came out, so hopefully that will encourage me to get it done sooner rather than later.

4 Comments 0 References Permalink
6

Coccinella and Spark

Posted by Daniel Henninger Apr 10, 2006

Just generally playing around with some clients, I rather dig Coccinella and Spark.

 

Spark is very cute and has a fairly nice interface.  It's "missing" some functionality here and there, but it's very young and has a nice plugin architecture that I was playing around with.  The login screen is a little on the ugly side, but then how often are you going to be looking at the login screen?  My only problem with it so far has been that it doesn't seem to like to log into my home servers for some reason.  Still trying to work that issue out.  I like how Coccinella has it's disco browser under a tab and, using plugins, I can do that with Spark to.  (ie, if I write that functionality)  Which is one thing I was working in for fun over the weekend.

 

Coccinella seems very feature right and has a wonderfully fun Whiteboard functionality.  It's also a very cute look and feel and it's Tcl/Tk-ness makes it very cross platform functional.  It's possible that the only reason I would -not- switch to this as my primary jabber client is that it doesn't 100% behave under OS X.  For example, periodically I have some major issues dealing with it's scrollbars.  Like they won't "pull" for me.  I have to click on parts of the scrollbar to get to where I need to go.  Likewise, it doesn't really keep a feel for it's last window positioning that I can see, so every time I start it up I have to pull the windows into the locations I want them in.  That one's not all that big a deal, but still.  Anyway, it's really quite nice.  =)

6 Comments 0 References Permalink
2

I have come to the conclusion that something I need to consider doing is writing a very quick and very dirty jabber client.  JWGC is not that client.  JWGC is a little complex and what I'm looking for is something . . . written in a scripting type of language that I know well (python? perl?) . . . that doesn't necessarily need to have a pretty user interface.  The goal here is..  as I'm working on new features for the python transports, I need to not be sitting here going "man, I wish I had a client that supported X feature so I could test it".  Hell with that, why don't I just write one that I can quickly and easily modify on the fly?  There's plenty of good libraries and such out there.  On the python front there's xmpppy which I have already coded one little thing with and it's realllly easy to code client type things with it.  Assuming I don't give a crap about anyone else but me using it, and I don't give a crap about the UI, what's keeping me from doing this?  I'd something that I ought to have done a long time ago.  Doesn't mean I wouldn't make it available for others to play with if they really wanted, but by the same token, since when can't I write something solely for me, where I don't offer or pay attention to bug reports... a "if you want to use this, here it is, if it doesn't work, fix it yourself or move on" software if you will.  Hell, who's to say I even have to make it available?  Sometimes I get stuck in the mentality that everything I do HAS to be done in a public facing manner and forget.

2 Comments 0 References Permalink
20

I have no concept of how many folk actually read this blog, but I have a question to pose.  What do you consider the reference or definitive Jabber client?  I know there is no official reference implementation at this time, but that doesn't prevent us all from coming up with our own decision about the matter.  I, for example, consider Psi to be the definitive.  It seems to implement things well, and implements a large chunk of functionality in the Jabber world, and is cross platform.  I primarily live in a Mac OS X world.  So ideally I'm thinking about Mac OS X clients.  Of course, that wouldn't prevent me from considering something for Windows, Linux, or Solaris.  My own client, JWGC, is far behind the times.  I'm going to talk about that some in a bit (separate post).  I was actually kicking around the idea of a strictly "here's a tool for testing out Jabber functionality" client at some point.  Of course, where will I find the time?  Something that would make it easy to mess with things on the fly and see what happens.  For example, what if I clicked the "send message" button, and it provided a typical send message window, but also put the xml equiv right below that I could edit by hand.  Actually, it might be easier and more worth my time to try to offer something like that as a patch for Psi.  Meh, we'll see.  Anyway, if you have opinions on what you consider to be reference Jabber client implementations, perhaps "one that implements the most functionality/number of JEPs", please post a response!

20 Comments 0 References Permalink