[ome-devel] Image impoorters

[Ilya Goldberg]

I added a new branch: IMPORT_CLEANUP_2006-06-27
Instead of tagging the whole code-base, I tagged only the OME/src/ 
perl2/OME/ImportEngine directory.  The other stuff fixed bugs that  
were common to HEAD anyway.
So to check it out, you have to do a couple things:

# Do a new checkout into a new directory
cvs co OME
# Rename it
mv OME OME-IMPORT_CLEANUP_2006-06-27
# Go to where the branch point is
cd OME-IMPORT_CLEANUP_2006-06-27/src/perl2/OME/ImportEngine/
# Update based on the branch
cvs up -r IMPORT_CLEANUP_2006-06-27
# Back out to the top level
cd ../../../..
# Install away
sudo perl install.pl -y


The thing to do is to see if it still imports your test images.  It  
imports all the test images we have here:
http://openmicroscopy.org/TestImages/

-Ilya



On Jun 23, 2006, at 11:07 AM, Ilya Goldberg wrote:

> Hi All
> I know that some of you have developed your own flavors of image
> importers for getting images into OME.
> I have been working on some much needed cleaning up, bug fixing and
> optimizations in the import code (sub-classes of
> OME::ImportEngine::AbstractFormat), but unfortunately it will almost
> certainly break importers that are not in the code-base.
>
> Basically I wanted to take a little survey to find out how many
> custom importers are out there, and how this transition should be
> handled:
> A.  Commit new importers to CVS-HEAD and wait for the screaming.
> B.  Commit new importers to a branch for testing, then move to HEAD
> and wait for the screaming due to the ignored branch.
> C.  Volunteer to fix other people's importers for them.
>
> Probably everyone would prefer option C, but that all depends on how
> many of you are out there.
>
> -Ilya
>
> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>