只要一支手写笔，或者一只鼠标，用户就可以在画布上绘制图片，且这并不需要程序员来跟踪或处理任何事件。
Using a stylus, or alternately a mouse, users can draw on the canvas without the developer needing to directly deal with tracking events.
当运行时错误被处理后，管理员必须使用管理控制台或失败事件管理器(FEM)api脚本重新提交失败事件。
Once the runtime errors are resolved, the administrator will have to resubmit the failed events using either the admin console or scripts that use the failed event manager (FEM) API.
例如，登记员的概念消失并且被术语系统取代，这表示已经决定自动处理许多有关参加的琐碎事件。
For example, the concept of a registrar disappeared and was replaced with the term system, indicating that a decision had been made to automate many of the mundane aspects of enrollment.
然而，SAX的设计只考虑了功能的强大性，却没有考虑程序员使用起来是否方便，而这个问题对于编写事件处理程序，却显得尤为明显。
However, SAX was designed for power, not programmer's convenience, and that becomes painfully apparent when you write an event handler.
从使用CPrimeCalculator来编写应用的程序员角度看，处理事件简单而直白。
From the perspective of a programmer writing an application that USES CPrimeCalculator, handling events is simple and straightforward.
要定义任何可能的SAX事件处理程序，程序员必须扩展XML::SAX::Base并重写任何需要的方法。
To define any conceivable SAX event handler, a programmer extends XML::SAX::Base and overrides whatever methods are of interest.
要定义任何可能的SAX事件处理程序，程序员必须扩展XML::SAX::Base并重写任何需要的方法。
To define any conceivable SAX event handler, a programmer extends XML::SAX::Base and overrides whatever methods are of interest.
应用推荐