Loading Profile...
YAML based plugins (service descriptions)
How about generalizing and abstracting the plugging in of different services to be able to activate new services by YAML (or XML or whatever) files, so that people could easily write their own "plugins", add them to a repository, and perhaps easily download the descriptive files from within Eventbox ?
I’m excited
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?EventBox is plugin based and if you've looked into the app bundle, you will see that each service is a separate binary. But it's impossible to write plugins just using YAML or XML, it's much more complicated than that. We have long term plans to open our API to 3rd parties.
The company thinks
this is one of the best points
-
Inappropriate?I saw the plugin folder in the app, that ́s why I thought of this. And I see that it ́s impossible in the current Eventbox, but I still think, if you wanted to, you could generalize plugins into sets of rules in the main app which could be activated through descriptive files including adresses to the service ́s endpoints (CRUD,favicon,etc.)
-
Inappropriate?I see your point. There is definitely a lot of potential in doing it this way but currently we just don't have the time to spend re-factoring EventBox. We would rather spend it implementing much needed user-end features although as I said, we will open things up eventually in some form or other.
