--
You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
To post to this group, send email to opensocial-an...@googlegroups.com.
To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.
To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
To post to this group, send email to opensocial-an...@googlegroups.com.
To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.
> ...
>
> read more »
--
You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
To post to this group, send email to opensocial-an...@googlegroups.com.
To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.
> ...
>
> read more ?
<script language=”Javascript”>
if (navigator.geolocation) {
navigator.geolocation.getCurrentPosition(function(position) {
ZoomToLocation(position.coords.latitude, position.coords.longitude);
});
}
else {
if (document.getElementById(“GeoAPI”)) {
document.getElementById(“GeoAPI”).innerHTML = “I’m sorry but Geolocation services are not supported by your browser – use Firefox 3.5″;
document.getElementById(“GeoAPI”).style.color = “#FF0000″;
}
}
function ZoomToLocation (mylat, mylong) {
if (document.getElementById(“GeoAPI”)) {
//Implement a zoom to location
document.getElementById(“GeoAPI”).innerHTML = “mylat: ” + mylat + “ mylong: ” + mylong;
}
}
</script>
> ...
>
> read more »
--
You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
To post to this group, send email to opensocial-an...@googlegroups.com.
To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.
I'm sorry my response too late because recently I was very busy...
Currently, I'm developing the patch code set for Shindig to support
our wap extension. I intend to complete this task by the end of this
month.
Well, we don't have the conclusion yet whether we should use or not
the type attribute with "wap" value to apply using the wap extension
to one content element. However, I think that the type attribute
should be used, the specific view name (ex. wapcanvas) should not be
used. The code I'm developing now is based on the approach of using
the type attribute.
Give me some time to develop the patch, please.
Thanks,
-Yoichiro
> --
> You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
> To post to this group, send email to opensocial-an...@googlegroups.com.
> To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.
>
>
--
Yoichiro Tanaka
Email: yoic...@eisbahn.jp
Blog: http://www.eisbahn.jp/yoichiro
Yes, I agree your suggestion, and also hope that the mobile proposal
should be divided two proposals. Mark, how do you think about this?
Thanks,
-Yoichiro