irmis-devel Mailing List for IRMIS

Hi all,

 

Big release with a few changes that break compatibility.

 

First of all: from now on IRMIS will come in different modules. There
are several reasons behind this push:

* different parts of IRMIS are at a very different level of maturity, so
it makes it impossible to have a non-alpha release for the whole
project. This will allow to tag stable the parts that are indeed so.

* one may be interested in only a piece of IRMIS, and now he/she will be
able to pick and choose what to get

* it will be easier to for different maintainer to contribute separate
modules, as the release schedule will be different for each, and so can
be the choice of underlying technologies.

 

So, each module will come in a separate tarball. All tarballs can be
installed in the same directory (can be put one on the other).

 

As of today, I will be responsible for only the IRMIS Components module.
The IRMIS Lattice module is released "as is" and I will not support it
in the near future (I'd rather concentrate to push IRMIS Components to a
final release and have other commitments in other projects).

 

For someone upgrading, there are a few key compatibility breaking items
you have to keep in mind:

* Only Glassfish 3.x will be supported going forward (I am starting to
use EJBs in a web container, which is not supported in the old
distributions) 

* The database script will move the IRMIS components tables to
irmis3-components, so make sure your db authorization is setup correctly

* The JDBC resource is renamed from irmisDB to irmis3-components, so the
glassfish setup needs to be updated

* All classes in the IRMIS Components API have moved

That should be all.

 

As for new functionality:

* attachment crawler: bundled a script that can crawl a directory and
add component type/component properties based on the content of the
directory. This allows to have a webdav share in which one can drop
files (manuals, reports, images, ...) that relate either to a component
type or to a specific instance and a property with a link to the
corresponding document will appear in the database.

* Better support for keyboard shortcuts in applications

* Reviewed Component Type Editor and Component Inventory to have a more
consistent UI

* Few bug fixes and addition to the Component Type Editor (highlights
which types have changes, new component type always shown regardless of
filter, ...)

* Service now keeps better usage information, including: a directory in
the home directory (of the user running the service) that will contain
each xml transaction and each client application log; a database table
with performance/usage data.

 

Full log at:

https://sourceforge.net/apps/trac/irmis/query?status=closed&group=compon
ent&order=summary&col=id&col=summary&col=owner&col=type&col=priority&col
=component&col=version&milestone=components-3.0.24-alpha%20(r1470)

 

Gabriele

Hi all,

 

Just a heads up: next release will require glassfish 3.x.

 

I am reorganizing the code on the server side, and I am making use of
EJBs to better break up the code. Glassfish 3.x allows EJBs to be
defined inside a web module, without having to define an extra separate
archive.

 

Gabriele

Hi all,

 

New release:

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

 

Fixed a couple of issues with the revised component type editor. The
lightweight inventory system not understands spare containers, which are
recognized as a location for your spares. Right now, one has to set the
"Spare Container" property to any value (either as an installation
property on a particular component or as a component type property which
then applies to all instances of the same type), I will understand how
to give a more native UI solution. Also added ability to edit the label
and color in the cable editor

 

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.23-alpha%20(r1448)

 

Merry Christmas, happy new year, enjoy your holidays (if applicable).

 

Gabriele

 

Hi all,

 

New release:

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

 

Component type editor re-implementation is done. Note that the behavior
is different! Which means, it's actually sane now... You can modify any
number of types, and then save/revert in much the same way that the
cable editor and the component editor works.

 

A couple of minor bugs in the applications were fixed as usual,
including wrong messages in the component inventory and missing error
messages in the saving progress dialog (thanks to Rolf for making me
aware).

 

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.22-alpha%20(r1411)

 

Gabriele

 

Hi all,

 

New release:

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

 

Component type editor now supports mass editing of manufacturer, form
factors, port types and channel types. The integrity check for the
hierarchy is now done only once at the end of the transaction, which
means that one can send a whole transaction that may have "inconsistent
middle steps". This allows, for example, to make extensive changes of
the interface types post facto.

 

