[brailleblaster] Re: Editor
- From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
- To: brailleblaster@xxxxxxxxxxxxx
- Date: Sun, 29 Jul 2012 13:56:04 -0500
The Sourceforge project ulses Swing. BrailleBlaster uses SWT. Combining
the two is not advisable.
I would prefer something that uses xml natively, rather than html.
Hanxiao is working on editing. This may take some time, however.
I've been wondering if it is feasible to split the editing functions off
from DocumentManager and put them in a separate class. That would mean
that one person could work on DocumentManager and another could work on
Editor, without needing to worry about merging the files.
StyledText can handle images. We are thinking of using jeuclid for
displaying math on the print sode.
When using UTD, the Braille view should be editable, but the Daisy view
should be read-only, since it simply shows the print that corresponds to
each line of Braille. Synchronizing the two views is indeed a problem.
They should scroll together, but it should also be possible to unlock
the scrolling. The Braille view will eventually display tactile images.
There are plans to include a 6-key entry method for editing Braille. I
think that in general screenreaders will be able to provide this and
also, of course, operate Braille displays. That's one of the things I
will be sure to include, since I use a Braille display.
I don't understand the back-translation problem as it is explained. It
is likely to be a problem with the tables rather than with the code.
Updating both the code and tables would be the best approach.
John
On Sun, Jul 29, 2012 at 01:28:22PM -0400, Keith Creasy wrote:
> I've spent some time this weekend looking over the current state of
> BrailleBlaster. My main thoughts so far are:
>
>
>
> The text editor/view needs to display the DAISY/NIMAS document as HTML with
> mixed fonts and images. Maybe we could use something like
> http://djproject.sourceforge.net/ns/ to do this? Please check it out and
> share your thoughts. Showing images is important since many textbooks
> contain images that need descriptions and also use images for such things as
> diagrams and math equations. This is where BB can shine by providing a nice
> user interface for expressing these items in text or Nemeth braille. XSL
> transforms can be used to render the XML to HTML for viewing and editing.
>
>
>
> Along with this is the need to support or allow one to use a braille display
> and keyboard to directly edit in the braille view. Maybe the screen readers
> can be used to make this work. Not sure. It would be great if the braille
> keyboard/display could be locked onto the braille view somehow.
>
>
>
> The braille view is read-only. We can probably use the current StyledText
> view for editing braille since we won't need images or mixed fonts in
> braille.
>
>
>
> We'll need a mechanism for synchronising the two views. I'm thinking the
> parent view can be notified of any edits to either view and then send a
> message with the view that changed and an object containing information
> about the change. Android has a nice structure for doing this and LibLouis
> provides information about the current offsets for braille and text. We use
> this for the Braille Plus' braille editor to synchronise the braille editor
> with the edit control in the Android app.
>
>
>
> In my opinion this is what is most needed in BB to make it the kind of
> powerful tool we want and need. Let's think about this and try to identify
> the best way to get this accomplished. I'm willing to put in some developer
> time-my own time-to work on it but we need to agree on what
> libraries/controls to use.
>
>
>
> Also, we found a translation bug in LibLouis but our library is out of date.
> Does anyone know off hand if it still reverse-translates "update" to
> "upaidate"?
>
>
>
> Thanks.
>
>
>
> Keith
>
>
>
--
John J. Boyer; President, Chief Software Developer
Abilitiessoft, Inc.
http://www.abilitiessoft.com
Madison, Wisconsin USA
Developing software for people with disabilities
Other related posts:
