[yast-devel] Dialogs integration
Hi, This has been discussed a few times before, with regard to the buttons order; having a specialized API for dialogs. There is one more good reason to it: accessibility software. It seems like Orca has some functionality for message dialogs: https://bugzilla.novell.com/show_bug.cgi?id=346987#c21 Maybe we could go with something like this: `MessageDialog ( `warning|`error|`information, heading, text, some_widget|nil, `ButtonsBox ("Ok", "Cancel", ...) ); Cheers, Ricardo -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Tue, Mar 11, 2008 at 01:38:24AM +0000, Ricardo Cruz wrote:
Hi,
This has been discussed a few times before, with regard to the buttons order; having a specialized API for dialogs. There is one more good reason to it: accessibility software. It seems like Orca has some functionality for message dialogs: https://bugzilla.novell.com/show_bug.cgi?id=346987#c21
What is Orca? I am afraid that the YaST team knows almost nothing about accessibility. Please educate us.
Maybe we could go with something like this:
`MessageDialog ( `warning|`error|`information, heading, text, some_widget|nil, `ButtonsBox ("Ok", "Cancel", ...) );
We have something like this in Popup.ycp already. So what is new here? -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Am Dienstag 11 März 2008 schrieb Martin Vidner:
On Tue, Mar 11, 2008 at 01:38:24AM +0000, Ricardo Cruz wrote:
Hi,
This has been discussed a few times before, with regard to the buttons order; having a specialized API for dialogs. There is one more good reason to it: accessibility software. It seems like Orca has some functionality for message dialogs: https://bugzilla.novell.com/show_bug.cgi?id=346987#c21
What is Orca? I am afraid that the YaST team knows almost nothing about accessibility. Please educate us.
Orca (assistive technology) From Wikipedia, the free encyclopedia Orca is a free, open source, flexible, extensible, and powerful assistive technology for people with visual impairments. Using various combinations of speech synthesis, braille, and magnification, Orca helps provide access to applications and toolkits that support the AT-SPI (e.g., the GNOME desktop). The development of Orca has been led by the Accessibility Program Office of Sun Microsystems, Inc. with contributions from many community members. The name Orca, which is another term for a killer whale, is a nod to the long-standing Assistive Technology product on Windows called JAWS, which is the name of a fictional shark. As of GNOME 2.16, Orca is a part of the GNOME platform. As a result, Orca is already provided by default on a number of operating system distributions, including Open Solaris, openSUSE, and Ubuntu. Greetings, Stephan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
What is Orca?
AFAIK Orca is a screen reader in GNOME.
I am afraid that the YaST team knows almost nothing about accessibility. Please educate us.
Maybe we could do this as a seminar on a YaST workshop? Cu, Martin -- Martin Schmidkunz User Experience Specialist martin.schmidkunz@novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Dňa Tuesday 11 March 2008 09:38:54 Martin Vidner ste napísal:
On Tue, Mar 11, 2008 at 01:38:24AM +0000, Ricardo Cruz wrote:
Hi,
This has been discussed a few times before, with regard to the buttons order; having a specialized API for dialogs. There is one more good reason to it: accessibility software. It seems like Orca has some functionality for message dialogs: https://bugzilla.novell.com/show_bug.cgi?id=346987#c21
What is Orca? I am afraid that the YaST team knows almost nothing about accessibility. Please educate us.
Maybe we could go with something like this:
`MessageDialog ( `warning|`error|`information, heading, text, some_widget|nil, `ButtonsBox ("Ok", "Cancel", ...) );
We have something like this in Popup.ycp already. So what is new here?
You need an integration at libyui level to get proper accesibility support. Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Ter, 2008-03-11 às 09:38 +0100, Martin Vidner escreveu:
On Tue, Mar 11, 2008 at 01:38:24AM +0000, Ricardo Cruz wrote:
Hi,
This has been discussed a few times before, with regard to the buttons order; having a specialized API for dialogs. There is one more good reason to it: accessibility software. It seems like Orca has some functionality for message dialogs: https://bugzilla.novell.com/show_bug.cgi?id=346987#c21
What is Orca? I am afraid that the YaST team knows almost nothing about accessibility. Please educate us.
I don't know much about it myself; it seems like it reads labels and stuff. I guess whats informative is how the accessibility library works: you describe the various UI elements and then through introspection, accessibility software makes sense out of it. In this case, we can't indicate whether a dialog is a message dialog or not, and whats the heading label and stuff.
Maybe we could go with something like this:
`MessageDialog ( `warning|`error|`information, heading, text, some_widget|nil, `ButtonsBox ("Ok", "Cancel", ...) );
We have something like this in Popup.ycp already. So what is new here?
Great. Then we just need to port it to libyui, to make it possible for the specific UIs to implement it -- or a fallback to be used. I guess it could look like: void openMessageDialog (enum type, string header, string text, Widget *, ButtonsBox *) I think it makes sense to have this ButtonsBox, derived from HBox, so that we can re-use it elsewhere. I'm not sure if allowing for a Widget is really that useful; in case we don't use it, we could just hang there, instead of using the usual event model. With regard to the ButtonsBox, maybe: Widget* ButtonsBox::add (const char *label, Type action) Widget* ButtonsBox::addOkCancel(), ... or enum { Ok, Cancel, .. }; Widget* ButtonsBox::addStock(enum) I'm not sure how widgets are identified in libyui, I guess by their address. Regardless, it should reflect that. Of course, the ycp bridge could treat it differently, and detect labels like Ok if that avoids the need to re-write things. Cheers, Ricardo -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (5)
-
Martin Schmidkunz -
Martin Vidner -
Ricardo Cruz -
Stanislav Visnovsky -
Stephan Kulow