irmis-devel Mailing List for IRMIS

Naturally, the version number is incremented... And as you could guess,
I edit the message from the last one every time... ;-) 

 

Gabriele

 

From: Carcassi, Gabriele 
Sent: Tuesday, September 29, 2009 4:00 PM
To: irm...@li...
Subject: Re: [Irmis-devel] IRMIS 3.0.10-alpha released

 

Hi all,

 

New release:

https://sourceforge.net/projects/irmis/
<https://sourceforge.net/projects/irmis/> 

 

A couple of minor database changes: removed the foreign key from
PV/lattice to the component database. This provides better independence
between the areas, and the cross-connecting will be done through naming.
The relationship order in the component relationship has been dropped:
ordering will not mean much once we have support for multiple
configuration, so we want to start not relying on it. The GUI already
allows dynamic ordering by other fields, and we'll improve on that so
that one is able to filter and re-order things as he pleases. The other
change was in the lattice relationships: we added a column to keep track
of ordering, so that we support ordering at the same lattice location (A
comes before B even if they are both at 5.035m). The rules on the
creating a lattice a slightly different: elements have to presented in
the right order (i.e. incremental offset) or the transaction is
rejected.

 

Other changes include further refinement of the new fluent Java API, and
retrofitting all the other component to use the new API. If you
experience problems in the GUI, please let me know as it might be side
effects of these changes

 

Full change log is available on Trac at:

http://sourceforge.net/apps/trac/irmis/query?status=closed&group=compone
nt&order=priority&col=id&col=summary&col=owner&col=type&col=priority&col
=component&col=version&milestone=3.0.11-alpha%20(r1093)

 

Gabriele

 

Hi all,

 

New release:

https://sourceforge.net/projects/irmis/
<https://sourceforge.net/projects/irmis/> 

 

A couple of minor database changes: removed the foreign key from
PV/lattice to the component database. This provides better independence
between the areas, and the cross-connecting will be done through naming.
The relationship order in the component relationship has been dropped:
ordering will not mean much once we have support for multiple
configuration, so we want to start not relying on it. The GUI already
allows dynamic ordering by other fields, and we'll improve on that so
that one is able to filter and re-order things as he pleases. The other
change was in the lattice relationships: we added a column to keep track
of ordering, so that we support ordering at the same lattice location (A
comes before B even if they are both at 5.035m). The rules on the
creating a lattice a slightly different: elements have to presented in
the right order (i.e. incremental offset) or the transaction is
rejected.

 

Other changes include further refinement of the new fluent Java API, and
retrofitting all the other component to use the new API. If you
experience problems in the GUI, please let me know as it might be side
effects of these changes

 

Full change log is available on Trac at:

http://sourceforge.net/apps/trac/irmis/query?status=closed&group=compone
nt&order=priority&col=id&col=summary&col=owner&col=type&col=priority&col
=component&col=version&milestone=3.0.11-alpha%20(r1093)

 

Gabriele