[
https://issues.apache.org/jira/browse/SHINDIG-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568898#action_12568898
]
Kevin Brown commented on SHINDIG-69:
------------------------------------
Sorry about that, the correct URL is:
http://code.google.com/apis/gadgets/docs/spec.html
"Google Gadgets" is not quite the same thing as the gadgets specification --
it's Google's (specifically, iGoogle's, since other google properties only
support what's in the gadgets spec) deployment of gadgets. gadgets and open
social are open standards much like HTML or javascript. Google does not dictate
these standards -- we simply have stewardship over their publication at this
point in time (until we can figure out a better arrangement). Discussion of the
specifications takes place at regular meetings, and there is a public
discussion group (though this was newly created to ease some confusion).
At this time we plan on supporting all APIs required by the spec (everything
marked "core"), any will also probably support any features added in the
"highly recommended" section. We will be trying as much as possible to avoid
adding any new features that are gadget author facing that do not have a formal
specification. iGoogle will continue to support drag, grid, and other features
that haven't been standardized for a very long time most likely, but that
doesn't affect what Shindig does (well, not directly; in the spirit of full
disclosure it's worth noting that igoogle is in the process of becoming a
shindig user and will therefore naturally have more input into the development
of the project in the future).
Someone could, for instance, implement a 'drag' or 'grid' feature in the same
vein as the other gadgets APIs in shindig before formally submitting it for
consideration in the spec discussion group.
Individual sites are free to implement any feature that they want, which is why
we have the <Require> and <Optional> tags -- we don't want a proliferation of
this, of course, but it's OK to extend the platform in this way.
As far as drag and grid go, specifically:
- When the specs were being formalized, the original plan was to not include
anything that didn't require any server side support. If it could be loaded via
a script tag from an external server without any knowledge of the containing
page, it shouldn't be in the spec.
- After a while, it became apparent that some of the UI type libraries (tabs
and minimessage, specifically) were so commonly used that we should publish a
formal spec for them, but not require support. This is where the "highly
recommended" features came from.
- grid, drag, and some others weren't commonly used enough to worry about
formal specifications at this point in time, and viable alternatives already
exist in robust javascript libraries such as YUI and dojo.
These APIs may be added to the spec in the future, but since they aren't there
now there's not much that we can do about it, other than adding more wonkly
kludges such as how we dealt with all the gadgets that require the "analytics"
feature.
> shindig does not support grid feature
> -------------------------------------
>
> Key: SHINDIG-69
> URL: https://issues.apache.org/jira/browse/SHINDIG-69
> Project: Shindig
> Issue Type: Improvement
> Components: Features
> Reporter: Martin Webb
> Assignee: Kevin Brown
> Attachments: grid.xml, grid_advanced.xml
>
>
> See test files attached to: https://issues.apache.org/jira/browse/SHINDIG-62
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