A couple of minor bugs in the applications were fixed as usual,
including forbidding properties with blank key.

 

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.21-alpha%20(r1390)

 

Gabriele

 

Hi all,

 

New release:

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

 

Work done on cleaning up parts of the UI, both in term of code and
actual functionality. The component field selection with the tree drop
down now gets the visual appearance of a combo box. The search field for
component types now support auto complete. Starting to add dialog boxes
to do mass editing of functions and interfaces, to allow easier
renaming, merging and other cleanup operations.

 

A couple of minor bugs in the applications were fixed as usual. No
progress on the authentication. 

 

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.20-alpha%20(r1370)

 

Gabriele

 

Hi all,

 

New release:

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

 

Most of the work has been to clean up. On the server side code,
properly handling error cases using http error codes and whatnot. Part
is also preparatory work for finally enabling security: I am waiting for
Glassfish 3.1 to be out (at least in beta) as I am planning to use the
PAM realm which will be included then. Once the security is implemented,
we can finally start calling IRMIS3 a "beta". On the client side, I have
been in trying to stabilize the UI testing infrastructure, and solving
some latent bugs (which never really could cause problems to users). I
also switched the "standard" maven repository I have setup for EPICS.

 

Plus, as a bonus, a couple of minor bugs in the applications were fixed.

 

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.19-alpha%20(r1325)

 

Gabriele

 

Hi all,

 

New release:

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

 

Most of the work has been on infrastructure, migrating from Subversion
to Mercurial and from ant to maven. Note the change in revision number
(going backwards): this is a onetime event caused by the migration.

 

A new addition is the attachment crawler, which allows for files to
automatically become property links within a component. At BNL, for
example, we have a directory exposed through webdav, and it will contain
the following  dir structure: components/ComponentTypeName/SerialNumber.
Any file dropped inside becomes a key/value pair in irmis, where the key
is the filename (without extension) and the property is the http link.
The crawler works just on any filesystem, so the links could be on
shared file system (NFS, AFS, ...), vcs (Subversion, mercurial, ...) and
so on. This is not yet packaged.

 

 I've also fixed a few small bugs in the applications.

 

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.18-alpha%20(r1264)

 

Gabriele

 

There has been some problems with the mailing list at sourceforge: I am
just testing whether everything is working.

 

And since you can see this e-mail, everything indeed is in order! ;-)

 

Gabriele

Hi all,

 

No IRMIS release this month as I mostly worked on CSS and related
things.

 

Cheers,

Gabriele

Hi Chii-jung,

 

The error means that somehow the xml coming from the server is not right. First you should determine whether it’s a server problem.

 

To do this go to:

http://localhost:8080/IRMISDataService/components

http://localhost:8080/IRMISDataService/componentTypes

 

You should see a well formed XML response. You should also look at the server logs (glassfish/domains/domain1/logs/server.log) and see if there are any problems there.

 

If everything is fine, then it may be a client problem: make sure you are using Java 6 on the client, and look at the console output of the java plugin. (Unfortunately where to get the output is OS and browser specific and I don’t know much of CentOS…)

 

I assume you get the error with all applications, right?

 

Gabriele 

 

 

From: 王中 [mailto:wa...@ns...] 
Sent: Wednesday, April 07, 2010 12:00 AM
To: irm...@li...
Subject: [Irmis-devel] Some problem!

 

Dear Sir,

    I have followed instructions on sourceforge to install the IRMIS3 package. When I run the web applications, I have "Read failed: unexpected element (uri:"", local:"message"). Expected elements are <{http://xml.bnl.gov/schema/irmis}attributes>,..." as depicted in the attached file. Since we are rookies to these complicated fields, would you please show us the cause to the problem and ,from whom or where, we could obtain the necessary knowledges of these fields which are totally unfamiliar to us. Sorry for the abruptness. Deeply and sincerely appreciate.

 

