On Wed, 8 Jan 2003, Dan Streetman wrote:

> 
> Ok, the 0.10 API, common RI, and Linux RI (which are all in CVS only)
> are essentially working at a beta level.  The UsbView (swing) app is
> updated for the new API methods (mainly offset/length and using
> ControlUsbIrps instead of Requests).  The JavaDOC is linked to
> from the main page (http://javax-usb.org/).  Besides the changes I
> suggested long ago, there a few more; if anyone has comments, please
> reply!  Also, if you have time, please try out the implementation.

I'll try it shortly (perhaps today).

> -All Descriptors' methods are renamed to exactly match the field
> listed in the USB spec.  For example:
> InterfaceDescriptor.getInterfaceNumber() -> bInterfaceNumber()
> ConfigDescriptor.getConfigNumber() -> bConfigurationValue()
> and so on.  My reasoning is, there is no need to reinvent a set of
> names to describe the same set of values; simply using the exact names
> as specified in the USB spec makes everything more consistent and
> easier to remember.  That's my reasoning at least, does anyone else
> feel differently? :)

I'm not to fond of setting the variable storage type (not variable type) 
in front of the methods. Hungarian notation at least tells what type of 
value the variable holds. But I see your point of following the PSecs 
notation.

> -Added bString to StringDescriptor, and getString throws
> UnsupportedEncodingException.  The bString is just the raw byte[],
> which the StringDescriptor should have.  The actual String though, has
> to be translated and it's possible the JVM doesn't have the encoding
> to translate it.

This issue is still foggy to me. Does anyone here have the 2 books 
referenced at page 205 in the usb spec? ("The Unicode Standard, Worldwide 
Character Encoding, Version 1.0 Volume 1 & 2" The Unicode Consortium, 
Addison-Wesley Publishing Company.) Section 9.6.5 in the USB specs only 
says UNICODE encodings, but to me this gives a whole range of possible 
encodings. And there is no way (that I can see) to find out which encoding 
is used. I'm guessing UTF-8 is used, but I do not know.

The rest seems fine at a glance, but I might change my mind after trying 
to use it ;-) 

//Roger



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
javax-usb-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/javax-usb-devel

Reply via email to