Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upSidebar columns are too narrow so variable and method names are cut in half #29
Comments
This comment has been minimized.
This comment has been minimized.
|
Thanks for this excellent package! I'm reporting this first, and then I'm going to take a peek at coming up with a pull request. My guess is that my solution will be a "single column sidebar" option that you can turn on but I haven't even looked at the code yet. :-) |
This comment has been minimized.
This comment has been minimized.
|
Ah, so I haven't really even figured out where you render the sidebar and I'm out of time for this increment. Let me know if you have some hints as to how to proceed... |
kernc
added
the
bug
label
Feb 13, 2019
This comment has been minimized.
This comment has been minimized.
|
Ah, very cool! So I could easily override this in my own template, and I will. It might be... that this is supposed to be a really simple dox generator, that "one column mode always" might be the best for 95% of the world, and the other 5% can override |
This comment has been minimized.
This comment has been minimized.
|
I like the two-column mode on wide screens. I'd rather consider an alternative CSS implementation, such as two separate lists floated left or additional CSS media queries. |
This comment has been minimized.
This comment has been minimized.
|
Well, unfortunately the customization was too easy so you robbed me of the
impetus to fix it! :-D
(Also, it seems I have a new job too...)
The documentation looks so nice, and took a tiny fraction of the time it
took me to get Sphinx going on my last project. I'll be using pdoc by
default from now on....
|
kernc
referenced this issue
Feb 14, 2019
Merged
BUG: Make TOC lists multi-column only when wide enough #31
This comment has been minimized.
This comment has been minimized.
|
The problem with overridden templates is maintaining them. Even as the API is mostly stable and shouldn't break customized templates in the near future, you're on your own merging in any likely forthcoming improvements. As an alternative, care to test PR #31 and see if it works well with your project on various zoom / browser width levels? |
rec commentedFeb 13, 2019
Expected Behavior
Variable names (e.g. class methods or members) that aren't "too long" should be displayed on one line
Actual Behavior
Variable names above 10 characters or so are split over two lines
Steps to Reproduce
instance_variablesinClassis cut in half unless the window is extremely wideAdditional info