[Nexus-developers] Java helper routines

[Campbell, SI (Stuart)]

Mark (and everyone)

I'm not sure what I have actually done should be put directly into the
distribution as it is very focussed and integrated into our acquisition
system...and probably poorly written! :-)  Therefore, I don't think that
my class structure would be of use to anyone else. 

Looking at what Pete has done is probably a better (more generic)
starting point.

But I do think that it is worth a discussion in the NIAC meeting and us
agreeing on how to proceed.  I think that the main questions that we
need to address are...

1) The Class Structure
2) Languages to support 
3) Where to put it ? Contrib or API

Cheers
Stu

-----Original Message-----
From: nexus-developers-bounces at nexusformat.org
[mailto:nexus-developers-bounces at nexusformat.org] On Behalf Of Mark
Koennecke
Sent: 04 September 2007 14:10
To: nexus-developers at nexusformat.org
Subject: Re: [Nexus-developers] Java helper routines

Stuart,

Campbell, SI (Stuart) schrieb:
> Hi everyone,
>
> Just wanted to ask people's opinions on a suggestion...
>
> I have been playing with the jnexus API quite a bit recently.  I have
> been wrapping a lot of the NAPI functions in routines that make it
feel
> more Java/OO like (and I think that Pete has been doing something
> similar).
>
> I was wondering if this sort of thing is something we should consider
> including in the distribution for Java and maybe even other OO
> languages.
>
> The main question probably is whether it should be included in the
> 'contrib' area, or added on top of the jnexus stuff.
>
> What does everyone think ?
>
>   

In general I do not mind adding this to the main NeXus-Java 
distribution. I even think this is a
good idea. But I would  like to ask you to do the following:

Make a little presentation about what you did and how you did it for the

next NIAC meeting
and we should this. There are various issues we have to agree upon:
- Is your class structure agreeable to everyone?
- Also for other OO languages?
- When I wrote the Java-NeXus API (way back in time it seems) I thought 
hard about a more OO
   approach. I then realized that the HDF-API is its own state machine 
and it would be quite hard to
   keep track of this state.  I would be interested how you solved this.

Do you keep the file structure
   in memory (with deferred loading for large datasets)  and deserialize

and serialize on
   NXopen/NXclose?
 

                         Regards,

                                     Mark
_______________________________________________
NeXus-developers mailing list
NeXus-developers at nexusformat.org
http://lists.nexusformat.org/mailman/listinfo/nexus-developers
<DIV><FONT size="1" color="gray">This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
</FONT></DIV>