1<page xmlns="http://projectmallard.org/1.0/" type="topic" id="desktop_tree_view"> 2 <info> 3 <link type="guide" xref="index#examining_a11y" /> 4 <title type="sort">1. Application Tree View</title> 5 <link type="next" xref="interface_viewer_plugin" /> 6 <desc> 7 Exploring the accessible hierarchy of the desktop 8 </desc> 9 <credit type="author"> 10 <name>Eitan Isaacson</name> 11 <email>eitan@ascender.com</email> 12 </credit> 13 <credit type="author"> 14 <name>Peter Parente</name> 15 <email>pparent@us.ibm.com</email> 16 </credit> 17 <credit type="author"> 18 <name>Aline Bessa</name> 19 <email>alibezz@gmail.com</email> 20 </credit> 21 <license> 22 <p>Creative Commons Share Alike 3.0</p> 23 </license> 24 </info> 25 <title>Application Tree View</title> 26 27 <p> 28 <app>Accerciser</app>'s interface contains a tree view, namely Application Tree View, that covers all 29 accessible applications currently running on the desktop. To create this tree view, <app>Accerciser</app> 30 uses the AT-SPI's registry daemon. This daemon is responsible for keeping track of all the accessible 31 applications on the desktop and forwarding X events over the AT-SPI D-Bus. After getting all accessible 32 applications, <app>Accerciser</app> represents each one of them as a hierarchical structure with expanding 33 nodes. 34 </p> 35 36 <figure> 37 <title>Application Tree View</title> 38 <desc> 39 <app>Accerciser</app>'s Application Tree View represents the interface of each accessible application 40 running on the desktop as a widget hierarchical structure. 41 </desc> 42 <media type="image" mime="image/png" width="400" height="600" src="figures/tree_view_accerciser.png"> 43 <p><app>Accerciser</app>'s Application Tree View represents the interface of each accessible application 44 running on the desktop as a widget hierarchical structure.</p> 45 </media> 46 </figure> 47 48 49 <p> 50 The first node of each application represented in this tree view is the application itself. When you expand a node, you 51 can see all of its child widgets, which allows a hierarchical view of the application's interface. For each node, 52 <app>Accerciser</app> provides some basic information, such as its name, role and number of children. 53 </p> 54 55 <note style="caution"> 56 <p> 57 Be aware that nodes with many children take a long time to expand. 58 </p> 59 </note> 60 61 <section id="bookmarking"> 62 <title>Bookmarking items in the Application Tree View</title> 63 <p> 64 <app>Accerciser</app> allows bookmarking items in the Application Tree View for later examining. This is helpful when 65 the target application must be restarted - after rebuilding it, for example. To bookmark an item, select it and do 66 <guiseq><gui>Bookmarks</gui><gui>Add Bookmark</gui></guiseq> or press <keyseq><key>Ctrl</key><key>d</key></keyseq>. 67 </p> 68 <p> 69 Bookmarks to accessible items in <app>Accerciser</app> are defined by an application name and a "path" in the 70 application's internal accessible hierarchy to the bookmarked accessible. When the target application is in a 71 different state - i.e. multiple top level frames -, the path might not be correct. Bookmarks could be managed 72 by accessing the bookmark editing dialog through <guiseq><gui>Bookmarks</gui><gui>Edit Bookmarks</gui></guiseq>. 73 </p> 74 </section> 75 76</page> 77