Re: Re: Questions...

[Stuart Booth]

On Thu, 29 May 2003 09:27:18 -0000, "Patrick Lidstone"
<<a
href="/group/xAP_developer/post?postID=ly3CtsB49t5pvytvwfpG_b2wnduccGPMW_XNlrMSVj5afJM1arr0KhSw0e2qpcQGL0kTZfe1oqLJdofnC5c">patrick@l...</a>>
wrote:

>> A "priority" flag might be an idea here, with a general
guideline
>> that, say:
>>
>> - priority=1 .... sufficient to send an SMS
>> - priority=2 .... sufficient to override current displays
>> - priority=3 .... general information
>
>This is a bad idea because *you* as the programmer are making
>assumptions about the fact that *I* as an end user might deem a
>particular event as being high priority.

An event occurs. Another application determines what to do about that
event, such as display a message. Isn't this where your own 'house
logic' is applied anyway, to build the display message, with its
priority field. It is also where the formatting of the display message
is determined, again allowing for user input to suit their
preferences/requirements.

This seems to me to be the same thing as your scenario #1.

>Scenario 1: I program my SMS sender to intercept alert class messages
>from a specific device, because that's what *I* as the end user want
>to do

S
--
Stuart Booth
xAPFramework.net - a reusable xAP framework for .net

<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>
<a
href="/group/xAP_developer/post?postID=wzFnXt5K7wnn4qWycgKrig07qso0361N51kat0-5ysw4GtSrQss9eFxBXgDov06XAJhejytSeLsyLDBJxfekRRA">stuart@x...</a>