[sldev] Notifications redesign
Argent Stonecutter
secret.argent at gmail.com
Wed Feb 13 05:57:16 PST 2008
On 2008-02-13, at 01:51, Kamilion wrote:
> Why not split all of the non-chat out from Near Me to an Event Log
> tab?
I have mixed feelings about that, lest it suffer the fate of being
hidden and ignored, but that would also work well. If it was hidden,
the user would get something like the current dialogs. If displayed,
the dialogs would be subsumed in the event log.
> Anything that can be answered via script dialogs should be highlighted
> like a URL and clickable.
> [18:32] Kamilion Schnook has offered you "Object". Accept? [YES] [NO]
> In this example, Kamilion Schnook should be highlighted as a URL
> (Zi's patches).
> YES should be highlighted as a URL and accepts the item.
> NO should be highlighted as a URL and declines the item.
I think, if possible, that these should be buttons (since they are
actions) rather than URLS (links), and that once clicked they should
go away. The event would perhaps change to:
[18:32] Kamilion Schnook has offered you "Object". (18:33 - Accepted)
Alternatively, the whole line could be a link that brings up the
dialog (or replaces the currently displayed dialog, if there is one).
> Eventually, this could be extended to script dialogs as well, so you
> could see neat stuff like:
> [18:33] Object Dialog - Item Server: Please make a selection... [Reset
> Main] [Reset Monitor] [Reset Display] [Trigger HTTP] [Update
> Inventory]
One issue here is that people use dialogs as menus, and expect the
dialog to come up when clicked, and they DO work well for that. In
the absence of multiple pending events, then, I believe the dialog
interface should remain by default. The existing three chevrons would
cycle through unacknowledged dialogs. An additional button opposite
"(ignore)" would bring up the event log.
Allow me to suggest that the dialog itself be more customizable,
perhaps even in XML:
llXMLDialog(string title, string message, integer channel);
llXMLDialog("Item server", "Reset: <button value='reset'>All</
><button value='rmon'>Monitor</><button value='rdisp'>Display</
><br><url=http://whatever>View in Web</><br><button='update'>Update
Inventory</>", 33);
To avoid people hiding embarrassing messages behind these buttons, it
should be restricted from allowing chat on channel 0?
> Prefix events with a type.
Yes.
The internal structure of the log should not be textual, or if it is
textual it's not necessarily what's displayed. Perhaps XML?
<message type="Voice Notification" time=017627846129>Connected to in-
world voice channel</>
<message type="Estate Notification" time=017672362476><source
type=agent name="Kamillion Schnook"/>Hey guys, you're lagging the
sim, triggering a restart in two minutes.</>
That would fit well with llXMLDialog. :)
> Personally, I'd like to see the L$ spent/received notification move to
> being a text event versus it's current nature as a Notification
> dialog. It's really a pain in the butt to pay a vendor then end up
> clicking Decline on the item offer when you're aiming to dismiss the
> payment dialog instead.
I brought this up during the debate over PERMISSION_DEBIT. System
dialogs should all be slightly different so that none of them have a
dismiss item. Making these dialogs schwoop down into the event log
when you open the event log would resolve that problem.
> And I can't stress this one enough: Release Keys needs to be moved off
> into a menu.
That is already going to happen, according to the Jira and comments
in the blog.
More information about the SLDev
mailing list