I'm starting to think that I may eventually do a major refactoring wherein Enola's "Things Core" would be more completely separated from Proto & RDF (et al.), which would become "plugins". It might one day look something like the following, which is a fairly different package structure from how things look like as I'm initially writing this:
dev.enola.common.io
dev.enola.core.datatype
dev.enola.core.thing
dev.enola.format.rdf
dev.enola.format.proto
dev.enola.model.markdown
dev.enola.model.java
dev.enola.shell.repl
dev.enola.cli
dev.enola.web
dev.enola.ai
It's a bit premature for this as-is today, as more will need to be untangled in the code, but creating this issue to track possible future related work.
I'm starting to think that I may eventually do a major refactoring wherein Enola's "Things Core" would be more completely separated from Proto & RDF (et al.), which would become "plugins". It might one day look something like the following, which is a fairly different package structure from how things look like as I'm initially writing this:
dev.enola.common.iodev.enola.core.datatypedev.enola.core.thingdev.enola.format.rdfdev.enola.format.protodev.enola.model.markdowndev.enola.model.javadev.enola.shell.repldev.enola.clidev.enola.webdev.enola.aiIt's a bit premature for this as-is today, as more will need to be untangled in the code, but creating this issue to track possible future related work.
What a "plugin" approach means for the CLI & distro is TBD. (💀 OSGi! 🤣 https://github.com/vorburger/HoTea?)