New destination guide for grids

There is a new destination guide available for any hypergrid-enabled grid: Hyperica Destination Guide.

Hyperica Destination Guide

To add the Hyperica Destination Guide as the default guide for your grid, simply edit your Robust.ini or Robust.HG.ini file. In the “[LoginService]” section there is a “DestinationGuide” parameter which can be used to communicate a URL to use for the destination guide for “V3″ style viewers.

Here is the code you would use:

   ; For V3 destination guide
   DestinationGuide = "http://www.hyperica.com/destination-guide"

What’s in the guide?

The Hyperica Destination Guide is actually composed of many pages. On the starting page, “Categories,” there are seven boxes.

“Most Popular Grids” takes you to another page, with the 15 hypergrid-enabled grids ranked by active monthly users.

“All Grids” takes you to a page with an alphabetical breakdown of all the major grids, and the “Hyperica Hyperport” button initiates a teleport to Hyperica.

“Events,” “Shopping,” “Free Land” and “Education” categories are grayed out because I don’t have those pages set up yet. If you would like to suggest a destination for one of these locations, email me at [email protected]. If you have a snapshot of the destination that would look good in a tiny size on a dark gray background, even better.

I’m also considering adding categories for “Sandboxes,” “Hyperports,” “More Categories,” and “Adult” and “Gambling.” The last two would be hidden under “More Categories” to keep people from being shocked — shocked! — to find out that there’s this kind of activity going on in OpenSim.

The Hyperica Destination Guide in the Firestorm viewer.

The Hyperica Destination Guide in the Firestorm viewer.

The Hyperica Destination Guide is based loosely on the Second Life Destination Guide, except that the pages are fully self-contained to make them easier to copy and adapt. There are no external stylesheets or dependencies — feel free to copy and paste and adapt for your own grid.

Now that I have the guide in place, I can’t believe I’ve ever lived without it. It is so easy to use it’s ridiculous.

I prefer using the guide in the Firestorm viewer because I can easily add the Destination Guide button to the bottom of my viewer screen. All I had to do was right-click on any of the buttons at the bottom, choose “Toolbar buttons” from the pop-up menu, and then drag the Destination Guide button to where I wanted it.

This button opens the Destination Guide window.

This button opens the Destination Guide window.

I haven’t figured out how to do this in Singularity.

Coding the teleport links

While creating this guide, I spent quite a bit of time researching teleport links and testing out the various coding options.

The alternatives are as follows:

  • secondlife://http|!!seleacore.com|8002+selea%27s+world
  • secondlife:///app/teleport/hg.osgrid.org:80:Lbsa%20Plaza
  • secondlife://hg.osgrid.org:80/Wizard/169/203/17
  • hop:///app/teleport/hg.osgrid.org:80:Lbsa%20Plaza
  • hop://hg.osgrid.org:80/Wizard/169/203/17
  • hop:///hg.osgrid.org:80:Wright Plaza/
  • https://osgrid/region/Sandbox%20Area/128/57/24

Not all work in all the viewers.

Fortunately, as I recently found out, the majority of hypergrid travelers use the Firestorm viewer, with Singularity in distant second place and other viewers having only a couple of percentage points of market share or less.

That means that, as far as the Destination Guide is concerned, the only viewers worth worrying about are Firestorm and Singularity.

And what I’ve found is that it’s this format that currently works in both of these viewers, without any error messages or configuration issues:

  • secondlife:///app/teleport/hg.osgrid.org:80:lbsa plaza

Note that there are three slashes after the first colon.

I will now use the following format for all my hypergrid links:

In other words, I use the plain hypergrid address as the text, so that people can copy-and-paste into their map. And for the hyperlink, I use the “secondlife:///app/teleport/” so if they just click on it, it takes them to the destination.

If you are not currently logged into a viewer when clicking on a link, it will just take you to your default viewer’s login screen.

The default viewer, by the way, seems to be whichever one you installed last. Since, in my case, this happened to be Kokua, I had to uninstall Firestorm and then install it again before it started acting like my default viewer for browser links.

maria@hypergridbusiness.com'

Maria Korolov

