A gui code runner built to test out slope's gui features
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
sloum 0fd6e3caa5 Removes dead file, changes screenshot name, updates drslope to better error handle recursive runs 4 weeks ago
README.md Removes dead file, changes screenshot name, updates drslope to better error handle recursive runs 4 weeks ago
drslope.slo Removes dead file, changes screenshot name, updates drslope to better error handle recursive runs 4 weeks ago
screenshot-drslope.png Removes dead file, changes screenshot name, updates drslope to better error handle recursive runs 4 weeks ago

README.md

DR. Slope

Dr. Slope a play on Dr. Racket. To be very clear: this was made on a lark and is nowhere near the same league as Dr. Racket. It actually took less than an hour to hack together thanks to slope being easy to develop gui software with thanks to the fyne toolkit!.

Current capabilities:

  • Can run any valid slope code that does not require terminal input
    • It actually works great for developing gui based applications with slope
    • It can run the drslope file itself to create a recursively run gui
  • Captures stdout and stderr to separate windows
  • Can open files
  • Can save work
  • Can clear the workspace
  • Can open a file when run from your terminal: slope drslope.slo drslope.slo (will open itself if you are in the drslope repo root)
    • Will display an error, but still run, if the given file could not be opened/read
  • Variables are available at the top of the file to easily edit the default size of the application

Issues:

  • Cannot take input from stdin
  • Buffers output and then flushes after the given program exits, making it unsuitable for a number of interactive use cases
  • Cannot render terminal escape sequences to any effect

Dr. Slope Screenshot

Running

Should run on any version of slope with gui compiled in >= 0.5.3