laminlabs / nbproject

Light-weight Jupyter notebook tracker.
https://lamin.ai/docs/nbproject
Apache License 2.0
34 stars 0 forks source link

Improve header formatting #157

Open Zethson opened 2 years ago

Zethson commented 2 years ago

From the docs image

50% of the success is visuals :)

  1. Consider using a Rich table maybe? It is "bigger" but looks more professional. See below for argument against this.
  2. Generally, color might be nice.
  3. The dependencies must be formatted more nicely. One dependency per row to more easily digest the information
  4. Argument against Rich tables: They cannot be properly collapsed. Consider using HTML formatting to allow for the interactive selection and hiding of information.
falexwolf commented 2 years ago

Thanks, Lukas! This is valuable feedback! We'll consider, and I'd also really like to discuss.

Rationale for dependency formatting is having them copy-pastable into a pip install .... If we do it in any other way, that won't be the case anymore. They're alphabetically sorted, and they're not meant to explode but represent the key dependencies the analyst deems crucial for the result of the notebook.

I have a quite strong opinion of keeping them in one row until things get fancier an interactive. But I'm also happy to re-think that opinion!

Zethson commented 2 years ago

You also have a command to export them to a requirements.txt file, which in turn is pip installable. This covers your use-case for me.