|
|
131.
|
|
|
Cairo's rich drawing model allows for high-quality rendering to multiple media. The same API can be used to create stunning on-screen graphics and text, to render images, or create crisp output suitable for printing.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/cairo.page:25(p)
|
|
|
132.
|
|
|
You should use Cairo whenever you need to draw graphics in your application beyond the widgets provided by GTK+. Much of the drawing inside GTK+ is done using Cairo. Using Cairo for your custom drawing will allow your application to have high-quality, anti-aliased, and resolution-independent graphics.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/cairo.page:30(p)
|
|
|
133.
|
|
|
Cairo Manual
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/cairo.page:37(link)
|
|
|
134.
|
|
|
Support for screen readers and other accessibility tools
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/atk.page:6(desc)
|
|
|
135.
|
|
|
ATK
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/atk.page:11(title)
|
|
|
136.
|
|
|
Accessibility is the process of ensuring your application can be used by people with various disabilities. Disabilities come in many forms: visual impairments, movement impairments, hearing impairments, cognitive and language impairments, and seizure disorders. Many people have some sort of disability, and making your application accessibility will allow more people to use your application effectively.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/atk.page:13(p)
|
|
|
137.
|
|
|
GNOME provides support for accessibility devices using the ATK framework. This framework defines a set of interfaces to which graphical interface components adhere. This allows, for instance, screen readers to read the text of an interface and interact with its controls. ATK support is built into GTK+ and the rest of the GNOME platform, so any application using GTK+ will have reasonable accessibility support for free.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/atk.page:20(p)
|
|
|
138.
|
|
|
Nonetheless, you should be aware of accessibility issues when when developing your applications. Although GTK+ interfaces provide reasonable accessibility by default, you can often improve how well your program behaves with accessibility tools by providing additional information to ATK. If you develop custom widgets, you should ensure that they expose their properties to ATK. You should also avoid using sound, graphics, or color as the sole means of conveying information to the user.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/atk.page:28(p)
|
|
|
139.
|
|
|
The GNOME desktop ships with a number of accessibility tools which enable users with disabilities to take full advantage of their desktop and applications. Applications that fully implement ATK will be able to work with the accessibility tools. GNOME's accessibility tools include a screen reader, a screen magnifier, an on-screen keyboard, and <app>Dasher</app>, an innovative predictive text entry tool.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/atk.page:37(p)
|
|
|
140.
|
|
|
GNOME Accessibility for Developers
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/atk.page:46(link)
|
