micromouseonline / micromouse_maze_tool Goto Github PK

As you have seen, I have just tried to contribute my first maze to this repository. In order to do so I needed to install a C++ compiler, compile the project and generate the 3 different formats required.

I also thought about cleaning up some maze file names (i.e.: make some file names more consistent), but then realized I had to do so for the 3 formats and lost interest... 😂

Maybe this could be approached in a different way: have a separate repository just for maze files. In my opinion this repository should:

• Contain only maze files, no scripts, no source code.
• Maze files could be stored in folders by maze dimension. For now there would only be 16x16 mazes, so just one folder.
• Contain a single file for each maze (i.e.: avoid duplication). I think this would be the most important part, actually.
• The file format should be text because:
  • It is self-explanatory (i.e.: no need to explain how information is stored in bytes).
  • It is language-agnostic.
  • It gets along with version control systems (Git).
  • It is easy to visualize right from the browser or locally with any text editor.
  • It is also easy to edit (in case someone wants to contribute new mazes or fix existing ones, they only need a text editor if they do not have better/automated tools).
  • It is not hard to parse nor to generate in any programming language.

Then you could use that repository as a Git sub-module in this maze tool or anywhere else you use maze files. I would do the same of course if that repository existed. 😊

Do you think it could be a good idea?

There seems to be a text file infiltrated in the binary folder:

mazefiles/binary/Taiwan2017.txt

😂