Skip to toolbar

Community & Business Groups

IndieUI: Events的标准工作草案更新

2015年1月15日,W3C的独立用户界面工作组(IndieUI Working Group)发布了独立用户界面:事件(IndieUI: Events 1.0)的工作草案更新(updated Working Draft),该工作草案中包含新的事件(Events)以及新定义的技术方法。IndieUI:Events 定义了一组与用户输入方式无关的事件,将依赖于用户输入方式的事件翻译为不依赖于用户输入方式的“高层”简单事件,基于这些简单事件编程可以简化Web应用的设计。例如,如果用户希望向下滚动页面内容,他可以用手指在触摸屏上向下滑动,也可以用鼠标上的滚动球向下滚动,或者使用滚轮,甚至在有些应用中通过语音命令来操纵。在IndieUI中,我们可以定义一个简单的Scroll Down事件,并将上述可能的操作关联到这一简单事件上。这在编写需要面对各种输入设备的Web应用时,将极大简化Web应用的开发。

独立用户界面(IndieUI)将使Web应用更容易适应于不同的设备(如智能手机及平板电脑)、不同的辅助技术、不同的用户需要等。开发者可以基于IndieUI开发适合多设备、多上下文的应用。欢迎您于2015年2月13日前提交您对该规范草案的意见和建议。

更多信息,请参阅IndieUI的概述,关于IndieUI: Events更新的相关邮件,及W3C的Web无障碍推进组织(Web Accessibility Initiative)

———————————————————————————————————-

The IndieUI Working Group today published an updated Working Draft of IndieUI: Events 1.0 – Events for User Interface Independence. This draft includes new events and a refined technical model. IndieUI: Events defines a way for different user interactions to be translated into simple events and communicated to Web applications. (For example, if a user wants to scroll down a page, they might use their finger on a touch screen, or click a scroll bar with a mouse, or use a scroll wheel, or say ‘scroll down’ with a voice command. With IndieUI, these are all sent to the Web app as simply: scroll down.) IndieUI will make it easier for Web applications to work in a wide range of contexts — different devices (such as mobile phones and tablets), different assistive technologies (AT), different user needs. With IndieUI,  Web application developers will have a uniform way to design applications that work for multiple devices and contexts. Comments on this Draft are encouraged by 13 February 2015. Learn more from the IndieUI Overview and the Updated Working Draft: IndieUI Events e-mail; and read about the Web Accessibility Initiative (WAI).

 

Leave a Reply

Your email address will not be published. Required fields are marked *

Before you comment here, note that this forum is moderated and your IP address is sent to Akismet, the plugin we use to mitigate spam comments.

*