eyeJabber - planning

[bluefoxicy]

As noted earlier, EyeOS 1.3 will have a networking service called eyeBus.  This leaves open the potential to create a Jabber client for EyeOS, which when complimented with a local Jabber server gives a powerful internal IM system.

I'm thinking of a sequence of events...

• Port jabberclass to eyeBus
• Create an eyepackage to install the new eyeJabberclass as some sort of library
• Create a client that just shows a buddy list of who's on (Proof-of-Concept)
• Add the ability to send and receive messages (Useful application phase)
• Begin extending into a fully featured Jabber client (Maturation)

The beginning of this entails critical, far-reaching design decisions.  Does anyone have any suggestions for other routes to take with XMPP/PHP?  There was class.jabber.php but that was rewritten to the event-driven jabberclass.

[Fernando Ibanez]

You may want to take a look at jwchat and muckl.

I can open muckl from eyeos using eyenav and it works fine.  It requires no PHP or eyeos integration, but integration would be nice.
If you could synchronize the jabber server with the eyeos users, I can see your idea being quite cool.  I am using ejabberd as the server.

[bluefoxicy]

mcukl won't work, as I want something running self-contained (i.e. something I could run on a network not connected to the Internet, but connected to other sites over a WAN?).

JWchat relies on Java, and doesn't integrate with EyeOS as well as I'd like.  It requires extra set-up and as far as I can tell likes to pop out its own windows (no good).  I've looked at this one before.

[Fernando Ibanez]

mcukl won't work, as I want something running self-contained (i.e. something I could run on a network not connected to the Internet, but connected to other sites over a WAN?).

JWchat relies on Java, and doesn't integrate with EyeOS as well as I'd like.  It requires extra set-up and as far as I can tell likes to pop out its own windows (no good).  I've looked at this one before.

If you have your own jabber server muckl could work.  I would look at it again. There is no difference between the wan or internet... the behaviour of the software is the same.

JWChat does not require java, double check that.  It does want to popout eyeos, I am currently looking at modifying this behaviour so it stays inside eyeOS.

[bluefoxicy]

JWChat does not require java, double check that.  It does want to popout eyeos, I am currently looking at modifying this behaviour so it stays inside eyeOS.

JWChat-1.0beta3.war (War Archive)

WAR archives contain Java servlet based applications to run on top a JSP/J2EE platform like Tomcat, Geronimo, Jetty, Websphere....

Not PHP.

[Fernando Ibanez]

JWChat is a full featured, web-based Jabber™ client. Written using AJAX technology it relies on JavaScript and HTML at the client-side only.

I have it working.  Try it, you'll probe yourself incorrect.

[bluefoxicy]

You're right, it uses javascript.  It just comes as a WAR file (which is a Java servlet platform i.e. Tomcat Web application archive), for no real reason.  My mistake.

Of course, it's terminally broken, as it exposes the login name and password through a GET request, which fills the web server logs with username/password pairs (I had to sanitize my logs), and also puts them in the Web browser's address bar.