The IDE will hang if told to "skip to end" with a non-halting program.

Example program:

+[>+]

Actions taken: Program input, run. IDE told to "skip to end."

Expected result: IDE stops after program runs too long or otherwise indicates that it cannot be "skipped to end."

Actual result: IDE runs program at high speed, using an entire CPU core. If user attempts to stop program using the "reset everything" button, IDE hangs.

Godot 3 is not backwards compatible with Godot 2 projects. We need to port to be able to use the new editor.

I already digged through the source, but I couldn't really find where the datamanager.AddVal(-1) is implemented.. it should be pretty easy to just check if the cell value is < 0 and add 256 in that case.

The current implementation of brainfuck is extremely slow. This is mostly due to it not being optimized (Its also implemented in a slow scripting language, but compared to the potential speedup of simple optimizations, this is negligible). Complex programs should run efficiently if desired, but optimizations must remain optional, as the user will often want to see their unoptimized brainfuck run one command at a time.

We need the ability to load and save brainfuck source files. It would also be nice to keep settings and/or open file persistent across closing and reopening the IDE. I've no idea how to do this, but Godot probably makes it somewhat painless. It may or may not be a good idea to wait on #4 (Port to Godot 3) for this.

It would be nice if you could scroll horizontally along the data tape

Most of this project was written over a couple of days for a single lightning talk. As you might imagine, the code isn't the best. Here are some low hanging fruit:

• Many names are in CamelCase, but some are in snake_case. All should be in snake_case (except maybe types?) as that's Godot standard.
• Node paths are hard coded all over the place, instead of exported to the editor

How can I run this engine? I can't launch the engine.cfg file.

data_display.gd currently manages both the internal representation of the data tape, and the visual display representation. Other bits of the brainfuck runtime (parsing and interpreting) are scattered throughout the code base. Purposed solution:

1. design a clean interface between the runtime and the rest of the code, this should support:
   • Adding instructions to the queue
   • Dequeueing and running one instruction at a time
   • Running many instructions as fast as possible
   • Fetching a portion of the data tape for display
   • Endless loop handling
   • more?
2. Implement this in GDScript
3. Port the visual frontend to use it

Advantages:

• Cleaner code
• Easier to add optimizations (see #5)
• Frontend can be designed such that it does not create nodes for every data cell in use (this allows for brainfuck programs with much larger memory requirements to run)
• brainfuck implementations can be interchangeable (even 3rd party ones could be added)

Can you go into godot and change the scaling type to stretch?