Add dearpygui integration

[eulertour]

Changelog / Overview

Motivation

Offers a way to get realtime feedback on variable parameters.

Explanation for Changes

Enables GUI interaction

Documentation Reference

Testing Status

Ran example GUI scene locally (Linux)

Further Comments

The API used for interacting with the GUI is subject to change, as right now it doesn't allow some things (like multiple windows)

Checklist

• I have read the Contributing Guidelines
• I have written a descriptive PR title (see top of PR template for examples)
• I have written a changelog entry for the PR or deem it unnecessary
• My new functions/classes either have a docstring or are private
• My new functions/classes have tests added and (optional) examples in the docs
• My new documentation builds, looks correctly formatted, and adds no additional build warnings

Reviewer Checklist

• The PR title is descriptive enough
• The PR is labeled correctly
• The changelog entry is completed if necessary
• Newly added functions/classes either have a docstring or are private
• Newly added functions/classes have tests added and (optional) examples in the docs
• Newly added documentation builds, looks correctly formatted, and adds no additional build warnings

[hydrobeam]

Some things that I've noticed:

• The gui initially starts at the bottom of the window and resets to this position everytime the scene is changed. It needs to be dragged up to actually be usable. It'd be nice if it started out in the center of the window and didn't need to be readjusted. Occurs in both windows and WSL.
  • 

[hydrobeam]

• Calling the gui test without specifying the scene from the command line: manim -p --renderer=opengl example_scenes/opengl.py causes the GUI interface not to appear. (the scene still plays)
  • Side note: it also asks for the scene twice (not caused by this PR)

[hydrobeam]

• Playing a GUI scene without the preview flag causes the GUI to appear and raises an error. Then after any input in the terminal, the program enters into a brutal never ending loop that forces me to kill my terminal. For the sake of avoiding this, the p flag should probably be automatically included when using the GUI.
  • input: manim --renderer=opengl example_scenes/opengl.py GuiTest
  • output: repeats indefinitely.

    Unhandled exception in event loop:
     File "C:\Users\laith\AppData\Local\pypoetry\Cache\virtualenvs\manim-zPbAr8g6-py3.9\lib\site-packages\prompt_toolkit\application\application.py", line 913, in inm    await _do_wait_for_enter("Press ENTER to continue...")
     File "C:\Users\laith\AppData\Local\pypoetry\Cache\virtualenvs\manim-zPbAr8g6-py3.9\lib\site-packages\prompt_toolkit\application\application.py", line 1282, in _r    await session.app.run_async()
     File "C:\Users\laith\AppData\Local\pypoetry\Cache\virtualenvs\manim-zPbAr8g6-py3.9\lib\site-packages\prompt_toolkit\application\application.py", line 816, in ruc    return await _run_async2()
     File "C:\Users\laith\AppData\Local\pypoetry\Cache\virtualenvs\manim-zPbAr8g6-py3.9\lib\site-packages\prompt_toolkit\application\application.py", line 792, in _r2    result = await _run_async()
     File "C:\Users\laith\AppData\Local\pypoetry\Cache\virtualenvs\manim-zPbAr8g6-py3.9\lib\site-packages\prompt_toolkit\application\application.py", line 721, in _rc    with self.input.raw_mode(), self.input.attach(
     File "C:\Users\laith\AppData\Local\Programs\Python\Python39\lib\contextlib.py", line 117, in __enter__
       return next(self.gen)
     File "C:\Users\laith\AppData\Local\pypoetry\Cache\virtualenvs\manim-zPbAr8g6-py3.9\lib\site-packages\prompt_toolkit\input\win32.py", line 594, in attach_win32_it    win32_handles.add_win32_handle(handle, callback)
     File "C:\Users\laith\AppData\Local\pypoetry\Cache\virtualenvs\manim-zPbAr8g6-py3.9\lib\site-packages\prompt_toolkit\input\win32.py", line 554, in add_win32_hande    run_in_executor_with_context(wait, loop=loop)
     File "C:\Users\laith\AppData\Local\pypoetry\Cache\virtualenvs\manim-zPbAr8g6-py3.9\lib\site-packages\prompt_toolkit\eventloop\utils.py", line 33, in run_in_exect    return loop.run_in_executor(None, ctx.run, func, *args)
     File "C:\Users\laith\AppData\Local\Programs\Python\Python39\lib\asyncio\base_events.py", line 814, in run_in_executor
       executor.submit(func, *args), loop=self)
     File "C:\Users\laith\AppData\Local\Programs\Python\Python39\lib\concurrent\futures\thread.py", line 161, in submit
       raise RuntimeError('cannot schedule new futures after shutdown')
    

[hydrobeam]

Kind of botched the review feature but:

• It'd be nice if the scene rendered in a fixed window at a certain position on the screen (like in manimgl). Right now, rendering a scene at full quality causes it to be off the side and difficult to manage.
  • Something like this would be ideal:
  • The GUI can be placed just below the preview window, or next to it.
• This is how it currently looks:
  • 
    • Note: I also had alt-tab to view these windows since they did not appear on top of the editor at first.

[hydrobeam]

Some comments about the formatting of the GUI.

[Darylgolden]

LGTM, given that this is experimental I think we can merge this now. This also fixes Intel rendering slowness despite @eulertour having no intention to fix it, and I would like to work on top of these changes to attempt to debug the Intel strokes problem.

[Darylgolden]

Actually, why didn't the CI run for this PR?

Addressed in later commit

Addressed in later commit