The other main difference is that this one was generated with individual images and letting the browser do the layering. So the gravel is one layer, the grass is another, the bushes are another, the trees are another... The gates and well are put in independently. The building... well, that's a bit more complicated...
The building was not clickable when I put it below the treeline because there was a transparent image above it consuming the clicks. To get this to work, I created two divs in the same place with different z-indexes. The bottom one had the img. The top one had a href tag with the same size of transparent image. That allowed it to APPEAR that you were clicking on the building when in actuality you were clicking on nothing. Clicking on the building pops up a fb:dialog.
Also, in the top left there is a link. If you click that link repeatedly, it will toggle the grid on and off. That is done using the facebook clicktotoggle event.
Overall, the biggest issue with this one is that the map wasn't zoomed out as far as in the previous test. I think we need to zoom out a bit in order to appear to have more real estate per screen refresh.
Scale is also something to consider. If you have something to always compare with, then you can keep it more realistic or items that are to scale with all other items.
ReplyDeleteTrue. The scale will be different for different types of maps. For example, a world map and a inside-the-house map.
ReplyDeleteIt would be good to determine how big '1 grid square/hex' is for each scenario though.
From the Grid blog, it looks like the square one is 22x19 on the screen at a time and the hex one is 25x39 (each overlaps it's neighbors).
I'd have to determine how many feet/meters per square-or-hex for:
1. inside a building
2. inside the town
3. in a dungeon
4. out in the countryside
5. viewing the global map
At minimum I'd need #1 and #2 immediately.