Return to Jive Software

2,256 Views 3 Replies Last post: Jun 17, 2009 3:15 PM by Todd West RSS
Rob Castle Novice 75 posts since
Jan 5, 2009
Currently Being Moderated

Jun 17, 2009 7:52 AM

Widgets in SBS 3.x

I am having trouble with a widget that I had working in 2.5 but doesn't seem to work in 3.0. All the documentation for widgets still have 2.5 information in it. Even the DTDs in the documentation specify the 2.5 version.

 

  1. Have there been any changes to the way widgets are built in 3.0?
  2. If so is there updated 3.0 documentation?
  3. Can I get a simple example widget that works in 3.0?

 

 

 

Thanks

Rob Castle

Todd West Jive Employee 15,918 posts since
Jul 14, 2008
Currently Being Moderated
Jun 17, 2009 8:38 AM in response to: Rob Castle
Re: Widgets in SBS 3.x

Hey Rob,

 

1. Have there been any changes to the way widgets are built in 3.0?

 

There have been a few changes to the Widget platform to allow for cacheable widgets/remote widgets for Bridging but for the most part the general design has stayed the same.

 

 

If so is there updated 3.0 documentation?

 

The 3.0 documentation can be found here:

 

http://www.jivesoftware.com/dev

 

and the Widget docs specifically:

 

http://www.jivesoftware.com/jivespace/docs/DOC-3301

 

 

Can I get a simple example widget that works in 3.0?

 

If you have a copy of the core source code handy this would be the best way to check out example 3.0 widgets. Let me know if you have any questions. Thanks!

 

-Todd

Todd West Jive Employee 15,918 posts since
Jul 14, 2008
Currently Being Moderated
Jun 17, 2009 3:15 PM in response to: Rob Castle
Re: Widgets in SBS 3.x

Hey Rob,

 

They actually aren't plugins, they are part of the core product. You can find them:

 

com/jivesoftware/community/widget/impl/*

 

 

Thanks.

 

-Todd

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.