Called angel and kaiser

Today’s my opened tabs on Firefox

I was surprised it, if I say so myself…

From left, “mixi Developer Center”, “DeNA Developer’s site” and “GREE Developer Center”.

It became the big market…

Posted:: 05.05.2010
Category:: OpenSocial

Versioned Core Gadget Features

The feature you want to use in your OpenSocial application (“opensocial”, “minimessage”, etc.) is declared by using Require element or Optional element. Then, the way to specify the version you want to use the feature was vague until now. To specify the version definitely, “Versioned Core Gadget Features” specification is added to OpenSocial specification 1.0.

The abstract of this specification is below:

The OpenSocial features (as used in gadget or elements) were defined with the version number as part of the name (“opensocial-0.7″, “opensocial-0.8″, etc.)

This lets them evolve from one version to the next without breaking backwards compatibility, and allows gadgets to clearly declare which version of the API they require.

This convention should be formalized in an explicit version attribute on the and elements, with versions defined for all of the features described by the OpenSocial specification.

As a special case, the core gadget spec format and rendering process should be versioned, with gadgets requesting a specific version of the specification using an attribute on the root element.

For instance, the following two point is added as the format for gadget xml file:

Added @specificationVersion attribute to Module root element.
Added @version attribute to Require and Optional elements.

For example, the usage is the following code:

...

If the specificationVersion or version attribute is omitted, it is regarded as the version 1.0 is specified. Each values can be ordered three numbers by divided using period.

MajorVersion.MinorVersion.PatchVersion

PatchVersion and MinorVersion can be omitted. In the above example, PatchVersion is omitted from the specificationVersion. This thinking about each item is same of the thinking for the general it of the versioning.

Based on this specification, the version number for all features included a name space called “gadgets” are basically 1.0.0.

The unclear point like “The feature called “opensocial” has the version number “opensocial-0.8″. Why is there no version number for osapi?” will be think once more based on this specification.

Posted:: 02.19.2010
Category:: OpenSocial

OSDE 0.7.0 Candidate 1 has been released

I have just released v0.7.0 Candidate 1 of OSDE. This release includes the following features:

The configuration to change the port number of Jetty (Issue 104).
Latency Reduction Tools – Evaluator for web performance (Issue 127).
Latency Reduction Tools – JS Compiler (Issue 180).
Manage/clean gadgets on iGoogle (Issue 155).
Support the HasApp filter and provide Application view to show the information and manage it (Issue 106).
Fix some bugs.

You can install this version using the following update-site for candidate versions:
http://opensocial-development-environment.googlecode.com/svn/update-site-candidate/site.xml

From v0.7.0, the feature and plugin name is changed to “com.googlecode.osde”. If you use the version 0.5.0 or lower, you can’t update OSDE automatically. Please install v0.7.0 Candidate 1 after uninstalling the old version.

Please confirm this version and feel free to feedback any problems.
Thank you for your cooperation.

Posted:: 01.03.2010
Category:: OpenSocial

Published the sequel

“Social Web in 2010″ has been published.

Social Web in 2010 (Sequel) (sorry, Japanese only)
http://gihyo.jp/dev/column/newyear/2010/socialweb-prospect-02

I have mentioned about Ad and some standard specifications in this article.

Posted:: 01.02.2010
Category:: OpenSocial

Social Web 2010

Happy new year! And thank you for your continued help!

So, I thought about how does Social Web of this year grow up. The article has already been published on gihyo.jp, and I would like you to read it.

Social Web 2010 (First) – Sorry, Japanese only.
http://gihyo.jp/dev/column/newyear/2010/socialweb-prospect-01

The second section will be published at about 10:00 on 2nd.

Posted:: 01.01.2010
Category:: OpenSocial

OSDE v0.5.0 stable has been released!

OSDE version 0.5.0 stable just has been released! You can update your OSDE easily by our update-site of OSDE:

http://opensocial-development-environment.googlecode.com/svn/update-site/site.xml

This version allows you to preview and publish your gadget on iGoogle. This function was developed by Albert and a few members in Taipei. Congrats and thank you for your helping and developing! If you would like to develop iGoogle Gadget, OSDE allows you to confirm your gadget both the internal Shindig server and the production server.

We continue to develop many enhancements and new features. If you want to know our roadmap, please see the following page:

http://code.google.com/p/opensocial-development-environment/wiki/Roadmap

Let’s enjoy your coding!

Posted:: 12.18.2009
Category:: OpenSocial

Begin providing life-cycle event!

In mixi platform, life-cycle event which most developers want has been provided.

[About life-cycle event - mixi Developer Center] (Japanese only)
http://developer.mixi.co.jp/appli/pc/lets_enjoy_making_mixiapp/lifecycle_event

If a mixi user install or un-install some application, the thing will be notified to an external server which the developer has. The life-cycle event was implemented on Hi5, and it was taken at the OpenSocial 0.8.

[Enable to receive the life-cycle event from v0.8 - OpenSocial-Japan] (Japanese only)
http://groups.google.co.jp/group/opensocial-japan/browse_thread/thread/baa5590cd35b58da/ba87c004d87508b6?lnk=gst&q=Lifecycle#ba87c004d87508b6

As event types, “addapp” and “removeapp” have been supported on mixi platform. For these, developers can know the situation about installing and un-installing for his/her application. Therefore, developers can do the following things:

Enable to know the usage situation of users.
Enable to clean the obsolete information.

Also, developers can receive the information “who did invite the user?” on the event.addapp type. In most applications, developers store the user list to be selected at the invitation and the user who invited in the database, and give the incentive to the user by the application.

However, developers really could not know “who did invite the user?”. For example, if the user was invited from 2 users for the same application, developers could not judge which is the user who invited you.

In the event.addapp case, if a mixi_invite_from parameter is included, developers can know that the user ID who invited. By this parameter, developers can speficy the user who should give some incentive correctly.

For reducing a load on mixi servers and developer’s servers, requests will be bound as one request. Therefore, please notice that developers can not receive the notification at the real-time.

Life-cycle event is supported for both devices of PC and Mobile. Using this function, I look forward to more great applications developed and published!