irmis-devel Mailing List for IRMIS
Status: Alpha
Brought to you by:
carcassi
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(2) |
Feb
(10) |
Mar
(5) |
Apr
(5) |
May
(1) |
Jun
(3) |
Jul
(3) |
Aug
(1) |
Sep
(2) |
Oct
(2) |
Nov
(1) |
Dec
(1) |
| 2010 |
Jan
(2) |
Feb
(1) |
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2011 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
1
|
2
|
3
|
4
|
5
|
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
|
27
|
28
|
29
(1) |
30
|
31
|
|
|
|
From: Carcassi, G. <car...@bn...> - 2009-12-29 20:18:58
|
Hi all, Merry Christmas! Happy new Year! Hope you are enjoying the holidays (if you have them)! Time for a new release: https://sourceforge.net/projects/irmis/ <https://sourceforge.net/projects/irmis/> No work on the database side, but we finally included the database schema as part of the documentation. On the service I completed the support for cable bundles. Most of the work went into the GUIs. Fixed a few minor problems with the current applications based on the feedback received by users (e.g. display functions/interfaces in alphabetical order in the component type editor, allow to use the right tree as a reparenting child in the component editor, etc...). But most of the work is going into the new cable editor, to allow editing large number of cables easy. Another feature that is partially implemented, and will work on to extend next month, is the ability to reference newly created objects within the same transaction. For example: <transaction xmlns="http://xml.bnl.gov/schema/irmis"> <create> <cableBundle cableCount="10" bundleLabel="bundleTest-1155484576" cableTypeId="1" id="-2"> <partition partitionTypeId="1" componentId="2"/> </cableBundle> </create> <connect> <cable cableTypeId="1" cableBundleId="-2" componentBId="16" portBId="22" componentAId="10" portAId="11" label="bundleTest-1155484576"/> </connect> </transaction> The first part creates a cableBundle and the second part connects a new cable within that bundle. The idea is that by giving a negative number for id at cableBundle creation, one can then use that same negative number to reference the cableBundle later. I intend to extend this to any entity type in any transaction element. This will, for example, avoid the double trip that is currently needed when creating a set of components (first you need to create them, then you need to establish the relationships since you need the id to create references). It should not only improve performance, but also avoid residual garbage in case of problems. 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.14-alpha%20(r1211) <http://sourceforge.net/apps/trac/irmis/query?status=closed&group=compon ent&order=priority&col=id&col=summary&col=owner&col=type&col=priority&co l=component&col=version&milestone=3.0.14-alpha%20(r1211)> Gabriele |