-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change input format to YAML #84
Comments
My long term plan is to switch input format to YAML format. I have a related project where we want to develop the next generation input parser and replace libgetkw. All suggestions welcome for features you would like to have implemented there. |
And I think input and scripts is a too wide topic. I think scrips and input format are two different topics. |
Why YAML? I found this page: http://yaml.org/ Does not look tempting to me. Changed the discussion topic for not being too wide. I think this is related to input format plans. |
That page is scary but YAML is the de-factor standard input format. Easy to parse for machines, easy to write for machines, easy to write for humans, readable for humans. You can have nested sections. My favorite format. But don't worry, before going there I would create a proper proposal demonstrating how the new input would look compared to now. What I can already promise is that it will look a lot cleaner and easier to read. |
Most importantly: it is a standard format. Creating own formats is not a good idea. |
Example - instead of:
With YAML:
|
I see your point. However, I am happy that this is not on the desk right now. ;) |
I will work on the input parser independently of GIMIC. Later GIMIC can decide whether it likes it or not. |
Ok - the example you showed is less scary that the web page. I suggest to take this up into an issue/meeting discussion. Would that be ok? |
That's fine. There is no rush with this. |
There is always a rush. I just put in on the agenda for our next project meeting. |
So we go for YAML. Replace getkw python. |
I got some user feedback regarding the input of gimic and would like to open an issue to discuss on how things should be restructured or not.
The text was updated successfully, but these errors were encountered: