-
Notifications
You must be signed in to change notification settings - Fork 0
Description
In the Agentic AI meeting last wednesday the constraints of the AnyLogic IDE were surfaced more forcefully than before.
I think the top friction we have for migrating off AnyLogic is that implementing the GUI will be harder.
It seems to me the most significant friction is that our front-end is preferably webbased but our simulation should be able to run on a powerful server. In the current paradigm of web development you would create an extensive schema in order to let the front-end fetch simulation data from the back-end.
AnyLogic gets around this problem by not shipping the data but instead shipping commands from the server to browser GUI components (and events the other way). Unfortunately with a limited set of components.
I would like to try out a variant of this approach.
Options:
- Vaadin
- Remote Compose
- Implement a custom renderer for Compose
- ...
Resources:
- https://proandroiddev.com/layoutnode-what-actually-happens-when-you-write-composable-05c0275875fa
- https://github.com/JetBrains/compose-multiplatform
- https://issuetracker.google.com/issues/482343980?pli=1
Concerns:
- can it handle intensive graphics like 3d?
Tasks:
- Research similar thin client architectures and solutions
- Create a proof-of-concept