Best Regards

 

                                  Chii-jung Wang,    National Synchrotron Research Center Taiwan,    04/07/2010

Hi all,

 

New release:

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

 

Quite a bit more exciting than the last one: 3 new applications! I
expect they will still need some work to polish them, but they are out
of the "developing" phase. The new cable editor is now more polished,
and only allows editing of cables. The bundle editor is a new addition
and allows to edit the information of cable bundle. The component
inventory allows to track component spares and properties attached to
them. The component editor was also modify to allow
installing/uninstalling of spares and to disallows the editing of
component properties (which should be managed by the inventory) while
still allowing the editing of installation properties.

 

The html of all pages was reviewed for cross-browser compatibility and
the main page was reviewed to better hold the links to all the
applications we now have. Some icons were also reviewed since I found
better sources of open source icons.

 

On the server side, the transaction allows to reference newly created
components within the same transaction, avoiding the double traffic of
before. It also means the save button is truly transactional from the UI
perspective.

 

Change log is available 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.17-alpha%20(r1382)
<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.17-alpha%20(r1382)> 

 

Gabriele

 

Hi all,

 

New release:

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

 

Between reviews, snow storms, season sicknesses and the shorter month,
this is not a very exciting release...

 

Minor change in the database: dropped the index that enforced serial
numbers are unique within a component type. This is now implemented as a
business logic rule to allow the special value 'N/A' as not unique,
which can be used for tracking component types where only the count is
interesting or for those components where the serial number is not
entered yet.

 

There were as usual a few improvement in the UI, coming from user
feedback at NSLS-II. I rewrote the layout of the HTML pages so that the
layout is correct on IE. More work was done on the new cable editor
(though is not finished yet) and some preliminary work was done to build
the inventory application.

 

Meager 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.16-alpha%20(r1310)
<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.16-alpha%20(r1310)> 

 

Gabriele

 

Hi all,

 

I uncovered a bug in the service that allowed some actions that should
be forbidden. For example: one could remove a function or an interface
even though they were used by other parts of the database. The bug is
fixed now in trunk and will be added to the next release at the end of
February.

 

Those interested in the details: I didn't quite realize JPA had its own
control for cascade operations, so a delete operation on one object
could trigger the deletion of relationships to other entities. When
switching from JDBC to JPA, then, I lost the check on some constraints
that the database was responsible for. I have appropriately set the
control to just rely on the database, and all is fine. There were
surprisingly very few other bugs that crept in.

 

Gabriele

Hi all,

 

First release of the year:

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

 

No changes in the database, though this month we'll most likely remove
the "number of cables" field in the bundle. Spare cables will become
unconnected instances in the cable table, since we'll need to keep track
of data associated with them (most notably a barcode number).

 

More slew of GUI fixes based on feedback. Among which:

* Adding tooltips and changing command names

* Component Editor is now more keyboard friendly

* Items are better alphabetized in the Component Editor

 

Couple of new features too:

* Component tree in the component browser can now be filtered to display
only a subset of components (i.e. a subsystem)

* Component Type editor can export to HTML

* Properties with hyperlinks as values are now clickable in the
Component Browser 

 

Rest of the time went into further improving the new cable editor (which
is not yet finished) and refactoring part of the GUI elements to make
them more stable and reusable.

 

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.15-alpha%20(r1266)
<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.15-alpha%20(r1266)> 

 

Gabriele

 

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

 

Hi all,

 

Happy Thanksgiving! Releasing a little bit earlier this month:

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

 

No changes on the database.

 

On the infrastructure side, we migrated the build server out of my
laptop to a server. I enabled the interactive GUI tests to run
independently within the build server (so I don't have to sit for 10
minutes at every commit, watching the tests go... it's cool once, maybe
twice...). This means there is a lot more tests being done on the GUIs
than before.

 

