W3C home > Mailing lists > Public > public-mbui@w3.org > January 2014

Re: Abstract User Interface Models - questions on event structure [Honeywell Internal]

From: Laufer <laufer@globo.com>
Date: Wed, 22 Jan 2014 14:20:54 -0200
Message-ID: <CA+pXJigXagxYv=XZPhPxZgVX8FefifhYCJampBydcUi+J_vxsg@mail.gmail.com>
To: Paolo Bottoni <bottoni@di.uniroma1.it>
Cc: "public-mbui@w3.org" <public-mbui@w3.org>
Hello All,

I want to contribute to this discussion.

I think a TriggerEvent is a turn-taking in the conversation. It tells the
other side that there is something to be treated.

An interface has a lot of ways to trigger things (to pass the turn to the
the other side) that are captured and treated in different layers. It can
be treated by the "hardware" (keyboard keys, touch screen, etc.), it can be
treated by a local code in RIA or smartphone´s apps, it can be treated by
the code running in the server, etc.

So, the interface models the next events to be treated by the application,
with the corresponding TriggerEvents (the interface corresponds also to the
response of a previous TriggerEvent).

Best regards,
Laufer






2014/1/22 Paolo Bottoni <bottoni@di.uniroma1.it>

> I can answer that.
>
> The TriggerEvent models events that trigger some high-level behaviour,
> typically a method in the domain model, or an activity in the world flow,
> which is not immediately corresponding to actions on the UI.
>
> However, the <<use>> dependency on events in the Behavior package is not
> correct (it was not included in the MBUI document, though).
>
> paolo
>
>
> 2014/1/22 Hickman, Steve (AdvTech) <Steve.Hickman@honeywell.com>
>
>  Classification: Honeywell Internal
>>
>> The 05 Nov 2013 Working Draft is spartan.  In particular, there isn’t
>> enough description of the event structure to understand how they differ.
>> Can someone explain this in more detail?  It seems to me that all events
>> trigger something unless they are ignored. It might be a change in a
>> display (selecting or deselecting a visual element, changing a value in a
>> visual element, etc.) or it might trigger something else.  So how is a
>> “TriggerEvent” something unique?
>>
>>
>>
>> Steve Hickman
>>
>> System Architect, Flight Deck of the Future
>>
>> 480-236-8367
>>
>>
>>
>>
>> ============================================================================================================================================================================================================
>> This message classified as Honeywell Internal by Hickman, Steve
>> (AdvTech) on Tuesday, January 21, 2014 at 5:30:42 PM.
>> The above classification labels are in accordance with the Honeywell
>> Corporate Classification Policy. The information contained in this
>> electronic message is confidential and intended only for the use of the
>> individual/entity named above, and the information may be privileged. If
>> you, the reader of this message, are not the intended recipient or an
>> employee or agent responsible to deliver this message to the intended
>> recipient, you are hereby notified that any dissemination, distribution or
>> copying of this communication is strictly prohibited. If you have received
>> this communication in error, please immediately notify the sender and
>> delete the original message.
>>
>> ============================================================================================================================================================================================================
>>
>
>
>
> --
> Paolo Bottoni
>
> Associate Professor of Computer Science
>
> Email: bottoni@di.uniroma1.it
>
> Website:
> http://w3.uniroma1.it/dipinfo/scheda_docente.asp?cognome=Bottoni&nome=Paolo
>
> Phone: +39 06 4925 5166
>
> Fax: + 39 06 8541842
>
> Important conferences:
>
> http://www.diagrams-conference.org/2014/home
> https://sites.google.com/site/vlhcc2014/
> http://hoc12.elet.polimi.it/avi2014/
> http://www.hpi.uni-potsdam.de/giese/events/2014/icgt/index.html
> http://www.ksi.edu/seke/vlc14cfp.html
>



-- 
.  .  .  .. .  .
.        .   . ..
.     ..       .
Received on Wednesday, 22 January 2014 16:21:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:26 UTC