I wrote a lot of image io stuff for my own projects before I became aware of skimage. I spent some time thinking about how people could add and maintain their own modules, and came up with the following:

io/

__init__.py

tiff.py

read()

write()

png.py

read()

write()

etc. This isn't coded, it was just on my todo. Adding new formats is then a matter of dumping in a file containing read() and write() functions, and importing that in the __init__.py file. This results in very clean syntax:

io.png.read()

There could also be io.read() and io.write() defined in __init__ or some generic name, e.g. io.auto.read(), that would call the right format based on filename.

Thoughts?

On Fri, Apr 19, 2013 at 10:47 PM, Stéfan van der Walt <stefan@sun.ac.za> wrote:

Hi Almar

On Wed, Mar 27, 2013 at 4:33 PM, Almar Klein <almar.klein@gmail.com> wrote:

> The project is called imageio and it is now a plugin-based library with a
> relatively small core. The freeimage plugin that started it all currently
> provides most file formats. Its now at a stage where I think the core is
> pretty much finished, and focus can shift towards different plugins for
> various scientific formats. But I am not going to do that alone :)

Is there a way to add plugins by simply "dumping" plugin files into
place? This was part of the thinking when we designed the skimage.io
plugin infrastructure (so it would be easy for, e.g., Debian to add
new formats by simply unpacking into the right location).

I am not entirely happy with the complexity of the io module in
skimage, and would love to hear ideas about how it can be simplified,
perhaps integrating with imageio.

Stéfan

--
You received this message because you are subscribed to the Google Groups "scikit-image" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scikit-image+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.