You can find the latest Jabber SDK (CAXL) demo attached to this blog post. This is a reasonably feature-complete demo of Jabber SDK. Since it is a pretty massive overhaul of the last version of the Demo, you will almost certainly find bugs. Please provide feedback so we can fix them.
You can edit the demoConfig section in JabberDemo.html to define you server, username, etc. That way, all the login information will appear automatically in the login window. Or you can simply fill out that information in the login window each time.
There are a lot of changes since the last time we posted a new Jabber SDK Demo.
Updates:
* It now generates a random resource caxl_(random number) so that you can login with the same account using two browsers, and XMPP will know which one is which. This is basically the same approach Jabber for Windows uses.
* Fixed a problem where it detected a non-existent persistent chat room.
* If you delete a contact using some other method, such as EPASSoap, it detects the change and reloads the roster. If that was the last contact in a group, the group disappears.
* Other minor bug fixes.
Previous post:
Noteworthy Changes
* Javascript is broken out into separate files for easier browsing. For example, roster handling is in one file, multi-user chat rooms in another.
* This new demo will detect persistent chat rooms and add them to the roster. CAXL does not allow you to create new persistent chat rooms, however. You can only detect existing ones and use them.
* You can still create an ad-hoc multi-user chat room, and you can have multiple chat rooms open at once.
* The UI is back to using jQuery UI. The material design Javascript library was too unstable to continue to use.
Known issues
* LDAP search for contact info is not yet working
To Do
* Add back the "save custom status" that was in the Material Design version
* Add back the desktop notifications that were in the Material Design version
* Clean up the code and add more comments explaining how things work
