You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The (current) crate description, and the Guide don't seem to explicitly provide the scope for Conrod. Given that it's under Piston and given its implementation details (drawing own widgets with OpenGL), I've thought of it as being primarily tailored to games and visualization apps. But it's not been made clear/explicit and people seem to bring Conrod up in the same context as Qt and GTK when focusing on more general users.
The reason I'm asking is that it's not clear whether supporting proper OS-specific keyboard accessibility and screen reader accessibility (that Qt and GTK provide with significant infrastructural work) – and which is mandated, in a sense, for major/common apps that serve edu or government or various businesses that must accommodate people with different abilities – would naturally be part of the scope of Conrod.
The text was updated successfully, but these errors were encountered:
The (current) crate description, and the Guide don't seem to explicitly provide the scope for Conrod. Given that it's under Piston and given its implementation details (drawing own widgets with OpenGL), I've thought of it as being primarily tailored to games and visualization apps. But it's not been made clear/explicit and people seem to bring Conrod up in the same context as Qt and GTK when focusing on more general users.
The reason I'm asking is that it's not clear whether supporting proper OS-specific keyboard accessibility and screen reader accessibility (that Qt and GTK provide with significant infrastructural work) – and which is mandated, in a sense, for major/common apps that serve edu or government or various businesses that must accommodate people with different abilities – would naturally be part of the scope of Conrod.
The text was updated successfully, but these errors were encountered: