1 <?xml version="1.0" encoding="UTF-8"?>
2 <node xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0" name="/node">
8 <interface name="org.freedesktop.atspi.Registry">
9 <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
10 <p>The Registry is a service through which applications providing
11 accessibility services (servers) can rendezvous with consumers of those
12 services (Assistive Technologies). The Registry is the first "port of call" for
13 accessible applications and for assistive technologies wishing to query and
14 interact with those applications. </p>
16 <p>The Registry service provides four basic functions to Assistive Technology (AT) clients:
17 \li it provides a list of the applications who have registered with the AT-SPI
18 framework, thereby announcing their participation in the AT-SPI framework;
19 \li it allows AT clients to register for notification of changes in application
20 state (at-spi Events);
21 \li it dispatches/relays said events from participating applications to
22 the registered listeners;
23 \li it gives access to system device events via the associated DeviceEventController
26 <p>From the point of view of accessible applications (i.e. AT-SPI service producers),
27 the Registry is primarily a registration and event delivery service. Applications
28 normally only call the registerApplication and deregisterApplication Registry methods,
29 and its inherited EventListener::notifyEvent method. </p>
31 <p>@note Although all application events are dispatched via the Registry, other AT client
32 calls are serviced directly by the applications, rather than being relayed via the
33 Registry. The AT client obtains references to these application objects
34 via the enumeration of Desktop instances whose children are Application instances
35 (Registry::getDesktopList) and via examination of the 'source' member of the Event
38 <p>The Registry normally lives in its own process space; communication via Registry and
39 both application services and AT clients takes place via IPC. A process space diagram
40 illustrating the relationship between applications, Registry, and AT is shown below.
41 @image html "http://developer.gnome.org/projects/gap/tech-docs/SPIBlockDiagram.png" </p>
43 <p>@see Desktop, Application, Event, EventListener</p>
45 <method name="registerApplication">
47 Register a new application with the accessibility broker.
50 <method name="deregisterApplication">
51 <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
52 <p>De-register an application previously registered with the broker.
53 deregisterApplication:</p>
55 <arg direction="in" name="app" type="o" tp:type="Application">
57 a reference to the Application to be deregistered.
61 <method name="registerGlobalEventListener">
62 <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
63 <p>Register a client's interest in (all) application events of
66 <arg direction="in" name="listener" type="o" tp:type="EventListener">
68 a reference to the requesting ::EventListener.
71 <arg direction="in" name="eventName" type="s">
73 a string which indicates the type of events about which the client desires notification.
77 <method name="deregisterGlobalEventListenerAll">
79 deregisterGlobalEventListenerAll:
81 <arg direction="in" name="listener" type="o" tp:type="EventListener">
83 the requesting EventListenerRequest that a previously registered client stop receivingglobal notifications for all events for which it was registered.
87 <method name="deregisterGlobalEventListener">
89 deregisterGlobalEventListener:
91 <arg direction="in" name="listener" type="o" tp:type="EventListener">
93 the requesting EventListener
96 <arg direction="in" name="eventName" type="s">
98 a string indicating the type of eventsRequest that a previously registered client stop receivingglobal notifications for events of a certain type.
102 <method name="getDesktopCount">
103 <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
104 <p>event types: "Window" "Desktop"
105 "Window:Create" "Window:Destroy"
106 "Window:Iconify" "Window:Restore"
107 "Window:Fullscreen" "Window:Resize"
108 "Desktop:Create" "Desktop:Destroy"
109 "Desktop:Focus" "Desktop:Defocus"
113 "GObject:notify:<propertyname>" </p>
115 <p>( not sure we should allow these last 2 forms,
116 since they are toolkit-specific, but they're powerful ) </p>
118 <p>getDesktopCount: </p>
120 <p>Get the current number of desktops.</p>
122 <arg direction="out" type="n" tp:type="short">
124 a short integer indicating the current number of Desktops.
128 <method name="getDesktop">
129 <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
131 @n: the index of the requested Desktop. </p>
133 <p>Get the nth accessible desktop. </p>
135 <arg direction="in" name="n" type="n" tp:type="short"/>
136 <arg direction="out" type="o" tp:type="Desktop">
138 a reference to the requested Desktop.
142 <method name="getDesktopList">
143 <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
144 <p>Get a list of accessible desktops. </p>
146 <arg direction="out" type="as" tp:type="DesktopSeq">
148 a sequence containing references tothe Desktops.
152 <method name="getDeviceEventController">
153 <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
154 <p>Obtain an object which can be used to request device event notifications. </p>
156 <arg direction="out" type="o" tp:type="DeviceEventController">
158 an object implementing DeviceEventController