Partial re-refactor of the accessibles registration code.

[platform/core/uifw/at-spi2-atk.git] / idl / Accessibility_Role.idl

diff --git a/idl/Accessibility_Role.idl b/idl/Accessibility_Role.idl
index b70e86a..fc962c6 100644 (file)
--- a/idl/Accessibility_Role.idl
+++ b/idl/Accessibility_Role.idl
@@ -296,21 +296,6 @@ module Accessibility {
   ROLE_EMBEDDED,
 
   /**
-   * The object is a link to some other content, for instance to a URI in this or another 
-   * document.  ROLE_LINK can occur primarily in two situations; as the role of an 
-   * object returned via the Hypertext::getLink, or, more importantly, as the role
-   * of a standalone object that implements the Hypertext interface but points to only
-   * one link object. 
-   *
-   * @note NOT SURE ABOUT THIS ONE, the description makes it sound pretty ropy.
-   * Why aren't links just identified via the Hypertext interface?  For non-textual
-   * hyperlinks (as allowed in XHTML 2.0), shouldn't this role be ROLE_IMAGE
-   * or ROLE_ICON?  
-   *
-   * @since AT-SPI 1.7.0
-   */
-  ROLE_LINK,
-  /**
    * The object is a component whose textual content may be entered or modified by the user,
    * provided STATE_EDITABLE is present.  
    * @note a readonly ROLE_ENTRY object (i.e. where STATE_EDITABLE is not present) implies a
@@ -372,6 +357,48 @@ module Accessibility {
    * @since AT-SPI 1.7.0
    */
   ROLE_SECTION,
+  /**
+   * The object is redundant with another object in the hierarchy, 
+   * and is exposed for purely technical reasons.  Objects of this role 
+   * should be ignored by clients, if they are encountered at all. 
+   *
+   * @since AT-SPI 1.7.6
+   */
+  ROLE_REDUNDANT_OBJECT,
+  /**
+   * The object is a containing instance of document content which
+   * has within it components with which the user can interact in order to
+   * input information; i.e. the object is a container for pushbuttons,
+   * comboboxes, text input fields, and other 'GUI' components.
+   * ROLE_FORM should not, in general, be used for toplevel GUI containers
+   * or dialogs, but should be reserved for 'GUI' containers which occur within
+   * document content, for instance within Web documents, presentations, or 
+   * text documents.  Unlike other GUI containers and dialogs which occur inside
+   * application instances, ROLE_FORM containers' components are associated with
+   * the current document, rather than the current foreground application or
+   * viewer instance.
+   *
+   * @since AT-SPI 1.7.6
+   */
+  ROLE_FORM,
+  /**
+   * The object is a hypertext anchor, i.e. a "link" in a
+   * hypertext document.  Such objects are distinct from 'inline'
+   * content which may also use the Hypertext/Hyperlink interfaces
+   * to indicate the range/location within a text object where
+   * an inline or embedded object lies.
+   *
+   * @since AT-SPI 1.7.6
+   */
+  ROLE_LINK,
+  /**
+   * The object is a window or similar viewport which is used
+   * to allow composition or input of a 'complex character',
+   * in other words it is an "input method window."
+   *
+   * @since AT-SPI 1.7.6
+   */
+  ROLE_INPUT_METHOD_WINDOW,
 
   /** not a valid role, used for finding end of enumeration. */
   ROLE_LAST_DEFINED