Communication Routing

I had this idea while reading this thread about Group IM Etiquette:

/invalid_link.html

I was thinking it would be great if we could selectively custom-route all the various channels of communication we have coming at us to all the various presentation systems that are available.

We have the following distinct types of communication:
- Local chat
- Personal IMs
- Group IMs
- Event anncouncements
- Payment advisories
- Logon/Logoff advisories
- Social advisories (ie notecard traded, rating given to you, object accepted)
- Error advisories (ie "parcel is full", "you do not have permission ...", etc)
- Object chat (via llWhisper, llSay, llShout)
- Object IM (via llInstantMessage)

We have the following presentation systems:
- Chat overlay
- Chat history
- IM window
- Dialog panel (top right, requires click to close)
- Advisory popup (bottom right, automatically closes)
- Email
- Logfile (to be added)

In the attached image, I have shown a grid of how we could potentially configure our communications to reach us.

Notes:
- Some of the email options would probably not be recommended, so I have left the intersections empty in those cases.
- Online Email vs Offline Email lets you determine if you get the message via email only when online, only when offline, or both if both are checked
- Logfile is not currently a feature we have, but I'm hopeful we might get it someday =)
- Communications which use the IM panel but are not IMs from a player/group should simply get a generic "tab" in that window named for their communication category (ie "Errors", "Object Chat", "Online Status", etc).

I totally like this!

It would allow for a degree of customizability that would probobly make a Linux user happy!

Also, I like the way that everything is checkboxes, so you could opt out of everything, or certain things only (aka Recieved/Gave Money Dialogs, I hate them ) and not see "Maxed out number of messages per frame at 200" in your debug window (Ah, So thats why my client is so laggy!).

==Chris

Ahh, good idea.

Excellent idea, Kex.

Lindens - please do implement this when you can.

Would be awsome to have this as long as the complexity could be hidden from newbies

Good point, sounds like this should be slated for the Debug menu

Not until we can pipe it through grep

-Adam

With the rise in the number of events recently, and with the early development phases of 1.4 probably being considered, I'd like to bump this suggestion and re-open discussion.