On the API/Service side, I finished implementing support for cable
types/functions/bundles and partition types. As for GUIs, the cable
types/functions and partition type editor is finished: I tested by
entering a good deal of data form NSLS-II and it was comfortable enough.

 

Now I am concentrating on revising the cable editor, so that the
interface can scale up to all the cables that need to be inserted. The
current one forces you to drag and drop components one by one, which you
may not be efficient if you have hundreds of components to cable...

 

On the PHP front, Peter added support for barcodes in the PHP inventory.

 

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.13-alpha%20(r1164)
<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.13-alpha%20(r1164)> 

 

Gabriele

 

Hi all,

 

New release:

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

 

We started to implement support for cable types/functions/bundles/paths,
which can be used to keep track of how cables are used and pulled across
a site. We plan to develop and use these future to plan and capture the
cable information for NSLS-II. There is a schema update script to create
the tables, and part of it is already supported at the service and API
level (all except the bundles and paths).

 

I also reviewed more closely the GUI widget, which solves a few issues
that would crop up from time to time.

 

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.12-alpha%20(r1115)

 

Gabriele

 

Hi all,

 

We are finalizing the schema that keeps track of where cable are pulled
across the site, through trays partitions and all. The new addition will
have a set of additional constraints that cannot be satisfied when
upgrading. For example, each cable bundle that is being pulled will
require to have the cable type associated with it: given that we
previously did not have cable types either, there is no away to upgrade
the database enforcing this requirement.

 

In this case, what I would do is have two scripts: one that upgrades
with the constraints turned off, and a separate script to turn on the
constraints that one would run after the data is fixed.

 

I am assuming, though, that no-one really populated that area of the
database (cable_pull, cablepull__traysegment), given that there was very
limited support. Therefore I will be preparing only one script that
simply assumes no data is there. (Note that cables/conductor themselves
are not affected)

 

If you have populated data only from the GUI or from the Java API, you
are guaranteed to not be affected. If you have no idea what I am talking
about, you are most likely not affected either.

 

If anybody did in fact put some data in, either through the service or
through direct access to the db, please let me know and I'll prepare the
extra scripts.

 

Thanks!

Gabriele

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

 

Hi all,

 

It's that time of the month:

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

 

Doug has worked on a tool to create text file templates that then get
populated with data from IRMIS. This will be useful for creating
configuration files using the data in IRMIS, such as DHCP configuration,
writing scripting to forward data, for example to an LDAP server, or
simply create text reports. This is not included in the release, since
we haven't finalized the packaging and all, but it's in subversion for
whoever wants to have a look. An overview can be found here:

http://irmis.svn.sourceforge.net/viewvc/irmis/docs/20090804.Doug_Sheffer
.IRMIS_Templates.pdf?revision=1054

 

Apart from a couple of fixes, there are no externally visible changes in
the application. Most of the time I have been spending improving (and
clarifying) the thread safety and immutability rules of the Java API. I
am also writing a more advanced query API to browse through components
and group changes. This is all work that should simplify the internals
of the API, making it easier to extend and support future functionality.

 

Full change log is available on Trac at:

https://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.10-alpha%20(r1052)

 

Gabriele

 

Hi Gabriele,

 

Please go ahead and add my name and email address:

 

quock=Debby Quock <qu...@ap...>

 

 

Thanks,

 

Debby

 

  _____  

From: Carcassi, Gabriele [mailto:car...@bn...] 
Sent: Thursday, July 30, 2009 11:20 AM
To: irm...@li...
Subject: [Irmis-devel] Migration to Mercurial

 

Hi all,

 

I have been doing some preliminary work to migrate to a distributed version
control system, namely Mercurial. After fiddling around, I am able to import
the repository with the whole history in the following directory structure:

 

- contrib (contains projects that are either experimental, or they are just
not going to be part of the standard distribution. Essentially it contains
what branches used to contain, since we weren't using branches a real
branches)

