Great post. This is brilliant. Works very well with IntelliJ Idea too.
On Dec 12, 5:29 pm, "John Panzer" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> We're happy to announce that we've just performed the first commit to the
> Apache Shindig project, contributing Gadget Container JavaScript and Gadget
> Server Java code.
>
> For some high-level context on this, read the related
> post<http://opensocialapis.blogspot.com/2007/12/lets-get-this-shindig-star...>at
> the OpenSocial Blog.
>
> In addition, the initial commit comment - copied below - provides
> finer-grained detail on what's just been contributed. We expect to continue
> to flesh out the code and submit a load of features in the upcoming weeks.
>
> We're excited to take this first step, and hope you are too. We're looking
> forward to keeping the pace of change high in the upcoming weeks and months.
>
> Best,
> John (on behalf of a bunch of people)
>
> [commit description follows]
>
> Initial commit of Shindig Gadget Container JavaScript and Gadget Server.
>
> Includes:
>
> - Gadget Container JavaScript. Code embedded into an arbitrary web
> page enabling it to render and manage Gadgets.
> - Support for rendering using gmodules.com or a Shindig Gadget
> Server
> - Basic IFPC (gadget <-> container communication) support via
> inclusion of Google IFPC library
> - Simple layout management: render in DIV (StaticLayoutManager);
> render multiple Gadgets left-aligned in DIV (FloatLeftLayoutManager)
> - UserPrefs support through JS interface
> - Cookie-based UserPrefs implementation
> - _IG_SetTitle container-side support
> - _IG_AdjustIframeHeight container-side support
> - Sample pages demonstrating all the above functionality
>
> - Gadget Server (written in Java). Web server that processes Gadget
> requests, parsing their spec XML, processing it through a workflow of core
> and extension (<Require>/<Optional>) Features, and serializing output for
> rendering the Gadget to the end user.
> - Core server implementation constructing processing workflows
> out of GadgetFeature objects providing various feature support
> - GadgetFeature interface providing core extensibility mechanism
> for the Gadgets platform; extenders implement GadgetFeature and register
> their implementation with GadgetFeatureRegistry
> - Gadget spec XML parser
> - Simple caching API with in-memory Map-based implementations as
> samples
> - Remote content (eg. HTTP) fetcher interface
> - Basic java.net-based RemoteContentFetcher implementation
> - "Hangman" variable substitution support (eg. __MSG_foo__),
> including BIDI, MSG (message bundles) and UP (user prefs) type variables
> - Early JavaScript-based Feature support through JsLibrary*
> classes
> - Content proxy including JSON support
>
> - A handful of tests for various Server components.
>
> - Maven build support.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Implementing OpenSocial Containers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/opensocial-container?hl=en
-~----------~----~----~----~------~----~------~--~---