Subject: RE: [Sipping] Comments on App Interaction Framework

From: "Eric Burger" <[email-masked]>
Date: Fri, 6 Dec 2002 15:11:14 -0500

This scheme is not workable in practice.  The example given assumes cooperation among the application developers.  That is, the recording app knows it has to prefix its commands with a '*' and the pre-paid app knows it has to prefix its commands with a '#'.  However, what if someone else wants to use '*'?  There is no way of knowing what script is loaded and what will come later.

Moreover, we can't just use the key as an escape.  From a user interface point of view, the prompt needs to know the focus key.  As you indicated, the prompt will be something like "to start recording, press *1; to stop, press *2".  The problem is that if we separate out the focus key, the prompt becomes "to start recording, press 1; to stop, press 2".  It gets worse if the user can set their own focus key.  The prompt may say "to start recording, press *1; to stop, press *2", yet the phone may expect "focus-1"-1 and "focus-1"-2.  That conflicts with the prompt and is confusing.

> -----Original Message----- From: Vijay K. Gurbani [mailto:[email-masked]]
[snip]
> Section 7.1, paragraph 6: a case can be made for primitive devices
> (12-button keypad) that the focus is the key being pressed.  When the
> pre-paid/recording application is interacting with a primitive device,
> some how, the user controlling the devices can be told that "press #1
> to start recording, #2 to stop recording and *1 to hear your pre-paid
> balance".  Certainly not elegant, but by pressing a # the focus shifts
> to the recording application and by pressing a * the focus
> shifts to the pre-paid application.  But clearly, this is an academic
> exercise, since behind the scenes, both the UIs will get the stimulus
> and decide if it is for them or not, depending on a # or *.  This is
> definitely a drawback since in richer interfaces, only one UI will
> get the stimulus.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP