Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(v2) feat: ferocious renderer #1200

Merged
merged 36 commits into from
Nov 12, 2024
Merged

(v2) feat: ferocious renderer #1200

merged 36 commits into from
Nov 12, 2024

Conversation

aymanbagabas
Copy link
Member

@aymanbagabas aymanbagabas commented Oct 23, 2024

This implements a cell-based renderer instead of the existing line-based one. The cell-based renderer will be used when TEA_EXPERIMENTAL=cellbuf is exported. The cell-based renderer, now called The Ferocious Renderer, is enabled by default. To disable it set TEA_EXPERIMENTAL=unferocious.

To trace the output of the program, you can export TEA_TRACE=<filename> and TEA_TRACE_OUTPUT=1 and/or TEA_TRACE_INPUT=1 to see the I/O of the program.

Supersedes: #1132

Right now, we only have one experimental feature to use the new cell buffer as a default renderer.
Use `TEA_EXPERIMENTAL=cellbuf` environment variable to enable the use of the cell buffer as the default renderer.
…hanges

This implements the meat of the cell renderer. It performs rendering changes
using a cell-based tracking. Changed cells are marked as dirty and only the
changed cells are rendered to the terminal. This is more efficient than
line rendering.
@aymanbagabas aymanbagabas marked this pull request as ready for review November 5, 2024 15:40
@meowgorithm meowgorithm changed the title (v2) feat: cell based renderer (v2) feat: ferocious renderer Nov 6, 2024
@aymanbagabas aymanbagabas merged commit 1ebb164 into v2-exp Nov 12, 2024
44 checks passed
@aymanbagabas aymanbagabas deleted the v2-renderer branch November 12, 2024 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants