We're excited to announce that the Clearspace and Clearspace X betas are now part of the release train and will be released every three weeks on the Wednesday directly following when the prior general release is made available. The first beta is available today for version 1.6, just after the final release of 1.5 came out last week.
Please don't use these beta releases in production, and please don't upgrade your production instances to the beta releases. Instead, install the beta as a new installation or use a copy of your production system to try out the beta upgrade. We don't officially support the betas, but would love to get your feedback on them in Jivespace.
1. Select the text to which you want to attach your link.
2. Click the Link button.
3. Type (or paste) the URL.
Ive watched novices struggle with this for years, and its no wonder that they do.
We've spent a number of cycles making the rich text editor linking process easier in Clearspace. In case you've never explored the little link button in the editor, clicking on it pops up a window that looks like this:
The pop up window defaults to showing you a search interface: do a quick search and you can link to anything in Clearspace. Conveniently there are two other options: the history option:
which shows a list of your most recently viewed blog posts, forum threads and wiki documents and second: the web address option:
where you can type in or paste a URL and then a link title. We've gone through a number of rounds of design on this pop up window and I'm sure there's still room for improvement (there is no perfect design). We'd love to hear your feedback though: what do you like about linking in the editor? Which of the three tabs do you find you use the most? Did you even know it was there? And for any developers out there, has anyone tried to or wanted to customize the editor? If so, what did you did do to it?
If you need an idea for a plugin, you might want to visit the plugin wishlist on Jivespace. We have several plugin ideas from people who want a specific piece of functionality, but who do not have the expertise or spare time to write a plugin.
If you have an idea, but have never written a Clearspace plugin, our documentation page might be a good place to start. We have a Clearspace Developer kit, tutorials, documentation, Javadocs, and more to help you get started!
As always, you can also ask questions in our community to get help from your peers or the experts at Jive Software!
Watch this video to learn more about how Clearspace handles internationalization and accessibility from Jive Software engineer Todd McCullough. Todd also wrote an accompanying blog post with more information about Clearspace product internationalization and related topics.
Since Jive is a vendor in the international market space, our products need to handle a variety of aspects of internationalization, or i18n. Typically, this involves extracting human readable text from the UI and moving it into a ResourceBundle. But, it doesn't stop there. We also need to handle localization of email templates, dates, bidirectional support, and accessibility. Most of this is not glamorous development work, but it's really important to a lot of our customers, and improves the usability of our products in general. Below are some high level details of our approach to these topics.
Forums and Clearspace both support locales at a variety of levels in the object hierarchy. This includes user, "container objects", and global locales. With Forums, locales can be defined in the Category and Forum container objects. With Clearspace, locales can be defined in the Community/Space container objects. If a user specifies a locale, that is chosen first in the decision matrix. After that comes the container object, and finally the global locale. A customer webwork interceptor applies the appropriate local to a given request.
Within the UI layer, we use webwork ww:text tags to retrieve the locale specific text String. The various ResourceBundles are specified in the webwork.properties file, and webork applies the locale that is set by the custom interceptor. Within the Action layer, we provide an implementation of the TextProvider interface. If an i18n String is required outside of an Action, the LocaleUtils class provides an alternate implementation of TextProvider.
Since email templates from our notification system can be quite lengthy, we provide the ability to create new set of email templates for each locale without having to muck with a ResourceBundle. This approach provides for a better user interface, and lets us store the customized templates into the database with the specified locale. In Clearspace, we created a nice UI to easily customize email templates for any number of locales.
International companies have stronger legal requirements for accessibility than the US. With software, we need to support screen readers for the visually impaired. Screen readers pay attention to every detail of the UI, which can come across quite differently than the visual representation. In general, pay attention to meta tags like "alt" for giving valuable details to images. It doesn't help someone out very much to hear "rockin_icon.gif, smileyface123.png" over and over again. Instead, we provide meaningful information in the alt attributes and the reader will announce those instead.
So, internationalization is sometimes tricky and cumbersome to implement, but overall is quite necessary to acceptance in the international market.
I wanted to let everyone know that the Jivespace Video Podcasts are now available from iTunes. You can subscribe using the previous links or by searching for Jivespace within the iTunes store. The iTunes versions are slightly higher quality than watching through the embedded player, so they will look a little better, but they may take a while to download.
Danese Cooper and I put together a community panel at OSCON discussing the art of building and maintaining successful communities. The panel included (from left to right): Danese Cooper (Moderating), Jimmy Wales, Dawn Foster, Sulamita Garcia, Whurley, Karl Fogel, and Brian Behlendorf.
This video contains the entire session and runs about 50 minutes.
Or download the Quicktime version (caution: this is quite large and may take a long time).