it is creating one or multiple Source< ? >s for a given input
it is creating a Converter< ? , ARGBType >
it is showing the (newly created) SourceAndConverter in bdv.
This is very convenient, but I was wondering whether it could be possible to separate this a bit.
For example,
having a SourceCreator( ... ) with several constructors
something like a DefaultConverterCreator( source )
and then have a method that shows a SourceAndConverter in bdv.
Right now, one can kind of do the same using SourceAndConverter sac = BdvFunctions.show( ... ).getSources().get( ... ) but one needs to show the object in order to convert it to a SourceAndConverter. In my experience, if dealing with many SourceAndConverters it can help to have a list of all of them already before showing them in bdv.
Also separating above functionalities into separate classes might simply structure the current code a bit more.
Currently
BdvFunction.showis doing three things:Source< ? >s for a given inputConverter< ? , ARGBType >SourceAndConverterin bdv.This is very convenient, but I was wondering whether it could be possible to separate this a bit.
For example,
SourceCreator( ... )with several constructorsDefaultConverterCreator( source )SourceAndConverterin bdv.Right now, one can kind of do the same using
SourceAndConverter sac = BdvFunctions.show( ... ).getSources().get( ... )but one needs to show the object in order to convert it to aSourceAndConverter. In my experience, if dealing with manySourceAndConverters it can help to have a list of all of them already before showing them in bdv.Also separating above functionalities into separate classes might simply structure the current code a bit more.