- docs (contains the documentation as before)

- trunk (contains the trunk as before, which constitute the main
distribution)

 

We may revise this directory structure, but it would be done as a separate
step as to not complicate things further.

 

There are two things I'd like to ask. First, if there is any reason to
postpone this migration (for example, someone has some work in the pipeline,
.).

 

Second, I will need to convert the usernames in subversion to ones used
according to the standard practices in distributed systems, which is simply
to use full names and e-mail address. I have made this tentative list, where
the e-mails are taken at the time of the contribution. Please, check the
spelling of your name and your mail address and let me know of any changes
you may want.

 

carcassi=Gabriele Carcassi <car...@bn...>

pbbeard=Peter Beard <bea...@ns...>

desheffer=Doug Sheffer <sh...@bn...>

berryma4=Eric Berryman <eri...@gm...>

dondohan=Don Dohan <do...@bn...>

karipid=Dan Karipides <ka...@tx...>

all5145=Amber Liverpool <liv...@bn...>

vikikivi=Vikram Aravamudhan <va...@bn...>

 

There are a few things I still need to sort out (so, this is not final yet),
but if everything goes well and nobody objects, I will probably make the
migration next week. I will make an announcement when I start the conversion
(so that people don't commit during that process) and when the conversion is
finished.

 

Thanks,

Gabriele

Hi all,

 

I have been doing some preliminary work to migrate to a distributed
version control system, namely Mercurial. After fiddling around, I am
able to import the repository with the whole history in the following
directory structure:

 

- contrib (contains projects that are either experimental, or they are
just not going to be part of the standard distribution. Essentially it
contains what branches used to contain, since we weren't using branches
a real branches)

- docs (contains the documentation as before)

- trunk (contains the trunk as before, which constitute the main
distribution)

 

We may revise this directory structure, but it would be done as a
separate step as to not complicate things further.

 

There are two things I'd like to ask. First, if there is any reason to
postpone this migration (for example, someone has some work in the
pipeline, ...).

 

Second, I will need to convert the usernames in subversion to ones used
according to the standard practices in distributed systems, which is
simply to use full names and e-mail address. I have made this tentative
list, where the e-mails are taken at the time of the contribution.
Please, check the spelling of your name and your mail address and let me
know of any changes you may want.

 

carcassi=Gabriele Carcassi <car...@bn...>

pbbeard=Peter Beard <bea...@ns...>

desheffer=Doug Sheffer <sh...@bn...>

berryma4=Eric Berryman <eri...@gm...>

dondohan=Don Dohan <do...@bn...>

karipid=Dan Karipides <ka...@tx...>

all5145=Amber Liverpool <liv...@bn...>

vikikivi=Vikram Aravamudhan <va...@bn...>

 

There are a few things I still need to sort out (so, this is not final
yet), but if everything goes well and nobody objects, I will probably
make the migration next week. I will make an announcement when I start
the conversion (so that people don't commit during that process) and
when the conversion is finished.

 

Thanks,

Gabriele

Hi all,

 

Time for a new release:

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

 

The biggest news is the contribution of the PHP API from Peter Beard
(National Superconducting Cyclotron Laboratory). Like the Java API, sits
on top of the service layer and consumes the XML. It is bundled with the
service layer, a tarball with the code plus the output of doxygen for
reference documentation.

 

Most of the rest of the work has been on the applications. Doug Sheffer
added channel support in the ComponentType editor. Other improvements:
per node ordering in the component trees, better and more consistent
ComponentType search panel, Excel export of a set of components and
various bug fixes. I have also started to review part of the Java API,
mainly to make it more "script friendly" by allowing to make complex
operations more readily available.

 

We should also celebrate another milestone: today we had our 1000th
commit to our repository!

 

Full change log is available on Trac at:

https://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.9-alpha%20(r1012)

 

Gabriele