-
Notifications
You must be signed in to change notification settings - Fork 11
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
Parameter lists hard to parse by eye #111
Comments
I prefer lines rather than colour. I find the alternating colour of some syntax highlighting very psychedelic and equally hard to read. Ultimately I think part of the problem is our massive signatures rather than the theme. We can probably group a bunch of them to make this simpler. For example all of the size, face_color etc will go into "style=", all of scale, translate etc into "transforms=", properties (deprecated) will go away... Not discussed but maybe name/metadata, opacity, blending can go into "layer_options=". Then you end up with something a lot more reasonable and readable. |
Agree, but this refactor should not be only in the constructor but also on the inner Layers structure. They have too many attributes, and they should be grouped. |
Yes @Czaki, apologies that wasn't clear: the refactor is for the whole stack — it would be very annoying to keep the parameter list and attributes in sync otherwise. |
I think this is much improved with #134 What do y'all think? |
I think we need to simplify our parameter lists 😂 But yes it's so much better 😭 ❤️ |
Parameter lists in
napari
API docs are hard to parse by eye for me - the black wall of text isn't very good for reading:It would be good if there could be some distinction between parameter names and values, perhaps using colour? Or putting each parameter on a newline instead of one continuous line?
The text was updated successfully, but these errors were encountered: