even MORE readable format #23

Open
opened 2026-08-04 23:31:15 +00:00 by Roboticy3 · 0 comments
Roboticy3 commented 2026-08-04 23:31:15 +00:00 (Migrated from github.com)

I want support for a plain text format where objects are separated by double newlines and components are separated by single newlines, and connections are denoted next to choice text instead of as separate objects. This is necessarily less powerful than the main json format since connections wont be first class objects, but it should be much easier to write and easier to convert to and from.

The only big technical implication is that object ids would work more cleanly as strings than as integers, which is what they are now. Maybe when reading a string id we could take the same approach as minecraft seeds where it first tries to convert it to an integer, then tries a hashing approach.

I want support for a plain text format where objects are separated by double newlines and components are separated by single newlines, and connections are denoted next to choice text instead of as separate objects. This is necessarily less powerful than the main json format since connections wont be first class objects, but it should be much easier to write and easier to convert to and from. The only big technical implication is that object ids would work more cleanly as strings than as integers, which is what they are now. Maybe when reading a string id we could take the same approach as minecraft seeds where it first tries to convert it to an integer, then tries a hashing approach.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Roboticy3/Louder#23
No description provided.