>>>>> "Stuart" == Stuart Ballard <[EMAIL PROTECTED]> writes:

Stuart> One thing I'd like to do once the generics branch becomes the
Stuart> main development trunk is to scan the source for FIXME, Not
Stuart> Implemented, etc and add a @Fixme or @Stub or @NotImplemented
Stuart> or something annotation to each such class/method. When Japi
Stuart> gets support for annotations, I'll be able to tweak it so that
Stuart> any member that has one of these annotations gets flagged in
Stuart> the Japi report.

This sounds quite nice.  With @Documented we can have these things
show up in the javadoc as well.

The most important ones for me are the stubs; many of the FIXME-type
comments are actually quite minor, but with the current setup it is
hard to distinguish these from methods that should do something that
don't, or methods that throw an Error and don't have an associated
FIXME.

Stuart> This doesn't, of course, help with classes that are
Stuart> implemented entirely but rely on some backing implementation
Stuart> or provider that implements a public API but isn't itself
Stuart> public. Japi can only go so far, unfortunately ;)

Mark's talk at FOSDEM was called something like 'beyond japi', but we
never really got around to this exactly.  I made a crude list of
possible tasks that would be useful but which would not show up in a
japi run.  I've appended it, let me know if I missed something.

Tom

Beyond JAPI

java.awt
  More back ends
  E.g., Mac OS X, Windows

java.nio
  More character sets
  Perhaps some optimizations possible

java.util.prefs
  gconf back end?

javax.crypto
  algorithm implementations
  we're doing pretty good here

javax.imageio
  various plugins

javax.naming
  not sure...
  at least ldap code

javax.print
  platform-specific printing back ends

javax.security.kerberos
  link to a real kerberos implementation

javax.sound.midi
  not sure

javax.sound.sampled
  works with tritonus but more could be done
  add some built-in file formats
  link to gstreamer to jack or ...

javax.swing
  write a plaf that uses gtk to do the rendering
  and thus allows native themes


Other things needing more-than-obvious support

Graphics2D
Regular expressions
  good work happening here
Locale stuff
  we seem to be reasonably good here
  but could compare against ICU4J
Security coverage
  good work happening here
URL protocol handlers
  also looking good afaics
Tools - see ongoing discussions about integrating them, etc
Documentation
  missing javadoc is pretty obvious but doesn't show up in japi

Reply via email to