These are chat archives for bigdataviewer/bigdataviewer-core
sc.fiji, although we should consider changing that.
transfer to bigdataviewer repository
You mean move the
bdv-panel repository to the
bigdataviewer organization? Or would you integrated it into another repository there?
doubleprecision, and transfer functions in general... how much the BDV should know or care about all that, versus assuming the input data conforms to certain assumptions, which the caller must take care to meet. But to address your question about whether to break the API: could you introduce a change like the one you made, but with a new constructor signature, and keep the old one deprecated? That way it won't break API, but still gains the benefits of the new idea... you could avoid the "ctor overload hell" by introducing static factory methods a la