Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(24)

Issue 144082: Deprecate redundant opensocial.* objects

Can't Edit
Can't Publish+Mail
Start Review
Created:
16 years, 8 months ago by Lane
Modified:
16 years, 8 months ago
Reviewers:
opensocial-and-gadgets-spec
CC:
Arne Roomann-Kurrik
Base URL:
http://opensocial-resources.googlecode.com/svn/spec/draft/
Visibility:
Public.

Patch Set 1 #

Patch Set 2 : Moved deprecated methods to their own file #

Unified diffs Side-by-side diffs Delta from patch set Stats (+4400 lines, -4129 lines) Patch
A OpenSocial-Deprecated-JavaScript-API.xml View 1 chunk +4395 lines, -0 lines 0 comments Download
M OpenSocial-Specification.xml View 1 11 chunks +5 lines, -4129 lines 0 comments Download

Messages

Total messages: 1
Lane
16 years, 8 months ago (2009-11-04 00:27:24 UTC) #1
I've moved the redundant method into a new file "OpenSocial Deprecated
JavaScript API", and added links to the osapi methods that replace them.

I captured a few issues here:
http://wiki.opensocial.org/index.php?title=Deprecate_redundant_opensocial.%2A...

Still a fair amount of work to do on this patch, but wanted to get some
high-level input before going further.

Open Question:  Should I rename this new file to be the "OpenSocial JavaScript
API" and move the rest of the osapi.* and opensocial.* methods under the same
roof?

I'm leaning toward this because 1) the "OpenSocial Specification" file can then
be soley focused on defining compliance and extensions and 2) IMO, xrefs are
better than erefs (but I don't feel strongly).  Thoughts?

-Lane
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b