eventcontrol | EventControl , jQuery timeline control | Plugin library

I understand that you want to display all the choices in a single JOptionPane.
If I understand correctly, then try the following code (which uses the stream API)

None of the operations are generated automatically. If you followed the documentation about extending the admin, you probably only have implemented the cgetAction() method, right? Therefore only the app.get_events route has been registered. As soon as you implement e.g. a postAction(), a app.post_event route will be registered for you. But you always have to implement the crud functionality for your custom entity by yourself, Sulu can't do that for you, because it's completely up to you, how your custom entity is stored (could be also stored as a file in your filesystem or as a document in elasticsearch)

Normally it's quite helpful to have a look at Sulu's internal bundles (the SuluTagBundle is quite an easy one) or other resources on github (e.g. Sulu Workshop and Sulu Demo) to see how such things are working.

You did not specified the action for your form. Use th:action="@{/your Url}" in the form tag.

No, you cannot avoid reconsuming ids for two reasons:

1. You have defined your controller as a singleton, so you could imagine that you'd have some race conditions with concurrency if the field member "Long id" was changed for simultaneous requests. Theoretically, you could define the Controller with scope prototype, but I'm not recommending that.
2. The PathVariable annotation is defined with @Target(value=PARAMETER). This means you cannot apply it to fields like you have here.

In order to receive events (such as the mouse moving), you need to call pollEvents on the window.

In your commented code, you were doing this through your Window::EventControl() method. Your new GameManager class isn't calling this, however, so you aren't receiving any events.

you can use route name
add a name to your route:

You can do something like this, where you check the content-type header and decide what to try to parse from the XML string. You would need to use your XML parser to implement the parseMessage function, and a similar parseEvent function.

I would suggest that you implement this in Laravel's way. In your api.php, change your route so that it accepts a parameter like below.

Notice that {account_id} is then replaced with the actual ID number when a program hits this API route.

The Controllers you are referencing in your routes are being prefixed with a namespace of App\Http\Controllers. Since your Controller is in a subnamespace of this (also a subfolder of the mapped directory for this namespace) you will need to tell the Router about the rest of the namespace to this Controller: