Skip to content
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

.aeon format rework #4

Open
daemontus opened this issue Feb 18, 2020 · 0 comments
Open

.aeon format rework #4

daemontus opened this issue Feb 18, 2020 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@daemontus
Copy link
Member

There are several problems with .aeon format right now:

  • There is no way to output variables without regulations (you can make a fake "self" regulation that does not change anything, but this is very wrong).
  • Parameters are implicitly declared based on update functions - this is error prone.
  • There is no support for multiline or composite expressions (or more complex things like switches).
  • The support for metadata is very lax and parsing them is very restricted.
  • No rich-text editor for aeon format.

Currently, there is some work in model-toolkit which might be a better starting point for a format like this, but everything there is mostly aimed at continuous/hybrid systems and written in Kotlin. However, it might actually be good to make a hybrid format for everything because we need to handle hybrid systems as well. However, there should be some kind of built-in validation for things like that (i.e. I can declare a certain file to be a boolean network and that means extra validation rules).

@daemontus daemontus added bug Something isn't working enhancement New feature or request labels Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant