Library separation

[9il]

A user may want to use this library only for CV algorithms. Library should not force a user to install any C libraries.
Looks like DCV may be splitt to

• algorithms / image manipulations (DCV)
• decoding / codecs
• visualization

Current library looks like it is oriented for the end user. Comparing with Python, it is better practice for D to have an API, which can be used to build extended functionality, e.g. to be used in other libraries and cross-platform products.

[ljubobratovicrelja]

I agree. I was already planning on separating visualization. So if we're gonna separate I/O also, I suppose dcv.io, and dcv.plot would be optional, included only if special version is defined? That way no C libraries would be required (except blas/lapack, but that'll be fixed with #26).

[9il]

So if we're gonna separate I/O also, I suppose dcv.io, and dcv.plot would be optional, included only if special version is defined?

Special configuration. Another option is move them to separate package.

[9il]

Also dub has sub-packages, but i don't know how good they work

[ljubobratovicrelja]

OK, I'll investigate that. I cannot tell from this point of view what would be a best option. I'd like to work on this and #26 after we resolve #20.

[9il]

imageformats does not depend on any other D or libraries, so it may be preserved, thought

[9il]

Also this will allow to exclude ggplotd from dependency list. ggplotd is not available for windows users :-(. This is significant constraint for newcommers