Casino
Introduction
Casino aims to migrate semi-automatically the front-end of applications regardless of its implementing language. The front-end corresponds to the widgets and their behaviors.
Migration Strategy
Here is a diagram showing the migration steps implemented by Casino.

GUI Meta-model
Full Widgets meta-model
Current results
GWT application migration to Angular
| Source Application (GWT) | Target Application (Angular) |
|---|---|
![]() | ![]() |
![]() | ![]() |
![]() | ![]() |
![]() | ![]() |
![]() | ![]() |
![]() | ![]() |
GWT to Seaside
Here are some other examples of the results obtained for GWT application migration to Seaside (Traccar):
| Source Application (GXT) | Target Application (Seaside) |
|---|---|
![]() | ![]() |
![]() | ![]() |
![]() | ![]() |
Spec to Spec2
| Source Application (Spec) | Target Application (Spec2) |
|---|---|
![]() | ![]() |
Links
The core of the project (with the importer GWT and the exporter Angular) is available on GitHub. There are also:
| Importer | Exporter |
|---|---|
| Swing | Spec |
| Spec | Spec2 |
| HTML | Seaside |
| GWT/GXT | Aurelia |
| Silverlight |
Some importers or exporters are still in beta version. However, you can help us! 😄
To use Casino, we must use a Moose 8 image.



















