[brailleblaster] Re: Displaying and editing documents

I can. Let me first find out if there is an official way for developers to gain 
access to sample content. If not there should be.

Keith


-----Original Message-----
From: brailleblaster-bounce@xxxxxxxxxxxxx 
[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of John J. Boyer
Sent: Wednesday, May 09, 2012 6:25 PM
To: brailleblaster@xxxxxxxxxxxxx
Subject: [brailleblaster] Re: Displaying and editing documents

Hi Keith,

Is there some way the BrailleBlaster community could have access to some sample 
NIMAS files? This would be a big help in determining how to display them. 

John

On Wed, May 09, 2012 at 11:28:59AM -0400, Keith Creasy wrote:
> I can imagine that displaying a NIMAS file correclty could be a bit of a 
> challenge unless we just use a web view of some sort. We'll have to consider 
> what is acceptable or whether we can actually use an HTML rendering engine.
> 
> K
> 
> 
> -----Original Message-----
> From: brailleblaster-bounce@xxxxxxxxxxxxx 
> [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of John J. 
> Boyer
> Sent: Wednesday, May 09, 2012 11:25 AM
> To: brailleblaster@xxxxxxxxxxxxx
> Subject: [brailleblaster] Displaying and editing documents
> 
> At present, when a file is loaded every text node in the document is simply 
> displayed. This needs to be improved. Probably we should use an xsl 
> stylesheet, but we still need examples of how the document should look. I.e., 
> How should the display of a NIMAS document look?
> 
> In the case of displaying a document which has been translated with UTDML, 
> the Braille is displayed on the right, and the print corresponding to the 
> braille line is displayed on the left. No stylesheet is needed.
> 
> In both cases, we need to work out how the files are edited. The underlying 
> xml document is handled by xom, a package for parsing, building and 
> manipulating xml files. The intermediate level will be handled by overriding 
> methods in the SWT StyledTextContent class. There is already a BrailleContent 
> class and a DaisyContent class. They need to be fleshed out.
> 
> The "top" level is of course what the user enters on the screen. This will be 
> handled by events and listeners in the content classes.
> 
> Thanks,
> John
> 
> --
> John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc.
> http://www.abilitiessoft.com
> Madison, Wisconsin USA
> Developing software for people with disabilities
> 
> 

--
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: