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

Custom Renderer #19

Open
FlatMapIO opened this issue Nov 12, 2022 · 7 comments
Open

Custom Renderer #19

FlatMapIO opened this issue Nov 12, 2022 · 7 comments
Labels
enhancement New feature or request

Comments

@FlatMapIO
Copy link

Is it possible to implement the createRenderer API in solid in voby? This allows voby to be used in a wider range of scenarios.

@fabiospampinato
Copy link
Member

fabiospampinato commented Nov 12, 2022

Potentially possible, if one doesn't need to render to multiple targets at the same time it should be relatively easy.

Let's see how much demand there is first, from what I've seen this is a fairly niche feature that almost nobody uses in practice.

@fabiospampinato fabiospampinato added the enhancement New feature or request label Nov 12, 2022
@fabiospampinato
Copy link
Member

fabiospampinato commented Feb 27, 2023

@FlatMapIO do you need multiple custom targets at the same time? And which target(s) are you most interested in?

@fabiospampinato
Copy link
Member

By the way do you know where this is documented in Solid? I can't find any docs on this createRenderer function.

@FlatMapIO
Copy link
Author

Less documentation:

Some usage examples may be helpful:

@FlatMapIO
Copy link
Author

@FlatMapIO do you need multiple custom targets at the same time? And which target(s) are you most interested in?

My work involves a lot of data analysis and visualization, so it would be great if canvas targets were supported.
Also, I would like to use jsx as a DSL for building SQL, which would avoid the ugly Jinja & macro that users use with dbt.

@theSherwood
Copy link

I too would be interested in custom renderer support for rendering into the terminal.

@fabiospampinato
Copy link
Member

For the terminal imo an approach like this is way way simpler. Like you really want components if you need to change how children are rendered, like by centering them or something. If you don't need that kind of capability then you really don't want to use a UI framework to render that, like it can take a few KBs to make a good looking terminal app, but if you are throwing a UI framework at the problem now the terminal app will necessarily start up slower, which goes in conflict with making a good terminal app. Like if there are requirements for features that are simpler to implement with a custom renderer for a UI framework those requirements should be questioned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

3 participants