[brailleblaster] Re: Functional Analysis of BrailleBlaster

  • From: Michael Whapples <mwhapples@xxxxxxx>
  • To: brailleblaster@xxxxxxxxxxxxx
  • Date: Tue, 16 Nov 2010 12:40:09 +0000

Yes that is a start, but to write an application you need to work out a little more detail of each block, which may require breaking it down even further. Also one needs to work out how each block interacts with the other.


As an example of what I mean: An embosser should be able to take a document and report back any error in embossing it. Also one may desire an embosser to be able to be queried for its state (eg. if it has paper, if it is busy, etc) and possibly a few tasks like feed on paper. Now taking the formatting part, is that something to do with the document or should we have a formatter which can tell the document what to do to be correctly formatted? I think it depends on the level of sophistication desired, basic formatting it may be the editor tells the document directly how to be formatted, but if we want automatic styles to be applied then we would want a separate formatter which someone could configure and apply to many documents.

Michael Whapples
On 16/11/10 12:09, Rick Roderick wrote:
I think in terms of the different functions:  importing, translation,
formatting, and embossing.  Is that a way you could divide up work?

Also is there going to be a way to bypass the editor if one wants quick and
dirty braille?




Other related posts: