Difference between revisions of "User:Dale Glass"

From Second Life Wiki
Jump to navigation Jump to search
Line 3: Line 3:
Currently working on adding an avatar scanner to the SL client.
Currently working on adding an avatar scanner to the SL client.


http://daleglass.net/images/screenshots/avlist3_001.jpg
http://daleglass.net/images/screenshots/avlist6_001.jpg


Features:
Features:
Line 20: Line 20:
* Automatically retrieves the birth date, account type and payment data for all users shown. The data is of course cached, and if this is too much of an extra load, I'll implement a permanent on-disk cache. If data doesn't arrive, it will retry with an exponential backoff (starting from 1 minute, doubling until 30 minutes)
* Automatically retrieves the birth date, account type and payment data for all users shown. The data is of course cached, and if this is too much of an extra load, I'll implement a permanent on-disk cache. If data doesn't arrive, it will retry with an exponential backoff (starting from 1 minute, doubling until 30 minutes)


* Displays activity status: new, left the area, emitting particles, moving, playing sound
* Allows moving the camera to the avatar with a double click, as well as cycling the camera between all or only the marked avatars
* Partial TrustNet integration: retrieves scores, but can't rate yet


What is not done yet, but will be:
What is not done yet, but will be:
Line 31: Line 36:
* Buttons for administrative actions such as ban/eject/freeze/etc
* Buttons for administrative actions such as ban/eject/freeze/etc


* Longer term, a display (as an icon for instance) indicating whether the avatar is playing a sound, rezzing objects, or emitting particles.
* Add activity status for typing and rezzing objects


* Also longer term, option to make the client stop rendering an avatar completely.
* Also longer term, option to make the client stop rendering an avatar completely.

Revision as of 15:25, 10 March 2007

Evil Scripter and RL programmer.

Currently working on adding an avatar scanner to the SL client.

http://daleglass.net/images/screenshots/avlist6_001.jpg

Features:

  • Shows a list of all avatars known to the client. This can be easily more than a standard 96m scanner, and seems to depend on rendering distance.
  • Keeps an internal list of avatars, and continues showing avatars that disappeared in the list for several seconds to give people time to perform some action on them (intended to make it easier to deal with griefers that do something nasty, then teleport out)
  • Shows Linden accounts in bold. This will be expanded later to highlight people who are very new, don't have a credit card on file, etc depending on user configuration.
  • Allows easy access to IM, profiles, etc
  • Allows to start a conference to multiple avatars around you, the same way it works in the friends list.
  • Allows tracking an avatar by placing a beacon on it. In the case the selected avatar isn't a friend who gave map location permission, it works anyway by placing a beacon on the avatar's last known position. This of course only works so long the avatar being tracked is near enough to be seen by the user.
  • Automatically retrieves the birth date, account type and payment data for all users shown. The data is of course cached, and if this is too much of an extra load, I'll implement a permanent on-disk cache. If data doesn't arrive, it will retry with an exponential backoff (starting from 1 minute, doubling until 30 minutes)
  • Displays activity status: new, left the area, emitting particles, moving, playing sound
  • Allows moving the camera to the avatar with a double click, as well as cycling the camera between all or only the marked avatars
  • Partial TrustNet integration: retrieves scores, but can't rate yet

What is not done yet, but will be:

  • Integration with my TrustNet system. See here for details:

http://daleglass.net/tikiwiki/tiki-index.php?page=TrustNetAvatarScanner http://daleglass.net/tikiwiki/tiki-index.php?page=HowTrustNetWorks

  • Integration with resident-run databases. For example, I've been asked whether I could make it automatically query a website with a database of buyers to be able to tell people who are using avatars made with copybot, for instance.
  • Buttons for administrative actions such as ban/eject/freeze/etc
  • Add activity status for typing and rezzing objects
  • Also longer term, option to make the client stop rendering an avatar completely.