Documentation & searchable archives?

[Tamlyn Rhodes <ta...@gmail.com>]

Is there a way to search this list's archives?
[http://mail-archives.apache.org/mod_mbox/incubator-shindig-dev/] You
can kinda use google but it's less than ideal.

Also is there any documentation available for the JavaScript APIs
(i.e. gadgets.*)? Even a javadoc-like HTMLization of the js sources
would be useful.

Finally, how much of the iGoogle front-end is Shindig aiming to
implement? For example, does it intend to (or does it already) allow
drag & drop re-ordering of gadgets, serialisation of gadget
settings/positions/states, tabbed views, native RSS support, etc.?

Thanks,

  Tamlyn.

Re: Documentation & searchable archives?

[Vincent Siveton <vi...@gmail.com>]

Hi,

2008/4/8, Tamlyn Rhodes <ta...@gmail.com>:
> Is there a way to search this list's archives?
>  [http://mail-archives.apache.org/mod_mbox/incubator-shindig-dev/] You
>  can kinda use google but it's less than ideal.

See markmail:
http://shindig-dev.markmail.org/

Cheers,

Vincent

>  Also is there any documentation available for the JavaScript APIs
>  (i.e. gadgets.*)? Even a javadoc-like HTMLization of the js sources
>  would be useful.
>
>  Finally, how much of the iGoogle front-end is Shindig aiming to
>  implement? For example, does it intend to (or does it already) allow
>  drag & drop re-ordering of gadgets, serialisation of gadget
>  settings/positions/states, tabbed views, native RSS support, etc.?
>
>  Thanks,
>
>
>   Tamlyn.
>

Re: Documentation & searchable archives?

[Tamlyn Rhodes <ta...@gmail.com>]

Great stuff. Thanks!

  T.

Re: Documentation & searchable archives?

[John Hjelmstad <fa...@google.com>]

> Also is there any documentation available for the JavaScript APIs
> (i.e. gadgets.*)? Even a javadoc-like HTMLization of the js sources
> would be useful.


http://code.google.com/apis/opensocial/docs/index.html
API Reference (v0.7) -> gadgets (core) and gadgets (feature-specific)

Finally, how much of the iGoogle front-end is Shindig aiming to
> implement? For example, does it intend to (or does it already) allow
> drag & drop re-ordering of gadgets, serialisation of gadget
> settings/positions/states, tabbed views, native RSS support, etc.?


This is the subject of much discussion right now. I wouldn't state the goal
in terms of "implementing iGoogle" functionality so much as making it easy
for containers to integrate gadgets support while customizing their user
experience. The concrete idea is to replace javascript/container/gadgets.js
with a much more modular and flexible implementation that takes in layout
management, persistence, rendering, logging, and other such plug-ins, each
with its own defined interface and default implementations. A few such
implementations could be plugged together to create an iGoogle-like (eg.
portal-like) experience... At present there's largely some exploratory work
done by individuals thinking about the problem.

John


>
>
> Thanks,
>
>  Tamlyn.
>