Return to Jive Software

1 2 3 Previous Next

Jivespace Community Blog

34 Posts tagged with the jivespace tag
Will French

Hello, Jivespace users and viewers!

 

Jive SBS 4.0 is generating quite a bit of buzz out in the marketplace, as well as here in Support.  We are excited about the new features we'll be taking advantage of when we upgrade, including some additional features and functionality in our Supportal customization.  Please read on to find out what is coming up in about a month!

 

First, the Vision

Jivespace started out with a focus on technical conversations and customer support.  Looking ahead, the vision for Jivespace is broadening to be a more connected communication ecosystem for technical and business people from the Jive team, customers, prospective customers, and partners.  The first step of this vision has already occurred (Oct. 3) by establishing a Business Conversations space and merging into that space all the content and conversations from a Jive community previously called Clearstep.  Many Jivespace members were also members of Clearstep, and, as just one example of the benefits to members, they now only have to worry about 1 set of login credentials.

 

With the upgrade to 4.0 in the near future, there are many additional features that will significantly help bring this vision to life.  Many of these new features are highlighted further below.  However, more than just new features, Jive is thinking about this community in a much more holistic way, and we are dedicated to making it a showcase of how businesses need to be operating by breaking down all the silos both within and outside a company's four walls.

Changes to the Supportal

 

Transition to Social Groups

We are making a big change when upgrading to 4.0: moving customers from spaces to social groups!  As we continue to evolve our support spaces, we have added additional functionality for membership.  One of the biggest advantages to moving to social groups is that we get membership for free!  We had been duplicating membership functionality, which, when looking at it from a higher level, really didn't make sense!  Social group are another way to align with our vision for Jivespace.

 

Cases and discussions

Both discussions and support cases will coexist in your customer group.  This lets you easily engage with other groups at Jive Software without having to wonder, "Where should this go?  It's not a support case."

 

Improved Severity 1 handling

We continually refine our support for major customer issues and have three changes in this release which help get us to the next level.

 

Severity 1 cases are now re-pageable

When a Severity 1 case is submitted by a customer with Premium Support, our on-call engineer is paged.  Once the on-call engineer acknowledges this page, no additional pages will be sent. Typically this is just what we want: an alert to get our attention for a S1 issue.  However, there are times where an on-call engineer asks for additional information or has an otherwise lengthy wait for a customer response.  During business hours this isn't a big deal, but off hours, in the middle of the night, it can be a burden.

 

To resolve this we've made S1 issues re-pagable.  When the S1 issue switches status to 'Waiting on Jive' during off hours, a new round of pages will be sent out.  This allows us the freedom to catch a few winks or otherwise step away from the computer while waiting for a response.  This will also help us increase our responsiveness to customers, as we'll be alerted immediately when the status of the case changes.

 

Integrated RCA cases (Root Cause Analysis)

Traditionally, Support has created separate Root Cause Analysis (RCA) cases for S1 issues upon request.  This was usually an ad-hoc exercise for sharing our findings.  Moving forward we'd like to solidify this process. To improve this practice we've implemented a 'Create RCA Case' feature available to our Support Engineers.  With one click, an Engineer can create a case based on a defined RCA template.  When doing so, we automatically link the S1 issue case to the RCA case for increased visibility and navigation.  Making it easy to create RCA cases will drive us to create RCAs for S1s at a higher rate than ever before, which in turn will help us ensure we are either prepared for this issue next time, or--better yet--stop it all together.  With increased visibility to RCA cases for our customers as well as the Support Engineers, resolution time for repeat issues should be dramatically reduced.

 

Automatic and Proactive follow-ups on Severity 1 issues

Severity 1 issues were not seeing the love they deserved.  We care as much about closing-out customer-reported S1 issues as you do, and with a new proactive follow-up tool in place, any S1 cases that become inactive for a couple days will send a friendly reminder to both the customer and the assigned Support Engineer.  Alternatives are to 1) decrease the severity of your case when it is no longer a Severity1 issue, or 2)  use the previously mentioned RCA ability to close out S1 issues quickly and effectively!

 

Upgrading to 4.0 = New features!

 

Without a doubt, 4.0 is Jive's biggest release ever, and we plan to leverage every applicable aspect for our public-facing communities.  In the Support area we're especially excited to use the new bridging capability with our internal community which will allow for more streamlined communication between our Support and Engineering teams.

