Summer travel choices:

• Hint as a base for Nawak.
• Nawak (editor / vm / platform).
• Conductor 2.
• Portnawak (quick game to learn kotlin).

Another idea to explore:

• Read a SCARM file and generate 3D track data for blender.
• Layout software for Android / mobile. Scrap existing library data to get started.

Maybe that’s what Portnawak could be: a potpourri of random mobile apps “1 day” experiments, with multiple absolutely unrelated activities in the same app.

Decided on the following plan for this summer:

• A 1-week addition to Portnawak as a simple “falling dot” game. Goal is to not focus too much on the engine part and develop some real kotlin code.
• A very very short throw-away track layout experiment. How would interaction work? Consider having only 2 pieces of tracks (1 straight + 1 curve) with auto-snapping. The goal here is to put that code in a generic library + UI that is android specific.
• After these 2, consider if I want to keep using kotlin or go back to Java.
• Then move on to the simulator for Conductor 2 (java app). Structure it at all in a library except UI in a java project (swing) or web rendering.