-
Notifications
You must be signed in to change notification settings - Fork 2
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
General Editor Module #1
Comments
I like this idea, this way we can separate all the editors from all the runners. I'm thinking I'll make this module into purely a code editor and separate code-running into a separate one. |
Hi, yesterday I added one 🙈 ... https://github.com/Cross-Lab-Project/edrys_module-editor It should already appear in your module-overview ... probably this could also be extended to something more project-based, which allows to define projects with different files in different tabs... I think, something like this could be configured like: {
"project": {
"main.cpp": "some code",
"class.h": "header code",
"class.cpp": "some class code"
}
} ... Just thinking aloud ... |
That is a great start, I think we can keep this one as-is (someone might find a all-in-one module useful) and continue developing the other one as well. Perhaps we can allow creating "files" in the editor and switching between them, similar to VS Code. |
Hi, I think it would be great to have something like a general Editor module, without any additional functionality at all.
The idea is, that the editor module can be configured to publish on different topics, when the "run-button" is hit. Another module can be configured also, to listen this topic in promiscuity-mode, which then releases some kind of action.
I did this, within the following module, which will execute the code, that is published from other modules:
https://github.com/Cross-Lab-Project/pyxtermjs
This way one editor module could be used for different purposes, even within the same classroom.
The text was updated successfully, but these errors were encountered: