last steps towards jwchat-1.0 (and thoughts about what’s beyond)

Currently I’m preparing for the long awaited release of JWChat v1.0. I haven’t been working on it for a long time now (2-3 years) and all I want to do is to fix some remaining issues, do some compatibility tests and that’s it. So if you know of some things you think they should urgently make into the v1.0 release please let me know.
My plans are to discontinue development on JWChat’s code basis after the release. As so many other projects JWChat has evolved out of some initial proof of concept and as such the code is merely utterly ugly. What I’d like to see is a framework for building web enabled (aka AJAX), XMPP driven chats that is really easy to integrate into existing projects. Which is easy to adopt and customize. I’m thinking of something built on top of dojo(?) and jsjac(?) with an MVC driven approach that let’s you define which parts to (re)use wihtin your own app and let’s you customize those that aren’t exactly the way you like it. Actually I’ve already started with it but that’s not ready for prime time. Hope there’s enough spare time for it soon 😉

3 Responses to last steps towards jwchat-1.0 (and thoughts about what’s beyond)


  1. Comment by Andrés Caro | 2008/10/01 at 23:56:55

    I have used you Jwchat client for some times it has a rustic appearance but it´s fast and works very well in closed networks with rude firewalls. I would like to see some features in a future like: transfer file, discover services, etc. But i think you will delivery a bug free product and don´t work any more in the code, then i only can say thank you and good luck with the new projects…


  2. Comment by zeank | 2008/10/02 at 00:38:51

    Well, actually JWChat does a lot of Service Discovery. But it hides it from the user because I don’t think that’s something the average people it interested in.

  3. Comment by Matt | 2008/10/05 at 23:07:03

    Are there any other mature IM client projecst out there? Everyone I’ve probed, seems dead.

    What happened to all that great potential for opensource applications? This is so disappointing.

Comments are closed