You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For almost all plotting modules, we usually have two separate ReST files for modern and classic modes, respectively. For example, we have image.rst and psimage.rst and gmtlogo.rst and gmtlogo-classic.rst.
More ReST files usually mean more maintenance burden, especially sometimes we may fix or update the modern mode examples in one file, but forget to update the corresponding examples in another file.
So, I guess it makes more sense to have only one documentation file for a single module. Usually, the differences of modern and classic ReST files are:
-K/-O/-P is only available in classic mode
Examples have different syntax.
For point 1, this can be addressed by emphasizing the these options are classic-mode only. For point 2, modern/classic modes can be switched using sphinx-design's tab directive (https://sphinx-design.readthedocs.io/en/furo-theme/tabs.html).
While I like the examples in two tabs, I'm afraid I don't like clear the mix of classic and modern in the man pages. I think it is confusing for users. And also, while I'm not really a modern mode user, remember that it was introduced so that new users are advised to use this only. Bring back the classic to front page is a step back on this.
That's a good point. The problem is, there are still many users who use classic mode and there are also many existing classic-mode scripts. So modern-mode users still need to know at least the existence of the classic mode. I think we just need to have a section explaining the differences between classic and modern modes and then link to that section when necessary.
For almost all plotting modules, we usually have two separate ReST files for modern and classic modes, respectively. For example, we have
image.rst
andpsimage.rst
andgmtlogo.rst
andgmtlogo-classic.rst
.More ReST files usually mean more maintenance burden, especially sometimes we may fix or update the modern mode examples in one file, but forget to update the corresponding examples in another file.
So, I guess it makes more sense to have only one documentation file for a single module. Usually, the differences of modern and classic ReST files are:
-K
/-O
/-P
is only available in classic modeFor point 1, this can be addressed by emphasizing the these options are classic-mode only. For point 2, modern/classic modes can be switched using sphinx-design's tab directive (https://sphinx-design.readthedocs.io/en/furo-theme/tabs.html).
#8487 is an example PR showing how it works.
The title:
Classic-only options:
Modern-mode example:
Classic-mode examples (after clicking the "Classic mode" Tab:
The text was updated successfully, but these errors were encountered: