[Nexus] [NeXus-committee] NXmonochromator for todays telecon

[Eugen Wintersberger]

If, as Mark and Tobias pointed out, NXcrystal is a utility class which
can be used to build things up, we have to do nothing. 
In this case my "Radical solution" is already reality and I am fine with
it ;)
I just wanted to ensure that this is the case. 

Just one comment on inheritance vs. composition. Though the GoF pointed
out that composition is superior over inheritance, this does not mean
that inheritance is useless or should be avoided at all. Just like all
design tools it should be used with care ;)

regards
  Eugen


On Wed, 2015-03-18 at 10:36 +0000, Koennecke Mark (PSI) wrote:
> Hi, 
> 
> 
> 
> > Am 18.03.2015 um 11:26 schrieb Tobias Richter
> > <Tobias.Richter at esss.se>: 
> > 
> > Hi,
> > 
> > My expectation was the NXcrystal would be a child of NXmonochromator
> > as an element used to build the thing up. 
> > That view is supported by the current documentation as far as I can
> > tell. In the last NIAC he approved NXgrating with the same rationale
> > (with isn’t fully documented yet - it isn’t referenced anywhere).
> > 
> > So I would think that, as valid as they they have been at the time,
> > the original intentions for NXcrystal are not binding. People
> > independently worked out a different, but consistent and valid
> > interpretation and we should honour that.
> > 
> > 
> 
> 
> My explanation about NXmonochromator was more historical. The only
> meaning of NXmonochromator in the OO sense is that there are some 
> fields like wavelength etc which should be in derived classes. 
> 
> 
> What I also wrote (or meant to write) is that OO in NeXus never took
> on and we are drifting towards composition solutions with either 
> interfaces or features. We are more or less free to do as we like. And
> add new classes for the new monochromator types. 
> And leave the rest until we sorted out either features or interfaces.
> 
> 
> Regards,
> 
> 
>      Mark
> 
> 
> 
> 
> 
> 
> 
> > That’s a different solution to either of the ones in your document,
> > correct Eugen?
> > 
> > Tobias
> > 
> > 
> > > On 18 Mar 2015, at 10:33, Eugen Wintersberger
> > > <eugen.wintersberger at desy.de> wrote:
> > > 
> > > Hi folks  
> > > as I was unabel to edit the wiki in finite time you will get my
> > > suggestions concerning NXmonochromator as an attachment to this
> > > mail. 
> > > I guess we should at least start a discussion about this today. 
> > > 
> > > regards
> > > Eugen
> > > 
> > > PS: yes Pete, it was made with LaTeX (even the figures) ;)
> > > -- 
> > > ------------------------------------
> > > DI. Dr. Eugen Wintersberger         
> > > 
> > > FS-EC                              
> > > DESY                    
> > > Notkestrasse 85                       
> > > D-22607 Hamburg                    
> > > Germany                            
> > > 
> > > E-Mail: eugen.wintersberger at desy.de
> > > Telefon: +49-40-8998-1917          
> > > -----------------------------------
> > > <nxmonochromator.pdf>_______________________________________________
> > > NeXus-committee mailing list
> > > NeXus-committee at nexusformat.org
> > > http://lists.nexusformat.org/mailman/listinfo/nexus-committee
> > 
> > 
> > _______________________________________________
> > NeXus-committee mailing list
> > NeXus-committee at nexusformat.org
> > http://lists.nexusformat.org/mailman/listinfo/nexus-committee 
> 
> 
> _______________________________________________
> NeXus mailing list
> NeXus at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus

-- 
------------------------------------
DI. Dr. Eugen Wintersberger         
                                    
FS-EC                              
DESY                    
Notkestrasse 85                       
D-22607 Hamburg                    
Germany                            
                                   
E-Mail: eugen.wintersberger at desy.de
Telefon: +49-40-8998-1917          
-----------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part
URL: <http://lists.nexusformat.org/pipermail/nexus/attachments/20150318/d97db2d8/attachment-0001.sig>