You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just tossing the idea here for future reference, in case anyone finds the ressource to tackle it.
The Eidos "input commands" subwindow of the SLiMGui offers sophisticated code-edition-related features like:
syntax highlighting
autoformatting
autocompletion
errors linting
code navigation
..
These must be the result of a huge work, and they make the Eidos coding experience rather nice. Unfortunately, they are restricted to this very particular sub-window of this very particular SLiMGui application. As a consequence, while writing Eidos code, we cannot benefit from any other standard modern IDE features like shortcuts customization, macros recording, automation, multiple window management, split views, theming, etc. unless we use an external editor instead of the SLiMGui editor. But then we loose the above features.
If the above features were extracted into a proper eidos-language-server, then we could have our cake and eat it too. We could edit Eidos script files using either SLiMGui/vim/vscode/intellij/emacs/atom/notepad++/<whatever>.. and still always benefit from the above features.
(Note: all population-genetics-simulation-related features (visualisation, genome browsing, reports, plots..) are not strictly related to code edition and cannot be forwarded to code editors via the language server protocol. Of course, SLiMGui remains the best application to run/visualize the models ;)
The text was updated successfully, but these errors were encountered:
As discussed over email with Iago, I've marked this "help wanted"; it might be a fun side project for somebody, but will be complex, and I'm unlikely to have time for it for, well, maybe ever. But it's a nice idea.
Just tossing the idea here for future reference, in case anyone finds the ressource to tackle it.
The Eidos "input commands" subwindow of the SLiMGui offers sophisticated code-edition-related features like:
These must be the result of a huge work, and they make the Eidos coding experience rather nice. Unfortunately, they are restricted to this very particular sub-window of this very particular SLiMGui application. As a consequence, while writing Eidos code, we cannot benefit from any other standard modern IDE features like shortcuts customization, macros recording, automation, multiple window management, split views, theming, etc. unless we use an external editor instead of the SLiMGui editor. But then we loose the above features.
If the above features were extracted into a proper
eidos-
language-server
, then we could have our cake and eat it too. We could edit Eidos script files using either SLiMGui/vim/vscode/intellij/emacs/atom/notepad++/<whatever>.. and still always benefit from the above features.(Note: all population-genetics-simulation-related features (visualisation, genome browsing, reports, plots..) are not strictly related to code edition and cannot be forwarded to code editors via the language server protocol. Of course, SLiMGui remains the best application to run/visualize the models ;)
The text was updated successfully, but these errors were encountered: