Why would a driver require a user name and password? After all, if you don't have the embosser installed the driver is useless. A dialog box would have to be provided somewhere, but can't we avoid drivers with such a requirement? John On Tue, Nov 30, 2010 at 06:58:22PM -0800, Alex Jurgensen wrote: > Hi John, > > What if the embosser driver requires other parameters, such as a user name or > password? > > Will Braille Blaster display additional parameters in a dialog, after the > "Emboss" button has been pressed. > > If not, should we provide the ability for drivers to present such a dialog as > part of the driver integration process? > > Regards, > Alex, > > > On 2010-11-30, at 2:16 PM, John J. Boyer wrote: > > > The first driver to be developed will of course be the generic driver, > > unless we can pick up some drivers from vendors. All the drivers will be > > in the package embosserdrivers. When something is to be embossed, a > > method in the DriverManager will be called with a String containing the > > name of the embosser and either a file or a byte stream. The latter will > > already have been translated and formatted. The DriverManager will call > > the driver for the appropriate embosser. Each driver will have a class > > of its own. > > > > John > > > > -- > > 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 > -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities