Jerry, Glad you found that useful. Also, I wanted to let you know that I've finished work on this document:
http://wiki.rifidi.org/index.php/Package_Structure_for_a_reader_project That describes in detail all of the different classes, packages, and interfaces needed to make a bare bones reader. I think that should help get you started. If you come up with an idea for how your BitEncodedCommands interface would be useful, let us know. -Kyle Information about Rifidi Development wrote: > I /really/ have to admit that Interfaces (and examples of extended > classes) used in the Symbol reader really helped me know what the > signatures are supposed to look like and what methods to include... > especially with the Eclipse auto-create stubs of abstract methods. And I > have one other suggestion for an interface... I will use Symbol for an > example: > > public class BitEncodedCommands implements EncodedCommands { > ... > } > > That way it would be easier to do polymorphism (Don't know how that > would be useful right now, but I think it would be down the road.) and > creating stubs in Eclipse. > > Comments or Suggestions? > > Jerry > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Rifidi-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/rifidi-developers > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Rifidi-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rifidi-developers
