The road to 1.0

[jcupitt]

This issue is to track progress towards a 1.0 public release.

• [x] Look through dicom-file and dicom-data and do a cleanup. I think there are a few things there I'd like to change a little.
• [ ] I think it'd be a good idea to make a very quick prototype Python binding using cffi. It shouldn't be much work, and it would reveal any "duh" moments in the API. Fixing stuff like that after we hit 1.0 is much harder.
• [x] #19
• [x] Perhaps make a tiny website for the project in gh-pages? If we have API docs in markdown, it's only an hour or so of work.
• [ ] Include a demonstration of useful performance improvements over existing dicom readers to motivate interest.
• [ ] Add a DICOM reader to libvips based on libdicom?
• [ ] vipsdisp would then get a DICOM loader too, also a potentially useful tool.
• [ ] Launch 1.0, announce on twitter, image.sc, etc.

Please edit and add / remove any of these suggestions, of course.

[hackermd]

Perhaps make a tiny website for the project in gh-pages? If we have API docs in markdown, it's only an hour or so of work

The website would be straight forward to add, since we already have online documentation build via Sphinx: https://github.com/hackermd/libdicom/tree/dev/doc/source

However, GitHub pages is not available for private repositories under the free plan..

[hackermd]

Documentation is now available online at Read the Docs: ttps://libdicom.readthedocs.io

[jcupitt]

A quick update: I've got Leica DICOMs working in my fork. I'll make a PR on openslide in a week or two after I polish it a bit.

Here's the standard Leica DICOM being viewed:

It's a bit slow (I'll try to improve that).

It looks very washed out due to no colour management. Here's the same slide with and without a profile:

[jcupitt]

There's a proposed 1.0 here: https://github.com/jcupitt/libdicom currently awaiting merge to this repo.

It implements all these ideas. I'll close this issue.