[brailleblaster] Re: Latest News
- From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
- To: brailleblaster@xxxxxxxxxxxxx
- Date: Mon, 6 Jun 2011 11:41:55 -0500
Here are my responses to the messages from Susan and John G.
The only reason for putting the StyledText widgets inside a Composite,
inside a ScrolledComposite is the runtime error if we try to get the
StyledText scrollbars. This can probably be solved. I prefer the much
simples approach of putting the StyledText widgets directly on the
Shell, where they work naturally. From experience, I distrust the more
complex approach. KISS.
John G, the braille is not line-by-line with the print. Rather, after
translation the Daisy view shows the print corresponding to each line of
braille. This is what we developed UTDML for. If the braille is in Grade
2 the corresponding print might be too long to fit in the Daisy view, so
it would be cut off at the right edge. The user will want the option to
scroll the Daisy view right without affecting the braille view.
The user will also want to disengage synchronous scrolling if she is
adding a lot to one of the views, then scroll the other view until the
print and braille again match up, then lock the views so they scroll
together again. That is certainly what I would want, and what I think
transcribers would want. If they don't get what they want they may just
KISS BrailleBlaster goodbye.
Being able to unlock and relock scrolling is not a difficult
implementation problem. We will need a menu item and hotkey for it. This
is not in the spec, but I think the spec should evolve as we gain more
design experience. users will bless us.
John B.
On Mon, Jun 06, 2011 at 08:54:43AM -0700, John Gardner wrote:
> Hi Chris. Below I put my interpretations of what the specs are or maybe
> what they are supposed to be.
> John G
> -----Original Message-----
> From: brailleblaster-bounce@xxxxxxxxxxxxx
> [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Chris von See
> Sent: Monday, June 06, 2011 8:38 AM
> To: brailleblaster@xxxxxxxxxxxxx
> Subject: [brailleblaster] Re: Latest News
>
> I have a couple of questions on scrolling two StyledText controls
> together:
>
> If a line of text translates into more than one line of braille
> JAG: This cannot happen. Word wrap is removed once the text window shows
> the translation, so the line may go off the page, but it doesn't wrap to
> another line. Unless a user is using a huge font, this should never happen
> anyhow.
>
>
> or if
> the user edits the braille to insert preliminary pages, transcriber's
> notes or other additional content that doesn't appear in the text, how
> will the scrolling controls behave?
> JAG: If a user adds lines or otherwise changes the line formatting, well I
> presume that the two views will continue to scroll, but the lines will be
> mismatched below the point where this occurs. A user can put additional
> lines into both views to keep things synchronized, but she has to do it.
>
> Is the scrolling line-by-line
> based on the lines as seen by the StyledText control, will the
> synchronization between the two controls be based on whatever content
> appears at the top of each control,
> JAG: Yes
>
> or will you use another strategy?
> and will end users be able to "un-synchronize" the two StyledText
> controls so that they can be scrolled independently?
> JAG: No, the user cannot turn off synchronized scrolling. I see no
> overwhelming reason that someone would want to do it. So KISS.
>
>
--
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:
