[JDEV] Good jabber client needed (was: Response to Jer's Article)

[Colin Madere]

(Agreed * 1000), Eric.

We literally have 6 jabber servers in different states that we're using for
development and testing and yet we are NOT running one for IM use... why?
There is no complete / friendly client out there (no offense to you client
developers.. but, hey..), not to mention we have users on Win32, MacOS and
Linux.

I am all for supporting such a client development.  It is something I have
heard many people say about Jabber: "Wow, that's great.. I wish there was a
good client."

The component idea I think would work.  Start by defining an API for each
component and then maybe have groups working in different languages to do
this (to me, Java is an obvious choice, but there are concessions you make
using Java for cross-platform work).  I know JabberBeans is an extensive
effort by David Waite, but what clients use it?

> -----Original Message-----
> From: Eric Murphy [mailto:murphy at cedarnet.org]
> Sent: Wednesday, March 14, 2001 5:10 PM
> To: jdev at jabber.org
> Subject: [JDEV] Response to Jer's Article
> 
> 
> I wrote a little something at 
> http://jabber.org/index.php?oid=651, or here
> is the text. Let me know what you think!
> ...
> 
> I asked Jer, and Jabion means 'Jabber-Vision'. It is implied (see the
> title).
> 
> My belief is that Jabber is only as good as the clients on 
> both ends of a
> conversation. Sure, the server may continue on growing, but 
> if everyone is
> out there using unfriendly/incomplete clients (Jabberzilla 
> ;-), then their
> impression of Jabber will not be good.
> 
> (One thing that I have noticed is how the term 'Jabber' has a 
> similarity
> with 'Linux', because their definition depends on how the 
> technology is
> presented and used)
> 
> Everyone in the Jabber community has an idea of what the 
> ultimate Jabber
> client is. These ideas seem to be mostly the same, from 
> talking with many of
> you. So, how do we get there? What are we looking for?
> 
> Somehow we need to work on a client project together, as a 
> group. Not all
> would have to program, but anyone with Jabber technical 
> knowledge would be
> of help in some form. Like Jer says, manpower is limited, so 
> we have to help
> each other out as much as possible.
> 
> We all use different types of computers, and have different 
> wants and needs
> of a Jabber client. Therefore, the client has to be cross-platform and
> flexible. There should be an infrastructure built so anyone 
> can come along
> and easily create their own Jabber client to fit their needs. In other
> words, create building blocks (feature components) that 
> author can use as
> needed, or build their own based on a specification.
> 
> How we should do this... is up for discussion :-)
> 
> 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20010314/1b20c853/attachment-0002.htm>