Hi GW Scripters,

  I've been working on this Braille encoding library for the .NET
Framework and I have a question that does not address a problem, but
rather your opinions: I would appreciate some feedback.

1. Is this something that .NET developers who are blind would find
useful if I release the library only, without a user interface? It
will support contracted and Nemeth Braille, and the level of
abstraction would be raised higher than, say, Liblouis or software
that requires one to implement a Braille table, which means tinkering
with another language (programming wise, that is).

2. If useful, should I add methods such as Parallel and/or
asynchronous translation for say web projects or Windows 8? Are those
reasonable additions?

The programming/object model will look like this, atleast in C#:

using CoreComponents.Braille; // CoreComponents is part of the
framework I'm building.
namespace BrailleExample
{
class Program
{
public static foid Main(string[] args)
{
// In just 3 lines, you can have translation!
SmartEncoder testVariable = new SmartEncoder();
string textToSave = testVariable.Translate(inputText,
EncodingOptions.AsContractedBrailleWithNemeth);
// Parallel translation:
testVariable.TranslateParallel(); // Same parameters apply.
// Now, asynchronous:
Task<string> content = await textVariable.TranslateAsync(); // Same
parameters apply.

}

}
}
Thanks in advance,
Regards,
Kevin Morales

Reply via email to