We occasionally need to engage our Engineering team to help with complex support cases.  Using automatic linking and the ability to push and pull messages in either direction will be a huge help!  We are also jazzed about the improved HTML email support, as well as the ever-improving RTE.  In addition, we have some amazing new functionality that will make viewing uploaded MSOffice or PDF documents a breeze, with no need to download.

 

A brief highlight of some of the new Jive elements you won't see on Jivespace but you should definitely learn about are Jive Market Engagement, our SharePoint Connector, new mobile elements (that we can't talk much about until the actual launch in a few days), and new reporting capabilities.

 

 

Thank you,

 

Will French, Support Manager

Adam Mertz, Product Marketing Manager

866 Views 5 Comments Permalink Tags: jivespace, upgrade, supportal
Todd West

Out with the old

 

old_open_cases_widget.png

 

In the past, when a customer wanted to check on the status of any of their open cases they would log into their secure space overview page and use the Community Open Cases widget. This widget was designed with a very simple goal in mind, just display the open cases with a bit of extra information and an emphasis on Severity 1 issues. This proved useful for quite some time and gave customers a good overview of what was going on with their community from a support perspective.

 

However, there was one major flaw. Customers had no way of interacting with this information and often found it very difficult to organize this data in a manner that they could use quickly and efficiently. Welcome, open cases widget 2.0!

 

 

 

 

The new and improved open cases widget

 

new_open_cases_widget.png

 

Along with our upgrade of the Supportal to SBS 3.0, I took on the job of updating this widget to provide customers with better control over their open cases. There are two major upgrades that I gave this widget which have enhanced the way people use it:

 

1. Cases broken down by Severity

 

Instead of displaying all the open cases in a potentially enormous group, I've broken down the display into 3 distinctive parts. This is especially helpful for customers with more than 10+ open support cases at a time and allows customers to quickly see if they have any Level 1 issues that they need to attend to quickly.

 

2. New case option available: Priority

 

To the right of every case status is a set of up and down buttons which control the individual priority of every issue (within their respective severity).

 

 

 

 

 

Okay great, so how do I use it?

 

Step 1: Log in

 

Log into the Supportal and visit your Company's secure space "Overview" tab

 

overview.png

 

Step 2: Organize open cases

 

Browse through any open cases and use the "move up/move down" buttons to re-order them. All the moving on the screen will be done in real-time thanks to our good old friend Javascript. You may recognize these buttons from SBS, as they are used to control the location of profile fields on the admin console registration settings page.

 

priority_control.png

 

Step 3: Don't forget to Save!

 

As of right now, your cases will be in the order you want on the overview page, but there is one final step. You will need to click the Save Settings button at the bottom right hand corner of the widget. This will take the current ordering of your widget and persist the case priorities to the database.

 

save_settings.png

 

You will receive a friendly notification at the top of the widget that your Priority changes have been successfully saved, and you are done!

 

settings_saved.png

 

 

 

Well that's easy enough, how does it all work?

 

I'm glad you asked--it's really quite simple.

 

 

Displaying the widget

 

First off, the widget loads up all the non-closed cases within a secure space and puts them into three different Collections (one for each severity):

 

for (String caseID : caseIDs) {
    try {
        SupportCase supportCase = supportCaseManager.getSupportCase(Long.parseLong(caseID));
        String status = supportCase.getStatus();
        if (status != null && !caseStatusManager.isClosedStatus(status)) {
            String severity = supportCase.getSeverity();
            String priority = supportCase.getPriority();
            supportCase.setPriority(priority != null ? priority : "0");
 
            if(severity.equals("Level 1")) {
                openSev1Cases.add(supportCase);
                Collections.sort(openSev1Cases, new CaseComparator());
            }
            else if(severity.equals("Level 2")) {
                openSev2Cases.add(supportCase);
                Collections.sort(openSev2Cases, new CaseComparator());
            }
            else {
                openSev3Cases.add(supportCase);
                Collections.sort(openSev3Cases, new CaseComparator());
            }
        }
    }
    catch (NotFoundException e) {
        log.error("Could not retreive support case in OpenCasesWidget: " + e.getMessage());
    }
}

(Ideally this will get refactored soon to allow for more or less than 3 severities instead of being hard-coded. But it will work for now.)

 

 

The CaseComparator() orders all the currently open cases by their priority in the database. If nothing has yet been set, it will be put in the order that the cases were created.

 

 

The fancy effects

 

The cases are now sent to the template, where they are displayed in their respective severity grouping and automatically hooked into the Javascript functions that allow the up/down buttons to work. When you click on one of the buttons the following Javascript magic happens:

 

1. References to the required objects on the screen are loaded up using Javascript:

 

var moveUp = function(e, type) {
    Event.stop(e);
    var ansc = this.up(".case-field");
    if(ansc != undefined) {
        ansc.previous().insert({before: ansc});
        updateHiddenField(ansc, ansc.next());
    }
    updateOrderingAnchors(type);
}

 

2. A hidden priority field for each case is updated with the new ordering value:

 

var updateHiddenField = function(element, newElement) {
    var temp = element.select(".case-priority")[0].value;
    element.select(".case-priority")[0].value = newElement.select(".case-priority")[0].value;
    newElement.select(".case-priority")[0].value = temp;
}

 

3. The ordering of the case above (or below if the down arrow was pressed) will be swapped on screen and the list rebuilt:

 

var updateOrderingAnchors = function(type) {
    if(type == "1") {
        var elms = $("sev1-case-list-body").select("tr");
    }else if(type == "2") {
        var elms = $("sev2-case-list-body").select("tr");
    }else{
        var elms = $("sev3-case-list-body").select("tr");
    }
    elms.each(function(tr, i) {
        var anchors = tr.select(".field-moveup")[0];
        if (i <= 0) {
            anchors.update("<span class='move-up-disabled'>move up</span>");
        }
        else {
            anchors.update(new Element("a", {"class": "anchor-move-up", href: "#"}).update("move up"));
        }
        anchors = tr.select(".field-movedown")[0];
        if (i == elms.length - 1) {
            anchors.update("<span class='move-down-disabled'>move down</span>");
        }
        else {
            anchors.update(new Element("a", {"class": "anchor-move-down", href: "#"}).update("move down"));
        }
    });
    bindAnchors();
}

 

 

4. Now that the ordering is complete, you click the Save Settings button which makes a call to this Javascript to call a DWR method and display the nice notification at the top of the widget:

 

CasePriorityAction.setPriorities( values, {
    callback:function() {
        $('save-button').enable();
        $('jive-success-box').style.display = "block";
        Effect.Fade($('jive-success-box'),{delay: 3, duration: 5});
    }
});

 

 

 

Saving the data

 

The final step involves saving this to the database, which is done by the call to the setPriorities DWR method as noted above. This loops through all the cases on the screen and sets the priorities in the database accordingly:

 

public void setPriorities(List<String> values) {
    try {
        for(String value : values){
            String[] vars = value.split("-");
            SupportCase supportCase = supportCaseManager.getSupportCase(Long.parseLong(vars[1]));
            supportCase.setPriority(vars[2]);
            
            supportCaseManager.updateSupportCase(supportCase);
        }
    }
    catch (NotFoundException e) {
        log.error("Could not retreive case in CasePriorityAction: " + e.getMessage());
    }
}

 

 

 

I hope this information provides you with interesting insight into how our custom development allows us to work smarter and more efficiently with all our customers.  We want these new features to enrich your Jive experience!

 

As always, Jive welcomes any and all feedback about this feature and the Supportal in general.  Please comment on this post or start a discussion in our Supportal Feedback space.

1,889 Views 3 Comments Permalink Tags: jivespace, customization, support, development, widget, javascript, supportal, sbs
Will French

Welcome to Jive SBS! We just upgraded our Jivespace community to SBS 3.0.1, and along with it upgraded the Supportal customization, adding a few new features and improvements.

 

If you see any issues, please post a discussion in our Supportal Feedback space or create a public case there, and we'll get it addressed quickly.

 

Now, on to the new features:

 

An updated Open Cases widget allows prioritizing by the customer

We previously allowed you to view your open cases, but sometimes when you have a few open cases it can be helpful to rank them in importance--both for you and your company, but for us as well. Have a look at it here, and it will automatically be in your account's secure space next time you log in!

 

http://content.screencast.com/users/klassikstile/folders/Jing/media/021663a7-277a-4f3f-a755-08d636bfc98c/2009-04-06_1501.png

 

Account Member Management falls into the hands of the Customer

Prior to this Supportal upgrade, if you wanted to add or remove someone from your secure space, you needed to ask Support to do so. Well, with the upgraded Supportal, you can now put this power into the hands of someone that is currently a part of your account. There is still one manual step, asking Support to appoint one of your users as 'user admin' for your account. Once designated, the user admin can add and remove users, as well as add/remove the admin privilege should that assignment need to change. You can see the link to manage account members on the Group Membership Widget on your secure space overview. Don't see it? Ask Support to add it to your account space today!

 

 

First integrated Environment tracking on cases

Are you tired of Support continually asking what version you're running, or similar questions? Well, we're tired of asking it too ! We've now taken the first step to associating Environments to each and every one of your cases. That way, if the version does matter, we can simply take a look at the environment you have associated with the case and dive right into troubleshooting. What's the catch? We are going to need you to keep these as current as possible in order to make this all work smoothly. We are hoping to evolve this to be able to eliminate the Product drop down and solely use Environments in the future. We welcome your feedback and help in shaping this new feature in the Supportal. Please visit our Supportal Feedback space to do this.

 

environments.png

 

Lastly, some new UI when creating a case

As you can see from the screenshot above, we've added some indication of what fields are required when creating a new case, and something you may also not notice is that we have taken away the 'Stage' detail as it was not useful to us.

 

Again, please let us know if you see any issues, and we hope you enjoy the new Supportal and the overall upgrade to SBS!

1,917 Views 5 Comments Permalink Tags: jivespace, upgrade, supportal, sbs
Steve Traut

A week ago Greg wrote about the changes we recently made to simplify Jive's communities. You'll now find four communities -- Support, Features, Developers, and Plugin Downloads -- under one community to collect them all: Jivespace. I'm chiming in this week with details on changes to docs for developers building customizations to Clearspace.

 

Here it is in a nutshell: The latest developer documentation will be in the Developers community in Jivespace. That community is also the place to post your questions and comments. Other content, including developer content from previous versions, will be on the site where docs have been for some time now.

 

The best part, as I see it -- and really, I think this is fantastic -- is that it's not just docs. There's a lot more information: FAQs, how-tos, links to more information, and more. Internally, we started out calling it a "cookbook" (okay, Greg called it a cookbook and we humored him for a while). But while it wasn't really as procedural and example-driven as software cookbooks tend to be, it was obvious he was on to something. You (and we) really needed a single place to collect the knowledge we develop internally for extending and customizing Clearspace.

 

If you've been to the Developers overview page, you might also have noticed that we've tried to make it easier to get to what you care about. The search box and "spotlight areas" are designed to help you find developer content without leaving the developers' stuff if you don't want to.

 

By the way, there are no longer any Forums or older Clearspace docs on Jivespace. It had gotten to be kind of a mess (a "train wreck," as one of its admirers said). We're thinking it's better to have one version of developer content on the Developers community, and the rest of it where other docs live. See what you think.

 

Here are the links of interest:

 

1,543 Views 0 Comments Permalink Tags: jivespace, clearspace, developers, documentation
Dawn Foster

This post is the fifth in a series of blog posts about customizing for Clearspace 2.x. The previous posts covered:

  1. Customizations in Clearspace 2.x

  2. Upgrading Themes and FTL Files.

  3. Widgets in Clearspace 2.x

  4. Macros for Clearspace 2.0

 

Several changes were made in Clearspace 2.0 that could impact your web services code, whether the code is for a client or new service. Generally, these changes were made to make the API easier to use, to add functionality (such as support for REST, new in version 2), or to remove a little-used feature that couldn't be made to work well.

 

  • ln version 2 Clearspace web services are built on the CXF framework. CXF evolved from XFire, the framework on which Clearspace version 1 web services were built. When upgrading, be sure to update your classpath to replace the XFire JAR file with the CXF JAR.

  • SOAP-based web services no longer support caching; references to caching have been removed from the web service client API.

  • If you're using the Clearspace web service client API (for SOAP web services), you'll need to update your references to some classes. To clarify the difference between the standard and web service client APIs, some class names were prefixed with "WS". The Upgrading Extensions to Version 2 documentation contains a list of the renamed classes; these are all in the com.jivesoftware.community.webservices package. Of course, this also means that signatures for some of the methods within the API itself have changed where these types were used.

  • Update some API references where arrays were used so that collections are used instead.

  • The .NET client API is no longer available. If you've got a .NET client, you'll need to rewrite it using another web service client library.

  • If you've written web services that expose Clearspace functionality, note that the WSUtil.getJiveContext method has been removed. Instead, as noted in the description of API changes, you should use Spring properties to obtain manager references.

  • Web services you've included in a plugin are no longer declared in the plugin.xml file. In version 2, when writing a web service for deployment in a plugin, you declare the web service in a spring.xml file included in your plugin. Use the conventions described in the Apache CXF user's guide.Here's an example 

<bean id="echoServiceImpl" class="com.jivesoftware.clearspace.plugin.example.webservices.EchoServiceImpl /">
    
<bean id="saajInInterceptor" class="org.apache.cxf.binding.soap.saaj.SAAJInInterceptor" />
    <bean id="wss4jInInterceptor" class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor">
        <constructor-arg>
            <map>
                <entry key="passwordCallbackClass"
                    value="com.jivesoftware.community.webservices.server.xfire.PasswordHandler" />
                <entry key="action" value="UsernameToken" />
            </map>
        </constructor-arg>
    </bean>
    <bean id="validationCheckInterceptor"
        class="com.jivesoftware.community.webservices.server.xfire.ValidationCheckInterceptor">
    <property name="jiveUserDetailsService" ref="jiveUserDetailsService" />
</bean>

<jaxws:endpoint id="echoService" address="/soap/EchoService">
    <jaxws:implementor>
        <ref bean="echoServiceImpl" />
    </jaxws:implementor>
    <jaxws:inInterceptors>
        <ref bean="saajInInterceptor" />
        <ref bean="wss4jInInterceptor" />
        <ref bean="validationCheckInterceptor" />
    </jaxws:inInterceptors>
</jaxws:endpoint>


  • In version 2 WSDL operation params have friendly names. You should get new version 2 WSDL.

  • In version 1 accessing web services via XML-RPC used two extra parameters for username and password; version 2 uses basic auth instead.

 

The information above along with more details can be found in the Upgrading Extensions to 2.0 documentation.

 

We also have a video (with an attached presentation) that shows more about using web services to access your data in Clearspace 2.0 with Andrew Wright, Jive Software Engineer.

 

 

1,669 Views 0 Comments Permalink Tags: jivespace, jivespace, clearspace, webservices, api
Dawn Foster

We just launched our new Jivespace Plugin Directory for Clearspace plugins! You can now more easily find and download plugins from Jivespace, and if you are developing plugins, you can add your plugins to the new directory.

 

Plugin Directory

 

The really cool part is that we created the entire plugin directory as a plugin to Clearspace. Our web engineer, Tim, took our existing document content type and extended it to create a new plugin type with additional information relevant to plugins along with a new look and feel for the plugin directory.  He also used the plugin jar to pull almost all of the metadata displayed with the plugins, including license, logo, readme, compatible versions, and much more. For developers, this means that you only need to enter the information in your plugin, instead of having to duplicate all of the information by filling out redundant forms. It also means that when you update your plugin jar file with a new release, the plugin information will be automatically updated.

 

Tim is currently working on polishing the code a bit, but he will be releasing this as a plugin for other people to use as a plugin marketplace. It also provides a very useful example of how to extend an existing Clearspace content type to create a new content type in Clearspace.

 

Keep in mind that this is just the first version of our Plugin Directory, and we plan to start making incremental improvements and enhancements. But first, we want to hear from you. Take a look at the new Jivespace Plugin Directory. What do you like? dislike? How can we make this even better in future revisions?  Please leave comments with your ideas on this blog post!

 

 

 

 

1,108 Views 1 Comments Permalink Tags: jivespace, clearspace, plugins, plugin_directory, plugin_directory
Dawn Foster

Learn all about how to write new widgets for Clearspace 2.0 from Aaron Johnson, Engineering Manager at Jive.

 

 

You can also download the Quicktime version (Caution: file is ~285MB), or you can watch a larger version online, which will improve readability of embedded screenshots (recommended).

 

The entire presentation is also attached below as a PDF file.

 

You can also watch an earlier video about developing widgets for Clearspace 2.0

1,475 Views 0 Comments Permalink Tags: plugin, jivespace, jivespace, podcast, video, clearspace, widget, 2.0
Dawn Foster

Theming in Clearspace 2.0

Posted by Dawn Foster May 12, 2008

As you know, we changed a few things in our underlying architecture for Clearspace 2.0, including some changes in the Freemarker templates as a result of moving from Webwork to Struts along with some other changes. In this video, Matt Walker, Professional Services Engineer at Jive Software, talks about the process of upgrading existing themes along with plenty of best practices to make your themes more easily upgradeable in the future.

 

Matt also did an earlier screencast as an Introduction to Skinning Clearspace, which you might also want to watch along with this video.

 

 

You can also download the Quicktime version (Caution: file is ~200MB), or you can watch a larger version online, which will improve readability of embedded screenshots (recommended).

 

The entire presentation is also attached below as a PDF file.

