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

Components too coupled to terminals #94

Open
davesmith00000 opened this issue May 26, 2024 · 0 comments
Open

Components too coupled to terminals #94

davesmith00000 opened this issue May 26, 2024 · 0 comments

Comments

@davesmith00000
Copy link
Member

davesmith00000 commented May 26, 2024

In order to use a Text instance, for example, you need a boundaryLocator to find the bounds. But there's no nice way to hook that in and keep the lower level components stateless.

Also the Theme instances clearly expect a terminal, they don't relate to anything else.

The alternative is to double down on terminals, at least for the component system/built in components?

@davesmith00000 davesmith00000 changed the title Components too couple to terminals Components too coupled to terminals May 26, 2024
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

No branches or pull requests

1 participant