Sounds like a fine idea to me. ViewPlus drivers will work in standard Windows mode in the Windows versions of BrailleBlaster, but we need to expand them to work in the Mac and Linux OS. There is aplan to do this, but it is presently only a plan. John G -----Original Message----- From: brailleblaster-bounce@xxxxxxxxxxxxx [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Bert Frees Sent: Sunday, July 17, 2011 4:44 AM To: brailleblaster@xxxxxxxxxxxxx Subject: [brailleblaster] Re: Co-ordinating work on the BrailleBlaster code Hello everybody, I'd like you to consider using brailleutils (brailleutils.googlecode.com), a Java API for embossing and converting braille. I think I mentioned it before. It was written by Joel Hakansson from TPB and I've been working on the project the last couple of months. It now contains about 50-60 embosser models (from Index, Braillo, Interpoint, Tiger, Enabling Technologies, Cidat & Mountbatten). The Tiger models currently use the Tiger driver in Legacy (generic) mode. This means that images & ink + braille interlined are not possible yet. brailleutils is being used in Daisy Pipeline 2 and odt2braille. It would be neat if it was used in BrailleBlaster too. No double work would be done, and any improvements that are made would benefit all 3 projects. I would be happy to help you guys with this if you are interested! Bert Op 16-jul-11, om 22:22 heeft John J. Boyer het volgende geschreven: Now that some people are interested in the BrailleBlaster code, perhaps we can discuss assigning different packages and classes to particular persons. I have already assigned the localization package to my on-site computer tech. The wordprocessor package will be revamped when I have a good grasp of JFace. For now, I want to stick with the present setup, so I can activate some menu items and actually get ?BrailleBlaster to do something. The Main class doesn't need much attention. It just gets things started and shuts them down. BBIni.java gets things set up. I want to keep that for my own work. Subcommands.java is just a skeleton that implements the translate subcommand and the emboss subcommand. Someone might like to flesh it out, using the apache.cli package to process commands. Someone might also like to look at the embosser package. It will contain drivers for each embosser. These will be co-ordinated by the EmbosserManager.java class.ifferent people might write drivers for different embossers. The genreic embosser is already taken care of by the classes in the daisy branch of the Java hierarchy. We need a driver for the Tiger, with appropriate saveguards for proprietary information. John -- Bert Frees Katholieke Universiteit Leuven Dept. Elektrotechniek - ESAT - SCD Onderzoeksgroep Documentarchitecturen Kasteelpark Arenberg 10 bus 2442 B-3001 Heverlee-Leuven België