8:28 a.m.
Up for comment is the Sim Application Toolkit API proposal for oFono. It is
largely based on Andrew's API proposal with several changes in areas I felt
needed further attention. I'd like all interested to comment, what looks
good, what looks crummy? Is anything missing?
Please note that the proposal only covers Setup Menu, Setup Idle Mode Text,
Select Item, Display Text, Get Inkey and Get Input proactive commands.
Also, several aspects of these commands are explicitly ignored, e.g. the user
help system.
---
doc/stk-api.txt | 162 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 162 insertions(+), 0 deletions(-)
create mode 100644 doc/stk-api.txt
diff --git a/doc/stk-api.txt b/doc/stk-api.txt
new file mode 100644
index 0000000..96bf710
--- /dev/null
+++ b/doc/stk-api.txt
@@ -0,0 +1,162 @@
+SimToolkit Hierarchy
+===============
+
+Service org.ofono
+Interface org.ofono.SimToolkit
+Object path [variable prefix]/{modem0,modem1,...}
+
+Methods dict GetProperties()
+
+ Returns properties for the SimToolkit object. See the
+ properties section for available properties.
+
+ Possible Errors: [service].Error.InvalidArguments
+
+ void RegisterAgent(object path)
+
+ Registers a default agent to be used for SIM initiated
+ actions such as Display Text, Get Inkey or Get Input.
+ These can typically occur when a special SMS is
+ received and might not involve interaction from the
+ user.
+
+ Possible Errors: [service].Error.InvalidArguments
+ [service].Error.InvalidFormat
+ [service].Error.InUse
+
+ void UnregisterAgent(object path)
+
+ Unregisters the default agent. If no agent is
+ registered then unsolicited commands from the SIM
+ are rejected.
+
+ Possible Errors: [service].Error.InvalidArguments
+ [service].Error.InvalidFormat
+ [service].Error.NotFound
+ [service].Error.NotAuthorized
+
+Properties string IdleText
+
+ Contains the text to be used when the home screen is
+ idle. This text is set by the SIM and can be changed
+ at any time.
+
+ array{string} MainMenuItems
+
+ Contains the items that make up the main menu. This
+ is populated by the SIM when it sends the Setup Menu
+ Proactive Command. The main menu is always available,
+ but its contents can be changed at any time.
+
+ array{array{bytes}} MainMenuIcons
+
+ Contains the icons associated with the main menu items.
+
+ string MainMenuTitle
+
+ Contains the title of the main menu.
+
+SimToolkitAgent Hierarchy
+===============
+
+Service unique name
+Interface org.ofono.SimToolkitAgent
+Object path freely definable
+
+Methods byte SelectItem(string title, array{string} items,
+ array{array{byte}} icons, byte default)
+
+ Tells the agent to ask the user to select an item
+ from the menu. This function should return the index
+ of the item or an error given below:
+
+ Possible Errors: [service].Error.SimToolkit.GoBack
+
+ Implementation notes:
+
+ - Data / Navigation type not indicated
+ - Soft key preferred not indicated
+ - Help available ignored
+
+ void DisplayText(string text, boolean urgent)
+
+ Tells the agent to display text from the SIM. The
+ boolean urgent parameter tells the agent whether this
+ is an urgent message and all other messages should be
+ cleared prior to the display of this text.
+
+ Possible Errors: [service].Error.SimToolkit.GoBack
+
+ Implementation notes:
+
+ - High / normal priority indicated by urgent
+ - clear / wait for user handled by setting a higher
+ timeout in the case of wait for user flag and using
+ the Cancel() method appropriately. If the agent
+ returns earlier from this method call, a terminal
+ response is sent.
+ - Immediate Response indication is handled internally,
+ terminal response is sent immediately and no other
+ indication is given to the user / agent. Response
+ from this method call is ignored and an infinite
+ timeout is used for the method call. Once another
+ proactive command arrives, and the DisplayText is
+ still pending, Cancel() is called.
+
+ string GetInput(string alpha, array{byte} icon,
+ string default, byte min, byte max,
+ boolean hide_typing)
+
+ Tells the agent to request an input string from the
+ user. The alpha parameter and icon gives context to
+ the user. The default string contains the suggested
+ default by the SIM. The min and max parameters contain
+ how many characters the user should enter. The
+ parameter hide_typing indicates whether user's typing
+ should be opaque.
+
+ Possible Errors: [service].Error.SimToolkit.GoBack
+
+ string GetDigits(string alpha, array{byte} icon,
+ string default, byte min, byte max,
+ boolean hide_typing)
+
+ Same as GetInput but only digit characters (0-9, *#+)
+ are expected.
+
+ Possible Errors: [service].Error.SimToolkit.GoBack
+
+ string GetKey(string alpha, array{byte} icon)
+
+ Tells the agent to request a single input key from
+ the user. The alpha parameter contains the context
+ for the request.
+
+ Possible Errors: [service].Error.SimToolkit.GoBack
+
+ string GetDigit(string alpha, array{byte} icon)
+
+ Same as above, but only digits (0-9, *#+) are
+ expected.
+
+ Possible Errors: [service].Error.SimToolkit.GoBack
+
+ boolean GetConfirmation(string alpha, array{byte} icon)
+
+ Asks the agent to get confirmation from the user.
+
+ Possible Errors: [service].Error.SimToolkit.GoBack
+
+ void Cancel()
+
+ Asks the agent to cancel any ongoing operation in
+ progress. This is usually either because the agent
+ is taking too long to respond or the Sim Application
+ has terminated the session.
+
+ void Release()
+
+ Agent is being released, possibly because of oFono
+ terminating, SimToolkit interface torn down or modem
+ off. If the agent is registered as a global agent,
+ no UnregisterAgent call is expected.
--
1.7.0.4
8:06 a.m.
On Mon, 19 Jul 2010 17:28:48 -0500
Denis Kenzior <denkenz(a)gmail.com> wrote:
Up for comment is the Sim Application Toolkit API proposal for
oFono. It is largely based on Andrew's API proposal with several
changes in areas I felt needed further attention. I'd like all
interested to comment, what looks good, what looks crummy? Is
anything missing?
General comments, from the perspective of one who may end writing an
STK Agent app/ui in MeeGo:
- Having not read the full spec, what (if any) considerations need to
be made for locales and multi-byte characters that could be entered
if the UI is running in a multi-byte locale?
Addendum: I now see the spec has the LANGUAGE NOTIFICATION Proactive
Command. Any early ideas on if/how this would be implemented and
what should be done from a UI perspective if the language does not
match the current runtime locale and/or language, esp if they differ
in directionality (right-to-left vs. left-to-right)?
- Same for translations? Do the strings provided need to be
translated, or is that left as a function of the SIM vendor and the
region the card is coded for?
If the LANGUAGE NOTIFICATION *is* implemented, then I assume the
agent writer would not have to deal with translation issues for text
provided by the SIM application. I would assume strings following a
change in language notification would be "pre-translated"... fair
assumption?
- Does the spec, or will ofono, define the max length of the strings
passed for any properties that will result in the display of text on
screen?
+SimToolkit Hierarchy
+===============
+
+Service org.ofono
+Interface org.ofono.SimToolkit
- I take it this interface is independent of the org.ofono.manager and
org.ofono.modem interfaces?
+Object path [variable prefix]/{modem0,modem1,...}
- Does this modem path map exactly to the path provided through
org.ofono.manager.GetProperties() or can/will it be completely
orthogonal to it?
- If closely tied to the "Modems" propertied in the Manager
interface, what is the effect (if any) to changes in the "Powered"
state on the modem when triggered via a call to
org.ofono.Modem.SetProperties() for that modem path?
Will it trigger a Unregister or PropertyChanged signal to the agent
and/or toolkit interfaces?
+
+Methods dict GetProperties()
+
+ Returns properties for the SimToolkit
object. See the
+ properties section for available properties.
+
+ Possible Errors:
[service].Error.InvalidArguments +
+ void RegisterAgent(object path)
+
+ Registers a default agent to be used for SIM
initiated
+ actions such as Display Text, Get Inkey or
Get Input.
+ These can typically occur when a special SMS
is
+ received and might not involve interaction
from the
+ user.
+
+ Possible Errors:
[service].Error.InvalidArguments
+
[service].Error.InvalidFormat
+ [service].Error.InUse
+
- Is the RegisterAgent() method used to inform UICC of "Terminal
Applications" and if so, what is the set of "well known" "Terminal
Applications" that cards use to refer to "launch-able" applications
(reading section 7.8.1 from ETSI 102.223)? It would sound like there
is not such list, except as defined by SIM card providers, correct?
If so, are there plans to have ofono define/use a set of well known
applications and perform any translations needed by vendors with a
config file or plugin? Again, having not read the entire spec, I
could be asking hair-brained questions, feel free to enlighten ;)
- The API seems to suggest that there is one and only one Agent
registered at any time, correct?
If so, does this "default" agent then need to handle *all* SIM actions (I
would assume so if certification is desired.
If not, how would one associate the Agent at one ObjectPath as the
handler for a specific (or subset of possible) action request(s)?
+ void UnregisterAgent(object path)
+
+ Unregisters the default agent. If no agent
is
+ registered then unsolicited commands from
the SIM
+ are rejected.
+
+ Possible Errors:
- I gather that a call to UnregisterAgent() will result in the
Release() method of the named agent (if existing) being called,
correct?
+ [service].Error.NotFound
+
[service].Error.NotAuthorized +
- What are the plans for the configuration of services/object paths for
"launch-able" Terminal Applications (AKA, Agents?)? Will there be a
stk.conf file or similar or will this be protected in a dbus service
config file?
- Signals? Surely we at least need a PropertyChanged() signal?
+ array{string} MainMenuItems
+
+ Contains the items that make up the main
menu. This
+ is populated by the SIM when it sends the
Setup Menu
+ Proactive Command. The main menu is always
available,
+ but its contents can be changed at any time.
- So subsequent changes to MainMenuItems (presumably through a
PropertyChanged or equivalent signal?) are to be considered complete
replacements for the currently displayed menu items, or must the
array be traversed and compared with current to identify new or
removed items?
+
+ array{array{bytes}} MainMenuIcons
+
+ Contains the icons associated with the main
menu items. +
- Does the spec (or ofonos interpretation and implementation of it)
plan to enforce any constraints on the 1:1 association of icons to
menu items?
IOW, can the MainMenuItems array contain a different number of
entries than are in the MainMenuIcons array? If so, how do you
propose the keep them properly aligned? If not (both arrays must
have same number of entries), can a given index in the icons array be
empty, indicating not icon is displayed for the matching index in the
MainMenuItems array?
- Does the spec, or will ofono, define the specific format of the byte
data being used to pass the icon data?
If not, I suggest a property that hold an icon format identifier,
"string IconFormat" as an example
+SimToolkitAgent Hierarchy
+===============
+
+Service unique name
+Interface org.ofono.SimToolkitAgent
+Object path freely definable
+
+Methods byte SelectItem(string title, array{string}
items,
+ array{array{byte}} icons, byte
default) +
+ Tells the agent to ask the user to select an
item
+ from the menu. This function should return
the index
+ of the item or an error given below:
- Not to make any assumptions, but does the SIM/UICC define whether
index returns are expected as 0 or 1 based?
- Same questions regarding item<->icon array mappings as above in
MainMenu* properties? Should the agent enforce any specific rules
between these two arrays, and if so, what (if any) errors should be
returned?
+
+ Possible Errors:
[service].Error.SimToolkit.GoBack +
- Can you describe a use case where I, as the Agent writer, would need
to reply with a "GoBack" error, and what it means from a UI
perspective?
I read it as, "User made no selection, but instead hit the escape or
'go back' button and made no choice". Is this a correct
understanding?
> + string GetInput(string alpha, array{byte} icon,
> + string default, byte min, byte max,
> + boolean hide_typing)
> +
> + Tells the agent to request an input string
> from the
> + user. The alpha parameter and icon gives
> context to
> + the user. The default string contains the
> suggested
> + default by the SIM. The min and max
> parameters contain
> + how many characters the user should enter.
> The
> + parameter hide_typing indicates whether
> user's typing
> + should be opaque.
+
+ Possible Errors:
[service].Error.SimToolkit.GoBack +
- Same questions as above regarding the icon data formatting.
- Given the min/max constraints, plus the default value, I assume
that if the input provided by the user falls within (inclusive) both
conditions, this is what is returned, otherwise the value of default
is returned, correct?
- Can min or max ever be 0, and if so, should unconstrained strings be
returned or is there a spec defined max length for strings?
> + string GetKey(string alpha, array{byte} icon)
> +
> + Tells the agent to request a single input
> key from
> + the user. The alpha parameter contains the
> context
> + for the request.
+
+ Possible Errors:
[service].Error.SimToolkit.GoBack +
- I am assuming this "Key" is in fact meant to imply a single
Character, not a scan code or keycode from some hardware key,
correct? May seem obvious to some, but I can't always be sure.
If so, isn't this just a special case of GetInput, with min and max
both set to 0?
+ boolean GetConfirmation(string alpha, array{byte}
icon) +
+ Asks the agent to get confirmation from the
user. +
+ Possible Errors:
[service].Error.SimToolkit.GoBack +
- Depending on the app/query, the text of the confirmation options
could be any of the following (at least):
yes/no (prompted to reboot)
cancel/continue (prompted to install an application)
"I agree"/"I do not agree" (prompted to agree to EULA?)
next/previous (progressing through a series of dialogs)
...
Given this, I could see the need for this API to contain parameters
for the strings that should represent the "true" and "false"
selection results.
This of course gets tricky if the locale and translations come into
play here...
What Proactive UICC command does this map to anyway? I don't see
any obvious compliment in the spec?
+ void Release()
+
+ Agent is being released, possibly because of
oFono
+ terminating, SimToolkit interface torn down
or modem
+ off. If the agent is registered as a global
agent,
+ no UnregisterAgent call is expected.
Ok, so in this case, the SimToolkit will call the agents Release()
method when (as asked above in the RegisterAgent() comments) the modem
Powered state goes from true to false (as well as under other possible
conditions, yeah, I know), correct?
Shane...
10:22 a.m.
Hi Shane,
On 07/21/2010 05:06 PM, Shane Bryan wrote:
On Mon, 19 Jul 2010 17:28:48 -0500
Denis Kenzior <denkenz(a)gmail.com> wrote:
> Up for comment is the Sim Application Toolkit API proposal for
> oFono. It is largely based on Andrew's API proposal with several
> changes in areas I felt needed further attention. I'd like all
> interested to comment, what looks good, what looks crummy? Is
> anything missing?
General comments, from the perspective of one who may end writing an
STK Agent app/ui in MeeGo:
- Having not read the full spec, what (if any) considerations need to
be made for locales and multi-byte characters that could be entered
if the UI is running in a multi-byte locale?
oFono always assumes input / output is UTF8. However, there might be a
consideration for the RequestInput and RequestInkey cases where the SIM
only wants GSM characters, not arbitrary unicode characters.
Addendum: I now see the spec has the LANGUAGE NOTIFICATION
Proactive
Command. Any early ideas on if/how this would be implemented and
what should be done from a UI perspective if the language does not
match the current runtime locale and/or language, esp if they differ
in directionality (right-to-left vs. left-to-right)?
This might be a consideration for Settings application, since the SIM is
notifying us of the Language selection. How this works out in practice
is unclear. Perhaps Settings has to inform the rest of the system of
the change, or just ignore it.
- Same for translations? Do the strings provided need to be
translated, or is that left as a function of the SIM vendor and the
region the card is coded for?
No translation is needed (or possible) here, oFono will send UTF8 strings.
If the LANGUAGE NOTIFICATION *is* implemented, then I assume the
agent writer would not have to deal with translation issues for text
provided by the SIM application. I would assume strings following a
change in language notification would be "pre-translated"... fair
assumption?
If the SIM supports multiple languages, then it would have to do the
translation. No translation is needed on the UI end.
- Does the spec, or will ofono, define the max length of the strings
passed for any properties that will result in the display of text on
screen?
The maximum is 255 UTF8 characters (not bytes).
> +SimToolkit Hierarchy
> +===============
> +
> +Service org.ofono
> +Interface org.ofono.SimToolkit
- I take it this interface is independent of the org.ofono.manager and
org.ofono.modem interfaces?
It is an atom interface, similar to VoiceCallManager, so yes, independent.
> +Object path [variable prefix]/{modem0,modem1,...}
- Does this modem path map exactly to the path provided through
org.ofono.manager.GetProperties() or can/will it be completely
orthogonal to it?
It is the modem path, similar to e.g. VoiceCallManager.
- If closely tied to the "Modems" propertied in the Manager
interface, what is the effect (if any) to changes in the "Powered"
state on the modem when triggered via a call to
org.ofono.Modem.SetProperties() for that modem path?
Will it trigger a Unregister or PropertyChanged signal to the agent
and/or toolkit interfaces?
If the Modem is removed or powered down, oFono will call the 'Release()'
method of the registered Agents, if any.
> +
> +Methods dict GetProperties()
> +
> + Returns properties for the SimToolkit
> object. See the
> + properties section for available properties.
> +
> + Possible Errors:
> [service].Error.InvalidArguments +
> + void RegisterAgent(object path)
> +
> + Registers a default agent to be used for SIM
> initiated
> + actions such as Display Text, Get Inkey or
> Get Input.
> + These can typically occur when a special SMS
> is
> + received and might not involve interaction
> from the
> + user.
> +
> + Possible Errors:
> [service].Error.InvalidArguments
> +
> [service].Error.InvalidFormat
> + [service].Error.InUse
> +
- Is the RegisterAgent() method used to inform UICC of "Terminal
Applications" and if so, what is the set of "well known" "Terminal
Applications" that cards use to refer to "launch-able" applications
(reading section 7.8.1 from ETSI 102.223)? It would sound like there
is not such list, except as defined by SIM card providers, correct?
If so, are there plans to have ofono define/use a set of well known
applications and perform any translations needed by vendors with a
config file or plugin? Again, having not read the entire spec, I
could be asking hair-brained questions, feel free to enlighten ;)
You're confusing yourself here. Agent is simply a user-agent (e.g. UI)
that oFono asks to perform some tasks. E.g. display some text, have
user give some input, etc.
- The API seems to suggest that there is one and only one Agent
registered at any time, correct?
If so, does this "default" agent then need to handle *all* SIM actions (I
would assume so if certification is desired.
If not, how would one associate the Agent at one ObjectPath as the
handler for a specific (or subset of possible) action request(s)?
There are actually two agents. The 'default' agent that is registered /
unregistered via RegisterAgent() and UnregisterAgent(). There's also
the 'user-session' agent that is registered via the SelectItem() method.
Please see the updated API for details.
The basic thinking is as follows. We define the 'user session' as
something that is explicitly initiated by the user. The only way to do
that is by going through the main menu. However, there are (very rare)
situations where the SIM itself can initiate a session. This is where
the 'default' agent comes in.
If the 'user-session' agent is active, it takes over ALL aspects of
SimToolkit, the 'default' agent is never called. Once the user session
is ended and the 'user session' agent is Release()-ed, then the
'default' agent takes over again. The side effect of this is that the
'user-agent' might accidentally take over tasks meant for the 'default'
agent, but the protocol does not let us recognize such cases. These
should be astronomically unlikely as well.
In general the 'default' agent _could_ be less featureful than the
'user-session' agent and not handle some of the more esoteric things.
> + void UnregisterAgent(object path)
> +
> + Unregisters the default agent. If no agent
> is
> + registered then unsolicited commands from
> the SIM
> + are rejected.
> +
> + Possible Errors:
- I gather that a call to UnregisterAgent() will result in the
Release() method of the named agent (if existing) being called,
correct?
Correct.
> + [service].Error.NotFound
> +
> [service].Error.NotAuthorized +
- What are the plans for the configuration of services/object paths for
"launch-able" Terminal Applications (AKA, Agents?)? Will there be a
stk.conf file or similar or will this be protected in a dbus service
config file?
- Signals? Surely we at least need a PropertyChanged() signal?
Yes, sorry that was missed. PropertyChanged is of course needed. This
has been fixed upstream.
> + array{string} MainMenuItems
> +
> + Contains the items that make up the main
> menu. This
> + is populated by the SIM when it sends the
> Setup Menu
> + Proactive Command. The main menu is always
> available,
> + but its contents can be changed at any time.
- So subsequent changes to MainMenuItems (presumably through a
PropertyChanged or equivalent signal?) are to be considered complete
replacements for the currently displayed menu items, or must the
array be traversed and compared with current to identify new or
removed items?
Great question. They will be complete replacements. Whether you choose
to do anything fancy here is up to you. The infrequency of main menu
changes (i.e. never) doesn't make this really important.
> +
> + array{array{bytes}} MainMenuIcons
> +
> + Contains the icons associated with the main
> menu items. +
- Does the spec (or ofonos interpretation and implementation of it)
plan to enforce any constraints on the 1:1 association of icons to
menu items?
Great question. There's nothing in the spec that enforces this, however
you can count on oFono to do the right thing here. You can always
assume that there will be parity between the # of icons and the # of
items.
IOW, can the MainMenuItems array contain a different number of
entries than are in the MainMenuIcons array? If so, how do you
propose the keep them properly aligned? If not (both arrays must
have same number of entries), can a given index in the icons array be
empty, indicating not icon is displayed for the matching index in the
MainMenuItems array?
An empty icon (not present) will be given an identifier of 0. All other
icon identifiers are between 1 and 255.
- Does the spec, or will ofono, define the specific format of the byte
data being used to pass the icon data?
We're currently investigating icon formats. The most likely candidate
is currently XPM. Suggestions here are welcome.
If not, I suggest a property that hold an icon format identifier,
"string IconFormat" as an example
> +SimToolkitAgent Hierarchy
> +===============
> +
> +Service unique name
> +Interface org.ofono.SimToolkitAgent
> +Object path freely definable
> +
> +Methods byte SelectItem(string title, array{string}
> items,
> + array{array{byte}} icons, byte
> default) +
> + Tells the agent to ask the user to select an
> item
> + from the menu. This function should return
> the index
> + of the item or an error given below:
- Not to make any assumptions, but does the SIM/UICC define whether
index returns are expected as 0 or 1 based?
For now assume the index is always 0-based. oFono will take care of the
mapping to the SIM (which is always 1-based)
- Same questions regarding item<->icon array mappings as above in
MainMenu* properties? Should the agent enforce any specific rules
between these two arrays, and if so, what (if any) errors should be
returned?
The latest API snapshot does not have this issue. Icon ids are always
between 1 and 255.
> +
> + Possible Errors:
> [service].Error.SimToolkit.GoBack +
- Can you describe a use case where I, as the Agent writer, would need
to reply with a "GoBack" error, and what it means from a UI
perspective?
I read it as, "User made no selection, but instead hit the escape or
'go back' button and made no choice". Is this a correct
understanding?
That is basically correct, e.g. the user wants to go back one level
without performing an action.
> + string GetInput(string alpha, array{byte} icon,
> + string default, byte min, byte max,
> + boolean hide_typing)
> +
> + Tells the agent to request an input string
> from the
> + user. The alpha parameter and icon gives
> context to
> + the user. The default string contains the
> suggested
> + default by the SIM. The min and max
> parameters contain
> + how many characters the user should enter.
> The
> + parameter hide_typing indicates whether
> user's typing
> + should be opaque.
> +
> + Possible Errors:
> [service].Error.SimToolkit.GoBack +
- Same questions as above regarding the icon data formatting.
- Given the min/max constraints, plus the default value, I assume
that if the input provided by the user falls within (inclusive) both
conditions, this is what is returned, otherwise the value of default
is returned, correct?
No, this is more about validation. E.g. the agent should not return
more than max or less than min characters. A maximum value of 255 means
no maximum is given.
The user can either accept the default value or enter his own input.
- Can min or max ever be 0, and if so, should unconstrained strings be
returned or is there a spec defined max length for strings?
The maximum returned pdu is 255 bytes, this translates to something less
than 255 character string.
> + string GetKey(string alpha, array{byte} icon)
> +
> + Tells the agent to request a single input
> key from
> + the user. The alpha parameter contains the
> context
> + for the request.
> +
> + Possible Errors:
> [service].Error.SimToolkit.GoBack +
- I am assuming this "Key" is in fact meant to imply a single
Character, not a scan code or keycode from some hardware key,
correct? May seem obvious to some, but I can't always be sure.
Correct
If so, isn't this just a special case of GetInput, with min and
max
both set to 0?
Both set to 1 actually.
> + boolean GetConfirmation(string alpha, array{byte}
> icon) +
> + Asks the agent to get confirmation from the
> user. +
> + Possible Errors:
> [service].Error.SimToolkit.GoBack +
- Depending on the app/query, the text of the confirmation options
could be any of the following (at least):
yes/no (prompted to reboot)
cancel/continue (prompted to install an application)
"I agree"/"I do not agree" (prompted to agree to EULA?)
next/previous (progressing through a series of dialogs)
...
Given this, I could see the need for this API to contain parameters
for the strings that should represent the "true" and "false"
selection results.
This of course gets tricky if the locale and translations come into
play here...
What Proactive UICC command does this map to anyway? I don't see
any obvious compliment in the spec?
This maps to GetInkey with the Command Qualifier 'Yes/No response is
requested' set. See ETSI 102.223 Section 8.6. I suggest always using
'Yes' / 'No' responses here.
> + void Release()
> +
> + Agent is being released, possibly because of
> oFono
> + terminating, SimToolkit interface torn down
> or modem
> + off. If the agent is registered as a global
> agent,
> + no UnregisterAgent call is expected.
Ok, so in this case, the SimToolkit will call the agents Release()
method when (as asked above in the RegisterAgent() comments) the modem
Powered state goes from true to false (as well as under other possible
conditions, yeah, I know), correct?
Correct, you can count on oFono to do the right thing here, unless of
course it just crashes. But that *never* happens ;)
Shane...
Regards,
-Denis
12:01 p.m.
Hi,
On 22 July 2010 02:22, Denis Kenzior <denkenz(a)gmail.com> wrote:
On 07/21/2010 05:06 PM, Shane Bryan wrote:
>
>> + [service].Error.NotFound
>> +
>> [service].Error.NotAuthorized +
>
> - What are the plans for the configuration of services/object paths for
> "launch-able" Terminal Applications (AKA, Agents?)? Will there be a
> stk.conf file or similar or will this be protected in a dbus service
> config file?
Most likely the Terminal Applications capability will not be
implemented for a while, it is not used by popular SIMs and is not
very practical. It may be implemented if needed.
>> + string GetInput(string alpha, array{byte} icon,
>> + string default, byte min, byte max,
>> + boolean hide_typing)
>> +
>> + Tells the agent to request an input string
>> from the
>> + user. The alpha parameter and icon gives
>> context to
>> + the user. The default string contains the
>> suggested
>> + default by the SIM. The min and max
>> parameters contain
>> + how many characters the user should enter.
>> The
>> + parameter hide_typing indicates whether
>> user's typing
>> + should be opaque.
>> +
>> + Possible Errors:
>> [service].Error.SimToolkit.GoBack +
>
> - Same questions as above regarding the icon data formatting.
>
> - Given the min/max constraints, plus the default value, I assume
> that if the input provided by the user falls within (inclusive) both
> conditions, this is what is returned, otherwise the value of default
> is returned, correct?
No, this is more about validation. E.g. the agent should not return
more than max or less than min characters. A maximum value of 255 means
no maximum is given.
The user can either accept the default value or enter his own input.
This really just means a text input field, with the default text as
initial value, if any.
>> + string GetKey(string alpha, array{byte} icon)
>> +
>> + Tells the agent to request a single input
>> key from
>> + the user. The alpha parameter contains the
>> context
>> + for the request.
>> +
>> + Possible Errors:
>> [service].Error.SimToolkit.GoBack +
>
> - I am assuming this "Key" is in fact meant to imply a single
> Character, not a scan code or keycode from some hardware key,
> correct? May seem obvious to some, but I can't always be sure.
>
Correct
The SIM either requests a single gsm 7-bit character, a single unicode
character or a single key press (on the physical keypad), depending on
the parameters of the SIM command. However this api does not make a
distiction between these options (the previous api does has an
"alphabet" parameter).
>
>
>> + void Release()
>> +
>> + Agent is being released, possibly because of
>> oFono
>> + terminating, SimToolkit interface torn down
>> or modem
>> + off. If the agent is registered as a global
>> agent,
>> + no UnregisterAgent call is expected.
>
> Ok, so in this case, the SimToolkit will call the agents Release()
> method when (as asked above in the RegisterAgent() comments) the modem
> Powered state goes from true to false (as well as under other possible
> conditions, yeah, I know), correct?
Yes, additionally ofono will call Release() on the "user-initiated
agent" when the card wants the UI to go back to the main menu or close
the UI altogether. The spec suggests / recommends that basically the
application should go to main menu if the last action performed was a
GoBack button press, otherwise the application should exit, but it may
depend on the specific use case. For example the javascript GUI
client I use for testing this always has screen space available so it
always goes to main menu.
Regards
4441
days inactive
4444
days old
3 comments
3 participants
participants (3)
-
Andrzej Zaborowski -
Denis Kenzior -
Shane Bryan