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

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

From: Heiko Braun <ike.braun@googlemail.com>
Date: Wed, 22 Jan 2014 14:33:25 +0100
Message-Id: <3A073AF4-8F0B-40B7-92E0-D70AA99FD257@googlemail.com>
Cc: "public-mbui@w3.org" <public-mbui@w3.org>
To: Paolo Bottoni <bottoni@di.uniroma1.it>
I think the term "trigger" is somewhat misleading. As Hick said "every event triggers something" as in "leads to certain behaviour". From my point of view, a "TriggerEvent" is something initiated by  by an interaction, opposed to system events or events as a result of function call.

More generally speaking, I think concrete events are not as important as the underlying concept of resource input and output. These are intended to model control flow within the application. The concrete event types as in the AUI model can thought of as just means of transportation with specific semantics. 

Regards, Heiko

> Am 22.01.2014 um 08:29 schrieb 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 13:33:56 UTC

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