-
Notifications
You must be signed in to change notification settings - Fork 3
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
Synchronize naming scheme of data and abstraction layers #7
Comments
This one is a tricky thing as, depending on the language, the name may be a keyword or close to it. Ideally we would want something that is common to the three language and that do not create conflict.
Not so much important but if all could be For the rest, there is little to no impact to the users. We just have to keep a certain coherence (and maybe a doc?) and we should be fine I would say. |
Yes, I'm thinking of something like |
I am already using a namespace The object I would also avoid the usage of |
We're building similar structures in pyclesperanto (P) and clesperantoj (J). Thus, we should make sure that things have similar names and potentially structure repositories similarily. This was done partly from the very beginning (thanks!) and has potential for sychronizing.
The following listing is from the inside to the outside.
Naming this is important, because we will see it a billion times future scripts that use clesperanto
This one is tricky. We are limited here by Java/Maven and Python/Pypi conventions. I can only upload to maven-central if the package starts with "net.clesperanto" because I'm owner of the domain. Packages on pypi typically have the same package name as the python module.
I would love to hear your optinions @StRigaud and @bnorthan 🙂
The text was updated successfully, but these errors were encountered: