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

Backend namespace should be inside the Rml namespace #660

Open
iAndyHD3 opened this issue Aug 28, 2024 · 3 comments
Open

Backend namespace should be inside the Rml namespace #660

iAndyHD3 opened this issue Aug 28, 2024 · 3 comments
Labels
discussion Meta talk and feedback

Comments

@iAndyHD3
Copy link

Backend namespace should be under Rml, so that it can be referended as Rml::Backend::. Backend namespace is too generic and the Rml namespace exists for that reason.

@mikke89 mikke89 added the discussion Meta talk and feedback label Aug 28, 2024
@mikke89
Copy link
Owner

mikke89 commented Aug 28, 2024

I see your viewpoint. Right now, the motivation behind having the simple namespace boils down to this statement (from the readme):

The provided renderers and platforms are intended to be usable as-is by client projects without modifications, thereby circumventing the need to write custom interfaces. [...] The provided backends on the other hand are not intended to be used directly by client projects, but rather copied and modified as needed. They are intentionally light-weight and implement just enough functionality to make the included samples run, while being simple to understand and build upon by users.

But I suspect that people start using the backend as is. And perhaps that is fine too for some use cases. I guess it's a broader question of how the backends should be used and integrate into peoples existing code, and I'm sure there are a ton of different use cases to consider.

But in any case, it shouldn't hurt to add it into the Rml namespace, so I might just go ahead and make that change.

@cafeed28
Copy link

in my opinion, backends are something like example implementations of interfaces, so they shouldn't be in the Rml namespace

@iAndyHD3
Copy link
Author

From my understanding, those example implementations are made to actually be used in your engine if possible, either way they're part of the library.

Just to name an example, the backend functions of Dear imgui are all prefixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Meta talk and feedback
Projects
None yet
Development

No branches or pull requests

3 participants