-
Notifications
You must be signed in to change notification settings - Fork 20
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
Display is too rich as default #83
Comments
I am open to whatever. I have to dmit I'm also a little confused how much detail each of the printing functions are supposed to provide in julia. My rationale for this was to have a brief default show function and a show for text/plain that gives the full overview. Especially for interactive work in the repl it's nice to get a visual interpretation and directly see changes to parameters. Or are you concerned with the detail when using print? |
I don't have strong feelings myself. I see Christoph's point that there are certainly scenarios where a long printout could be cumbersome and that argues for an alternative function to show more detail. However, the argument against that in my mind would be that a user might not be aware that that function exists and then feel frustrated that (they perceive that) there's no convenient way to display more detail...I suppose one (admittedly clunky) solution would be to add a little parenthetical thing into the output of the briefer one to tell the user about this other function, perhaps with an additional dispatch so it only displays once if you're calling it on an array of objects. I'm not sure if that's worth the inelegance, though... |
If I have a unit cell as here
then If I have a structure from a large simulation, then I think this is simply silly:
|
Just add the rich display into the docs:
|
an alternative option could be to have the rich display as default but add a global variable in AtomsBase that I can change to make it slim. |
And btw, I can't use semi-colons, because I do want a little bit of visual feedback. |
I agree. This is useless. We should only do the extensive printing for small cells. You can always manually call the visualise function if you want (which we should document better). |
I think adding it to the docstring makes the most sense. I'm also fine with only including the full bounding box in the detailed printout too, so that we can keep the default to be one or two lines. |
I appreciate this is largely personal preference:
The extremely detailed and rich text-based summary of the
Atoms
object is nice, but as a default I think it gives far too much information for my taste. I normally, want to see a very brief summary (cf Lux layers) and then the option to for a more detail. E.g. there could be arich_display
function added toAtomsBase
.How do others feel about this?
The text was updated successfully, but these errors were encountered: