gselzer on sharpen-smooth
Add DefaultSmooth and DefaultSh… Preserve differentiation in sum… Rely on helper Ops to decrease … and 1 more (compare)
scijava/scijava, although I favor the latter at the moment.
Otherwise, as soon as we want to iterate on the core scijava platform again (ha ha, hopefully never, but you know... might need to break some API later)... we go from
org.scijava.ops.v2, which is weird... I'd rather go from
v2, or even
Does this scheme allow us to iterate on a particular component? Do you see us ever wanting to?
org.scijava.parseis taken, we have to call it
org.scijava.parse2, with artifactId
OpEnvironmentwill do no discovery...
BaseOpEnvironment, and then the fancy one should extend it? But it depends what functionality each one brings to the table.
OpEnvironmentFactoryobjects you want to use, and that is pretty hard to do if you are getting them through
Initializable? I think the reason is that there are two
Initializableinterfaces: one in scijava-common and one in imagej-ops. See imagej/imagej-ops#455