Maria Korolov is editor and publisher of Hypergrid Business. She has been a journalist for more than twenty years and has worked for the Chicago Tribune, Reuters, and Computerworld and has reported from over a dozen countries, including Russia and China.

  • I just put the destination guide on an in-world prim, and was able to navigate with it and travel around — whoo hoo!

  • Here are the numbers for this to scale right:

    Object: 1.9 m wide, 0.67 m high

    Texture: materials is media
    Auto Zoom, Auto Scale: not checked
    Auto Play: Checked

    Horizontal Scale: 0.63
    Vertical Scale: 0.2
    Horizontal offset: -0.18
    Vertical offset: 0.4

    • Another tip — to turn off the navigation bar at the top, go to the media settings, customize, and turn off the control bar — while keeping the interactivity setting checked.

  • I just put a free-to-copy copy of this kiosk on Hyperica — hg.hyperica.com:8022 — for anyone to play with.

    Please let me know if it works, if there are any broken links, etc…! Thanks!

  • Nicky Perian

    https://dl.dropboxusercontent.com/u/7833186/DestinationsGuideiIconCapture.JPG
    As shown, Kokua’s default buttons have the destinations guide installed to the left second down. Web related buttons are on the left bar and stacked from the bottom.
    It comes that way when installed and of course any button can be dragged and dropped to the bottom or right and may be rearranged within the bar as desired.

  • Geir Nøklebye

    Nice work Maria. Thanks for running with it!

  • markjohnwiseman

    Good going Hyperica 🙂 I concur on the format of gridurl:port:region to standardize on as a format. It’s simple, and the landing coordinates can be up to the region owner as they can (should) set a default landing spot.

    • Also, I think specific coordinates are important on Second Life, where land costs are astronomical.

      But in OpenSim, there is, at this point, really no reason why anyone should be hiding shops or venues or other interesting destinations in little out-of-the-way corners or up in the sky somewhere.

      Unless the whole point of the region is for people to have fun looking for them.

      • Geir Nøklebye

        Keep the coordinates too as part of the standard as there are multiple reasons to land avatars on set locations that is not necessarily the default landing point for the sim. It could be an event entrance, multiple stores, a sky or underwater location, specific floor – what have you.

  • Casias Falta

    Hey this works great. btw i run a diva distro standalone and so the [LoginService] section that you put the new code in is found in MyWorld.ini since I don’t have any Robust. But it work just the same 🙂

  • I just added an “events” section featuring some regular weekly events, and a “hyperports” section with Hyperica, Sanctuary, Soloton and OpenSimWorld.

    • Geir Nøklebye

      You might want to put in the weekly developer’s meeting too. I guess JustinCC has the details.

      • IDEALLY, what I would want is to have a central metaverse calendar, with upcoming events, snapshots, and hypergrid addresses, that I can simply pull the the upcoming events from…

        THAT’s what I should be coding next, right!

        A calendar app for WordPress that I could pull all the hypergrid calendars into, and have my assistant set photos and hypergrid addresses for those that don’t have any!

        • Geir Nøklebye

          Steady now! One project at the time. 😉

  • Seth Nygard

    The destination guide is a great addition. One suggestion however, is to add an auto-resize container for the guide so it auto-adjusts to fit the window size if the user changes it in their viewer.

    I use Firestorm on a wide screen monitor so frequently widen windows when I can, which it is easy to do for the destination guide. However with its current HTML setup it remains a fixed size so I simply have a larger window with empty space. If you look at the destination guide for SL it does auto-scale to fill the window width.

    • Arrgh! I didn’t know you could resize the window! It took so much fiddling to get it to look right!

      LOL….

      Okay, I’ll work on it! Anybody have any CSS advice on how to do it — I welcome your input!

      • Geir Nøklebye

        Check if the LL window is resizable. If it is, you should have the CSS there?

        • Their CSS is a muddled mess of multiple interrelated stylesheets and divs piled on top of divs piled on top of divs… mine is a lean, mean, short snippet of code that’s embedded right in the page.

          • Seth Nygard

            Although there are better ways to do it, if you make the following changes it should work;
            In your body background change to; body {background-color:#383838; width: 95%;}
            for the main body add an addition div container to encapsulate the body contents;

            Then change the width of the two div containers you are using to auto as well. Make sure to keep these original divs contained within the new div container we added.

            The quick mock-up I did appears to give the expected results with minimal changes to what you already did.

          • Seth — you’re a genius! I added the width CSS to body, and took out the widths in the divs themselves, and it worked. (I missed the part where you had me add another div container — but it doesn’t look like it was needed.)

            Check it out. I just made the changes to all the Destination guide pages.

          • Seth Nygard

            I just verified your change is working properly in Firestorm.

            Glad I could help.

          • XMIR Grid

            Their seemed like a mess – absolutely. I just thought you by now had decoded it sufficiently to also be able to get the resize bit of it without too much effort. 😉