Hi John, Will text-based PDF's work as input to this command? I also tink that the perameters I specified should still be included. These features would allow me to write a printing workflow that will show up in the Mac's print dialog. I really apreciate your feedback on whether or not you think that a quick-emboss dialog should be included as part of the native platform's print dialog. think Regards, Alex, On 2010-11-29, at 11:05 PM, John J. Boyer wrote: > Alex, > > Thanks for the idea. We can do even better than Louis on the Mac. The > liblouisutdml tool file1brl will be available as a subcommand. This is > basically the same as the old xml2brl. It will produce nicely formatted > braille from a template. The embosser would have been set beforehand. So > the command would look like > > brailleblaster file2brl templatename inputfilename > > This should be simple enough to do. The big problem would be getting the > embosser driver. I can help someone who wants to work on this feature. > My own work will center on laying the groundwork for the word processor. > > John > > On Mon, Nov 29, 2010 at 10:22:26PM -0800, Alex Jurgensen wrote: >> Hi All, >> >> I was thinking that it might be a good idea to produce a quick-Braille mode >> at the command-line for a first version. We can always add this later into >> the binary if we feel like it. >> >> My idea is a Command-Line tool that can be a sub-command of Braille Blaster >> that would allow the user to quickly emboss ad document without needing to >> format it. This is similar to the functionality of Louis for Mac >> http://www.cucat.org/projects/ but without the GUI. >> >> For example, a user could enter: >> >> $ brailleblaster quickemboss --width 40 --height 25 --embosser tiger_pro >> myFile.txt >> >> This would send the document "myFile.txt" to a Tiger Pro embosser with 40 >> cells across the page and 25 down. >> >> I think this would be a good first goal of the Braille Blaster project as it >> would allow both the input classes and embosser driver classes to be written >> while creating something that can be used right away. >> >> The only downside to this idea that I can see is the fact that the UI will >> not be developed at the same time, because work on the UI related classes >> would stop while the quick-emboss feature is written. However, if someone >> continues to work on the UI classes while others work on the quick-emboss >> feature, I think that we can avoid the problem. >> >> If this does not sound good as a first goal, I suggest that we should >> include this feature in the final release of Braille Blaster. >> >> Please let me know what you think. >> >> Regards, >> Alex, >> >> >> Alex Jurgensen, >> VoiceOver Trainer, >> ASquared21@xxxxxxxxxxxxxxxxx >> >> Visit us on the web at: www.vipbc.org >> > > -- > John J. Boyer; President, Chief Software Developer > Abilitiessoft, Inc. > http://www.abilitiessoft.com > Madison, Wisconsin USA > Developing software for people with disabilities > > Alex Jurgensen, VoiceOver Trainer, ASquared21@xxxxxxxxxxxxxxxxx Visit us on the web at: www.vipbc.org