-
Notifications
You must be signed in to change notification settings - Fork 45
Enhancement: Create a tool for the creation of OpMon #95
Comments
There is a complete guide about creating OpMons here in the wiki: https://github.com/OpMonTeam/OpMon/wiki/How-to-create-an-OpMon |
I started to build the tool here: |
Oh, thank you! Meanwhile, I've done a little guide about the OpMon JSON format. I will add other formats guides, but for now, this is enough I think : https://github.com/OpMonTeam/OpMon/wiki/JSON-guide |
This tool probably should be a new repository of the OpMonTeam account, don't you think ? A fork would be enough ^^ |
Btw, I think it would be advised to do the user interface in Qt, as it will be more native for end-users and considerably speed up the coding process as well |
I agree about Qt, I've already used it in the past for personal projects. However, I don't know anything about the Qt license, and if it's compatible with the GPL 3.0. And I've forked the repository, but I won't have to time to personally contribute to it. |
Qt has two licences : a proprietary one and a (L)GPL v3. So it is possible to do open-source projects based on Qt. As for @PyroFlareX , maybe put him administrator of the fork, so he can manage it from the OpMon Team's group directly ? |
That's what I've done, I invited him to the @OpMonTeam/opmon-creation-tool team, so he can have admin permissions on the fork. And ok for Qt! |
Done |
I was looking through the project, and there weren't any resources for existing OpMon besides a JSON that didn't really have the names. Are there any current resources or example sheets for the creation of OpMon? If not, a simple (even a commandline) tool that exports an OpMon JSON based on given info. I'd make one, but can't seem to find any info on what the format is.
If it hasn't been done already, having a JSON or a custom file format extension PER OpMon would make creation simpler as well.
EG: OpMon/Data/OpMon/*.json (or *.opmn) with a file for each OpMon.
The text was updated successfully, but these errors were encountered: