[brailleblaster] Re: Image Describer feedback

  • From: "Keith Creasy" <kcreasy@xxxxxxxxx>
  • To: <brailleblaster@xxxxxxxxxxxxx>
  • Date: Thu, 9 Jan 2014 08:05:48 -0500

The problem of waiting for the document to update is the reason that I 
suggested that the document have it's own thread and be event driven in the 
beginning. I still think that should be the way it works.


Changes to one element (image) should be saved when one moves the focus to a 
different one. That is how the Braille perspective works now.

I noticed we still have an "Apply" button in the perspective but I guess I 
didn't think through why it was there. We do have, and need, an "Apply to All" 
button but applying changes should be transparent to the user just like most 
other document interfaces.

-----Original Message-----
From: brailleblaster-bounce@xxxxxxxxxxxxx 
[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Chuck Myers
Sent: Wednesday, January 08, 2014 4:06 PM
To: brailleblaster@xxxxxxxxxxxxx; NIMAS Digital Production Discussions
Subject: [brailleblaster] Re: Image Describer feedback

I think it was done this way because we didn't want to access the document 
every time there was a keypress. Obviously, we could use a timing mechanism and 
commit the changes after so many milliseconds. It would improve the user 
experience.
________________________________________
From: brailleblaster-bounce@xxxxxxxxxxxxx [brailleblaster-bounce@xxxxxxxxxxxxx] 
on behalf of Larry Skutchan
Sent: Wednesday, January 08, 2014 3:57 PM
To: NIMAS Digital Production Discussions; brailleblaster@xxxxxxxxxxxxx
Subject: [brailleblaster] Re: Image Describer feedback

Couldn't save apply before it saves, or is there a use case for saving without 
applying?


-----Original Message-----
From: nimas-bounces@xxxxxxxxxxxxxxxxx [mailto:nimas-bounces@xxxxxxxxxxxxxxxxx] 
On Behalf Of Chuck Myers
Sent: Wednesday, January 8, 2014 3:35 PM
To: NIMAS Digital Production Discussions; brailleblaster@xxxxxxxxxxxxx
Subject: Re: [Nimas] Image Describer feedback

Okay, I gave the save feature a quick look. You have to hit "Apply" to commit 
your changes before saving. I'm sorry this isn't more obvious. We are very open 
to suggestions regarding the layout.
________________________________________
From: nimas-bounces@xxxxxxxxxxxxxxxxx [nimas-bounces@xxxxxxxxxxxxxxxxx] on 
behalf of Chuck Myers
Sent: Wednesday, January 08, 2014 12:32 PM
To: NIMAS Digital Production Discussions; brailleblaster@xxxxxxxxxxxxx
Subject: Re: [Nimas] Image Describer feedback

The html file is just supplementary data for the browser view. It's not meant 
to be a usable format, so you can ignore it. :) ...and yes, you are correct. We 
are saving changes to NIMAS, but it seems the save feature needs to be 
revisited for a moment. We had this working before...

As far as the browser skipping content, that's an interesting one. I had 
exactly 1 document that exhibited this behavior before, but chose to leave it 
be since it seemed isolated. I chalked it up to bad markup. I'll look at it 
again.

Thanks for testing and finding these issues. We'll get to them ASAP. Keep the 
feedback coming.
________________________________________
From: nimas-bounces@xxxxxxxxxxxxxxxxx [nimas-bounces@xxxxxxxxxxxxxxxxx] on 
behalf of Nicole Gaines
Sent: Wednesday, January 08, 2014 10:30 AM
To: brailleblaster@xxxxxxxxxxxxx
Cc: NIMAS Digital Production Discussions
Subject: [Nimas] Image Describer feedback

Hi, Chuck. In testing the image describer from the BrailleBlaster version from 
12-20-2013, I am finding these issues:

1. Clicking the save button appears to convert the NIMAS file set into an HTML 
file; it does not appear to save the image descriptions. I opened a NIMAS file, 
added several image descriptions, and hit the save button. Then I exited the 
program, started it again and re-opened the same NIMAS file. None of the 
descriptions were in the XML file. However, an HTML file had been generated. 
But in all the places where an image description had been added, the HTML file 
showed "ADD DESCRIPTION!" and not the description.

As an aside, my understanding had been that the goal of the image describer was 
to save changes to the NIMAS, so I'm interested in knowing more about why the 
save is generating an HTML file.

2. The text scrolling does not appear to be working properly. In the file I 
tested just now, the image describer correctly displayed the first image from 
the book, but the XML opened at page 81, not at page 3 where the first image 
appears.

The first 80 pages of the XML file did not render in the image describer at all 
(i.e., it wasn't possible to manually scroll up to the top of the XML). Let me 
know if you would like screen shots for that. Here is where the Image describer 
began the XML file. You will also notice that it rendered some characters oddly:

“Can I help you clean your room?”

“You decide what movie we go to. You have much better taste!”

“I don't like hanging around with your friends. They're much too 
sophisticated for me.”

82
“Can I finish your lima beans?”

“Here's your sweater back. I had it cleaned before I returned it.”

“You don't have to entertain me while Mom and Dad are out. I'll go up to my 
room and read a book by myself.”

“You take the biggest piece of pie. I'm too full!”

83
“I'll be happy to lend you ten dollars. Pay it back whenever you can.”

“Can I do your math homework for you tonight? I don't have much to do.”

“It wasn't your fault. It was all my fault!”

“I saw you were on the phone, so I decided to be silent.”
----------

Thanks!

Nicole

Other related posts:

  1. Home
  2. brailleblaster
  3. Archive
  4. 01-2014