Re: understanding structures

[Ralph L. <Ral...@be...>]

On Mon 19 Apr 2010 9:01:00 Marty Kraimer wrote:
> [...]
> Does this mean that for a javaIOC every record has a unique structure?
>
> No. When controls are being implemented for some site, the site will 
> have to select hardware. Normally a relatively small set of different 
> types of hardware interfaces will be chosen. For each type an xml record 
> template can be created that has just the fields required. This template 
> is used to create  the record instances. If existing support works it is 
> attached to the appropriate fields. Only if really unique requirements 
> exist will it be necessary to implement new support.
>
> The same ideas apply to non-hardware related requirements. Define a 
> record template or set of record templates that satisfy the requirements.
>   

Sorry, but I think this is evolving into the wrong direction.

If we leave the creation of standard record types to the sites, this 
will be the end of standards in this area.

One of the central strengths of EPICS (compared to Doocs or Tango) is 
that it features standard record types, thus allowing to share and 
collaborate on device support, and making generic applications possible.
Losing that advantage sounds like a really bad idea.

Having every hardware support create their own specialized record type 
scares the hell out of me.

Ralph