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

make the backend choice more clear #4040

Merged
merged 5 commits into from
Jul 24, 2024

Conversation

SimonDanisch
Copy link
Member

No description provided.

docs/src/index.md Outdated Show resolved Hide resolved
@asinghvi17
Copy link
Member

Looks good to me, aside from the typo :D

Co-authored-by: Anshul Singhvi <asinghvi17@simons-rock.edu>
@asinghvi17 asinghvi17 added the skip-changelog Skips changelog enforcer label Jul 17, 2024
@jkrumbiegel
Copy link
Member

I don't know, maybe it's pedantic but "most feature complete" doesn't make sense to me. Especially because it's totally unclear what "complete" means. And I'm also not sure if I would call GLMakie "preferred", so many people use cairomakie because they have no strong need for interactivity or 3D. Maybe it could be the "suggested" backend for people who want interactivity, and CairoMakie for those who want vector graphics.

@asinghvi17
Copy link
Member

I agree with your point, that being said the distinction between "good at interactivity" and "good at vector graphics" may not be totally clear to a newcomer.

Maybe we could instead recommend GLMakie for True 3D graphics and interactivity and CairoMakie for 2D static plots with vector graphics? Something like that might help people understand when to and when not to use the backends more immediately.

@ffreyer
Copy link
Collaborator

ffreyer commented Jul 17, 2024

Plots.jl has a overview table and some short Pros & Cons lists to explain this kind of stuff:
https://docs.juliaplots.org/stable/backends/#At-a-glance

Maybe that would be better for differentiating backends? Or maybe a high level feature table (e.g. rating 2D, 3D, Interactivity, performance and maybe noting specialties like vector graphics, ray tracing, etc?)

@SimonDanisch
Copy link
Member Author

Maybe we can have that too, but I think that quickly becomes overwhelming, so we should have a simple, quick to choose version in getting started.

docs/src/index.md Outdated Show resolved Hide resolved
@SimonDanisch SimonDanisch merged commit dcada17 into master Jul 24, 2024
3 checks passed
@SimonDanisch SimonDanisch deleted the sd/getting-started-improvements branch July 24, 2024 21:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-changelog Skips changelog enforcer
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants