NeXus C++ API

[Mark Koennecke]

  Dear Brian,

On Thu, 10 Jan 2002, Brian Tieman wrote:

> To all,
> 
> I have a C++ API based on NAPI which I've been using for several years now.  The
> API I've created hides the NAPI API almost entirely and allows for a much simpler
> (in my mind anyway) interface to the data.  There is a class wrappered around NAPI
> in the method Mark suggests and this class is the basis to create other classes
> which do closely follow groups, datasets (fields in my naming scheme) and
> attributes.

> .............. deleted some ...................

> 3)  We were toying with replacing NAPI entirely since it's only serving as a
> gateway to HDF.  My API is also generic enough that the underlying file mechanism
> is not what's important (we were thinking of adding NetCDF or HDF 5 to the API
> independant of NAPI)

  If you get the new NeXus-API you can save the work, it supports both
  HDF-4 and HDF-5 transparently.

> 4)  Nexus does not appear to be catching on as a file protocol in the areas where
> I actively develop.  We will likely keep my API, but we may abandon the efforts to
> be Nexus compliant altogether.
> 
  This is interesting. I feel that everybody who is doing new things
  is using NeXus. What is your special area?

                  Regards,

			Mark Koennecke