1,417 Views 2 Comments Permalink Tags: jive_software, jivespace, jivespace, podcast, video, clearspace, themes, freemarker, customization, struts, struts
Dawn Foster

I wanted to remind everyone that we have a Jivespace weekly group chat scheduled for tomorrow (and every Thursday) from 9-10am Pacific time. During this hour, you can ask any questions about Clearspace development topics to the engineers who wrote the software.

 

Do you have questions about

  • how we are using Spring, Struts, Acegi, and more in Clearspace 2.0?

  • a particularly difficult customization?

  • writing plugins and widgets?

  • accessing Clearspace data from other sites using web services?

  • any other developer topic?

 

Please feel free to drop in anytime during the hour to ask questions. We also post all of the chat transcripts to Jivespace.

935 Views 0 Comments Permalink Tags: jivespace, jivespace, community, clearspace, chat
Dawn Foster

DWR in Clearspace 2.0

Posted by Dawn Foster Apr 18, 2008

Aaron Johnson, Jive Engineer, presented to our engineering team about how DWR is used in Clearspace 2.0. He started by walking us through an overview of DWR. After the overview, he showed us exactly how he used DWR in his FeedBlog plugin.

 

This 7 minute video has the highlights from his presentation.

 

 

You can watch a larger Flash version or download the Quicktime Movie version (Caution: 1761MB file)

1,137 Views 0 Comments Permalink Tags: jivespace, podcast, video, video, clearspace, 2.0
Dawn Foster

Here are some resources for anyone wanting to migrate to Clearspace 2.0 or just learn more about the development environment for Clearspace 2.0.

 

A week ago, we did a series of presentations about Clearspace 2.0 development. We also videotaped all of the presentations, but the editing will take some time for the video, so I wanted to go ahead and share PDFs of the presentations now with the Jivespace community. The videos should be coming out at a rate of 1-2 per week over the next few weeks.

 

I have attached 5 presentations, and I suggest reading them in this order:

  • Clearspace 2.0 Overview

  • Theming

  • Plugins

  • Widgets

  • Web Services

 

 

1,714 Views 0 Comments Permalink Tags: jivespace, clearspace, developers, developers, 2.0
Dawn Foster

Clearspace 2.0.1 Released

Posted by Dawn Foster Apr 18, 2008

Clearspace 2.0.1 was released last night. It has a number of bug fixes over the 2.0.0 release.

 

It also has significant improvements to the source build. Several people posted issues  with our source build here on Jivespace, and we think that this version should resolve those issues.

 

Existing customers can download the new source build or the new application files from your "My Account" page. If you want an evaluation version of Clearspace or Clearspace Community 2.0.1, you can find it on the Jivespace downloads page.

1,134 Views 5 Comments Permalink Tags: jivespace, clearspace, 2.0
Dawn Foster

I wanted to point out (in case you haven't noticed the difference) that Jivespace and some of our other Jive communities are now running on Clearspace Community 2.0!

 

You can learn more about our launch of Clearspace 2.0 and our new website by visiting Jive Talks.

 

With any major upgrade, we can probably expect a few minor issues (despite intensive internal testing). If you notice anything strange or buggy, please post comments here.

1,045 Views 2 Comments Permalink Tags: jivespace, clearspace, clearspace_2.0
Dawn Foster

In this video, Clearspace developer, Nick Hill, talks about how Prototype, Scriptaculous and other Javascript technologies are used within Clearspace 2.0. This was originally presented as an internal Jive training to get our developers up to speed on some of the newer technologies used in Clearspace 2.0, and we wanted to share it with other people doing Clearspace development. If you want to learn more about the Clearspace 2.0 beta, you can visit the beta area on Jivespace.

 

The pdf file with the complete slides from the presentation is attached below.

 

 

You can watch a larger Flash version or download the Quicktime Movie version (Caution: 179MB file)

1,189 Views 0 Comments Permalink Tags: jivespace, video, clearspace, javascript, 2.0, 2.0
Dawn Foster

I took the best 6 minutes out of a presentation that Fred Brock of Jive Software delivered to our engineering teams to teach all of us about the best ways to develop widgets for Clearspace 2.0. This is a must-see for anyone wanting to write widgets for Clearspace 2.0! I've also attached a PDF version of the slides from Fred's presentation.

 

 

Or you can download the Quicktime movie (Caution: ~85MB file)

2,170 Views 1 Comments Permalink Tags: jivespace, podcast, video, video, clearspace, beta, widget
1 2 3 Previous Next

Actions

Popular Blog Posts