jrawio 1.6 is an important milestone

24-Sep-2009 09:15 - Filed under: Miscellaneous

The release of jrawio 1.6 is an important milestone, and for this reason I'm giving it a special blog post. There are three major features for this release:

  1. jrawio is now distributed as a single jar file (it.tidalwave.imageio.raw.jar) - no more behavioural differences between putting jrawio.jar only or adding reajent.jar. A new experimental API has been introduced and allows to choose whether reajent should be activated or not. For people wanting to just drop jrawio into their ImageIO - aware application, it is possible to control the behaviour by means of a few system properties. Please have a look at the 1.6 specification page.
  2. jrawio is now officially distributed with support for three environments: plain Java, NetBeans Platform and OSGi. Plain Java and OSGi are supported by the .jar artifact, while the NetBeans Platform is supported by the .nbm artifact. This should make things much easier for people wanting to integrate jrawio in their applications (to be noted that OSGi support has been introduced since 1.5.0, but it was plagued by a few issues). This threefold environment support will be incrementally applied to all the other products made by Tidalwave, starting from Mistral. For curious people, a post at DZone explains how this goal has been achieved.
  3. For the first time in the history of the project, this release has been greatly influenced by a few people in the jrawio community. Great feedbacks, thank you guys, and we are happy to deliver something that fit your needs to the best.
     

People using Maven should be aware that we are using a new repository for publishing the releases - look at the quickstart for more info.

Please try jrawio 1.6 and submit feedback. Also be on the lookout for version 2.0, which will introduce the concept of an officially supported (= stable) API, including a complete redesign of package names. Be aware of that in your plans. Before version 2.0, regular releases will be produced to fix bugs and support more cameras.

 

 

 

 

This blog doesn't allow to directly comment posts. Please provide us with your feedback by means of either the “dev” or the “users” mailing list, as described in the contact page. Thanks!