-
Notifications
You must be signed in to change notification settings - Fork 49
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
Documentation reorganization - a suggestion #256
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #256 +/- ##
=======================================
Coverage 94.34% 94.34%
=======================================
Files 13 13
Lines 1697 1697
=======================================
Hits 1601 1601
Misses 96 96
☔ View full report in Codecov by Sentry. |
modules = [ImageFiltering, OffsetArrays, Kernel, KernelFactors, ImageFiltering.MapWindow], | ||
format = format, | ||
sitename = "ImageFiltering", | ||
pages = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a glance of the file changes:
- It is recommended to preserve existing spaces for readability while adding new lines.
- Please remember to add
.DS_Store
to the.gitignore
file to avoid unnecessary commits.
Pad(style::Symbol, lo::Dims{N}, hi::Tuple{}) where {N} = Pad(style, lo, ntuple(d->0,Val(N))) | ||
Pad(style::Symbol, lo::Tuple{}, hi::Dims{N}) where {N} = Pad(style, ntuple(d->0,Val(N)), hi) | ||
Pad(style::Symbol, lo::Dims{N}, hi::Tuple{}) where {N} = Pad(style, lo, ntuple(d -> 0, Val(N))) | ||
Pad(style::Symbol, lo::Tuple{}, hi::Dims{N}) where {N} = Pad(style, ntuple(d -> 0, Val(N)), hi) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the commit. The following is my personal view, please fell free to correct me.
30 file changes in one commit might require more careful attention during code review. Additionally, some of these changes appear to be related to formatting strings. Perhaps we can split this into two separate changes: one for adding a new feature and another for changing the format.
Nonetheless, the file appears to be generally in good condition.
Many thanks for taking on this big task. I managed to build the documentation locally without any issues. There's obviously a lot to read through, but my first impression is that people will find the REPL experience much more pleasant now that you moved the LaTeX out into separate documents. The tutorial you wrote is also really nice, and in general the layout of the documentation feels like a great improvement. One thing I notice is that |
Can we please move this forward?It would be great to get this done, issa common gripe 😓 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, this is huge. Thanks for doing this! I can't pretend I've read everything carefully, but here are a few things I noticed.
Overall I think we should do this. If there's stuff I've missed, we can always fix further problems later.
convolution = imfilter(f,reflect(w),Fill(0,w)) | ||
``` | ||
|
||
## Miscellaneous border padding options |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this section redundant with the one above?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
Best way to make that happen is to give it a thorough review! But you could wait until my comments above are addressed. |
Would adding |
Co-authored-by: Tim Holy <[email protected]>
Co-authored-by: Tim Holy <[email protected]>
@timholy Thanks so much for the comments and review, and for taking the time... I confess I don't understand the fine details of the package, but perhaps the structure of the docs is a bit better now, and in the future will allow people to add more information in the right place. |
When I'm back from travels I'll build this locally and give it a read-through; assuming nothing serious comes up I'll merge as-is and we can fix minor problems later. Or if anyone else wants to build it and do that for me, just let me know the verdict and we can merge more quickly. |
I built it locally, and it looks awesome. Thanks ever so much, @cormullion! A huge contribution! |
Did these docs ever get released? |
This PR comprises a suggested reorganization of the documentation. My approach is probably reasonably similar to the Divio style - at least, try to keep different types of information separate, so that novices, casual users, experienced users, and package developers don't trip over material not meant for them. (I think this is probably the opposite of Images' current approach (judging from this RFC issue.)
The main thing was just to add some hierarchy to the manual, then to move as much stuff out of the docstrings as possible (cf my previous pet gripe, all that LaTeX). 😂
(I'm not too sure how you'd preview this...)