You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Javadoc discovery via therapi is great for dependency-free op registration, but still requires modification to "source" code. Ultimately for adoption we need a mechanism for registering ops without any changes to source or documentation.
It seems sensible to support a configuration file syntax, e.g. in yml.
This would likely be the mechanism for including libraries in other languages.
If a library has a mechanism for introspecting its available algorithms, we could (on a per-library basis) create an automated mechanism that generates a companion ops configuration yml, and it would also provide a path for manual configuration when introspection is not possible.
Activity
gselzer commentedon Nov 3, 2022
Sure. What items are needed? Shall we prototype something like this?
I would think that the goal should be to create something that gives us all of the needed info for matching without loading in the code until needed
Merge pull request #97 from scijava/scijava/scijava-ops-engine/cautio…