Anyone who’s been poking around the SLOpenID group for a while will probably know about the SLNTPoHTTP protocol I use to power my multi-timezone clocks. We’ve decided to release a much easier to use unauthenticated version of the service (the LSL client for the authenticated service is designed for use with a payload of multiple requests for multiple clocks at once), so Residents can make LSL scripts to make it easier to figure out what time it is in another timezone.
I’ve posted the LSL script for the authenticated SLNTPoHTTP service on the SL Wiki.
We now have an LLSD version of the JSON SL Maps API. It’s pretty much the same as the JSON one, except it’s along the lines of http://services.slopenid.net/grid-map-llsd/offset2region/901/901 vs http://services.slopenid.net/grid-map-json/offset2region/901/901
I added 1:64, 1:128 and 1:256 scale levels to the SLOpenID SL Maps API. You can view the world map at these scales in the following documents:
Yes this means that you can view the world map where each region takes up a pixel. Yes I’m aware my references to “scale” are slightly off- I’m referring to the square root of the number of regions contained in each texture.
At the moment, my rather lacklusture implementation of webmap API (I’m not as good with JS as I should be) doesn’t do any checking for non-existent images, hence the alt text displayed when you zoom right out. This is a simple case of running an is_file() check before spitting out the API results, so it should be fixed soon. Once it’s fixed, I’ll update the PHP API wrapper with any fixes
Why is Marv blogging this instead of making a group notice ?
Quite simply because the group notices are too small.
Why is SLOpenID releasing an API for the SL World Map? I thought we already had one
Take a look at the source code for the mapapi.js file. It’s too complicated for it’s own good.
What SLOpenID plans do with it’s SL Maps API is along the lines of what XHTML did for HTML; SLOpenID plans seperate design from data, simplifying things a hell of a lot in the process.
Read the rest of this entry »