[brailleblaster] Re: Making the GUI
- From: Alex Jurgensen <asquared21@xxxxxxxxx>
- To: brailleblaster@xxxxxxxxxxxxx
- Date: Mon, 7 Feb 2011 07:36:20 -0800
Hi,
I think that If there are any web related bugs in Orca or any other screen
reader, that we should work with the screen reader manufacturer to fix them.
I feel that strong web support is an essential component of any screen reader
and that this support will become even more important as the web becomes used
for more and more tasks.
Just my thoughts.
Regards,
Alex,
On 2011-02-07, at 6:22 AM, Michael Whapples wrote:
> Hello,
> Firstly I am not quite sure what you mean by the lack of a virtual cursor
> will disadvantage platforms like Linux, I generally would say I prefer orca's
> way of interacting with web pages.
>
> However I do still have concerns for Linux with such an approach, there are
> many gecko bugs and while orca tries to work around them it doesn't always
> quite manage to and so navigation can go a bit wild or it may just be
> painfully slow.
>
> Would the types of controls we want be possible in a browser, I think yes but
> at what cost? I have mentioned some wikis and forums where wysiwyg editors
> are used and accessibility of those are lacking. I still ask for an example
> of a good one which we could try out on various platforms, at least to know
> that such an editor control is possible.
>
> Also it was stated that the user should be able to have both the original
> document view and the translation view open at the same time and that they
> can position these views as they wish. How possible is that in a browser
> window, I would imagine that something like jetty would struggle with
> synchronising between two browser windows (IE. are we constrained to one
> browser control). It may be possible to use some sort of scripting to move
> the views about inside a browser control, but what would the accessibility be
> like around something like that?
>
> Michael Whapples
> On 07/02/11 14:13, Sina Bahram wrote:
>> This can disadvantage platforms like Linux in which there is no virtual
>> cursor support and whose support for the browser is, less
>> than good, let's just say.
>>
>> Also, if we're dealing with specific fonts and translations of lines of
>> input, is a browser control really what we want?
>>
>> Take care,
>> Sina
>>
>> -----Original Message-----
>> From: brailleblaster-bounce@xxxxxxxxxxxxx
>> [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of John J. Boyer
>> Sent: Monday, February 07, 2011 8:15 AM
>> To: brailleblaster@xxxxxxxxxxxxx
>> Subject: [brailleblaster] Making the GUI
>>
>> After investigation it appears that the best approach to makeing the GUI
>> would be to implement the menu structure in SWT and the actual content
>> of the views with Jetty and the SWT browser control. Since SWT uses the
>> native grfaphics controls for each platform, the menus wil appear as
>> they should for that platform. The views will be much more flexible with
>> this approach and can be made more visually pleasing, while remaining
>> accessible.
>>
>> I now have the SWT jar file for the Mac and I have verified that it
>> works. I am using org.eclipse.swt.SWT to get system information, because
>> it can be more specific and perhaps more reliable than the
>> System.getProperty method. It works at the command line, but anything
>> complicated would require a GUI environment.
>>
>> John
>>
>
>
Other related posts: