Spark is an Open Source, cross-platform IM client optimized for businesses and organizations. It features built-in support for group chat, telephony integration, and strong security. It also offers a great end-user experience with features like in-line spell checking, group chat room bookmarks, and tabbed conversations.
Combined with the Openfire server, Spark is the easiest and best alternative to using un-secure public IM networks.
When SparkWeb became open-source, I took a look at the source code and found it had more features than the Flex-based XMPP client I was co-developing for the Red5 Plugin. It therefore made sense to migrate the Flash audio and video features we had developed for our client to SparkWeb and make it compatible with the Spark and Openfire Red5 Plugins and package it as part of the Red5 plugin. The downside to this that the modifications to the Red5 version of SparkWeb makes it out of sync with the official SVN and it could possibly become a fork requiring a name change later on.
So what does the Red5 SparkWeb offer?
![]() |
I also made a few cosmetic changes to my taste and added sound effects for incoming calls and instant messaging. I added some code to improve the loss of focus detection by tracking Flash application activation/deactivation messages and mouse movement. If you use Internet explorer and enable pop-ups, you will get a pop-up in the bottom right corner of the screen with a photo, name and first line of the incoming messaging if you are outside of SparkWeb when a new message arrives.
I am hoping to add fastpath support and a calendar to SparkWeb next.
Matt's recent post on our client strategy generated quite a bit of discussion.
In this video, David Smith chimes in with some thoughts on the strengths and weaknesses of emerging technologies associated with web applications. Watch the video below to learn more about our thoughts on the future direction of web app vs. desktops apps.
Or download the Quicktime version (Caution! ~200MB file).
You may or may not already be aware that I have been a full time member of the Jive family for a couple of weeks now! It's been quite interesting to see how different it is from my previous job in a university setting. It's been a lot of fun already and it's really exciting to have turned my favorite hobby into a career. =) My coworkers are great and I almost find myself wondering why I didn't do this earlier.
So what am I going to be doing? Well, the development of the IM Gateway plugin is part of my job now. We'll be setting solid goals and release dates instead of it being dependent entirely on my free time. That and Openfire are my main focuses. I'm really excited about playing a more direct role in Openfire development! One of my first tasks will be to improve the unix installers for Openfire. They have been lacking love for a while now and I have a strong unix background to bring to the table. In one of the next releases of Openfire we'll have improved packages, unix scripts, and better support for more operating system distributions. Overall, good things to come! =)
You may have heard that I have taken over as lead developer of Spark. It's been a long time since I have been involved in client development and I actually miss it. My very first XMPP related project was a client. Now, as you've heard from the Ignite Realtime post preceding this one, Spark is a low priority. My focus with it in terms of work with Jive is bug fixes, maintenance, and paying customer requirements. Beyond that, I'll likely be working on it on my own time when I need a change of pace. I am a Mac user primarily, so you may see more Mac focused fixes at first. If nothing else I'm going to make sure Spark is something I enjoy using, which coincides to a lot of things that the community has reported/requested anyway. I highly encourage folk who are interested to submit patches! The only caveat is that for patches of any size, I'll need you to sign contributor agreements, if you haven't already.
Now, since I'm involved in more than just the IM Gateway plugin now, I can't keep up with the forums as much as I did before. I try to spend some time each day looking over the forums, but with more than just the single forum, it's too much to keep up with entirely. Dawn is working hard on coming up with good ways to involve the community more and try to make sure things don't get missed! She has been speaking on this in the Jive Lounge, so please visit the lounge and contribute if you have some thoughts!
Anyway, I wanted to make sure folk understood that my role has changed and wave hi from within Jive! =) Any questions?
So, what's up with Spark? Many of you have commented on the fact that the pace of development has slowed and that Derek is less present in the community. Now that a major new version of SparkWeb is out, it seems like a good time to provide a more detailed status report on everything happening around client development.
First up, an announcement: Derek has taken a new position (Sales Engineer) inside of Jive. So far he seems to be loving it, but I'll let him comment on this blog post with further details. Unfortunately, that means that Spark has lost its lead developer. For the time being, other team members have stepped in to help out. We're committed to providing bug fixes and minor new fixes to Spark for the foreseeable future. It remains one of the best cross-platform XMPP clients available.
Since Spark development is slowing down, what's next? Most of Jive's XMPP client efforts are now focused on the web via the SparkWeb Flash client. We're using the same technology base to add real-time features to Clearspace. Further, the upcoming Adobe Air technology offers the intriguing possibility of building a new desktop client using Flash. To us, it all seems like the perfect triple play -- a single code base that can be used for Sparkweb, Clearspace features and a new Spark desktop client. Only Sparkweb is ready so far, but you'll see new real-time features in Clearspace soon and we'll keep everyone updated on a desktop client based on Adobe Air.
Change isn't always easy and I'm sure that some of you will be disappointed to hear that our approach to how we build Spark is changing. There may be some rough spots as we move from one technology to another, but we're pretty excited about where things are headed.
In this video, Jive Software's David Smith talks about Actionscript, Javascript, and the future of webapps as they relate to his work on Spark.
Or download the Quicktime version (caution: 69MB file)