Conversation
…GMT logo (#3849) Co-authored-by: Dongdong Tian <seisman.info@gmail.com> Co-authored-by: Michael Grund <23025878+michaelgrund@users.noreply.github.com> Co-authored-by: Wei Ji <23487320+weiji14@users.noreply.github.com>
Summary of changed imagesThis is an auto-generated report of images that have changed on the DVC remote
Image diff(s)DetailsAdded images
Modified images
Report last updated at commit 2197015 |
…_pygmtlogo_circle_no_wordmark (#4617) Co-authored-by: Yvonne Fröhlich <94163266+yvonnefroehlich@users.noreply.github.com>
…for readability (#4630)
…4634) Co-authored-by: Yvonne Fröhlich <94163266+yvonnefroehlich@users.noreply.github.com>
…nd-white dark-theme logo (#4638)
| "light": (color_light, blue, color_dark), | ||
| "dark": (color_dark, yellow, color_light), |
There was a problem hiding this comment.
| "light": (color_light, blue, color_dark), | |
| "dark": (color_dark, yellow, color_light), | |
| "light": (color_light, blue, red), | |
| "dark": (color_dark, yellow, red), |
There was a problem hiding this comment.
For the color choices, I feel the old version is better, because the GMT-red color makes the text “GMT” too visually heavy and eye-catching, drawing attention away from the logo symbol.
There was a problem hiding this comment.
Hm, that's true coloring also "GMT" makes the wordmark more prominent. I am fine with both versions. Let's see what the others think / prefer 🙂.
|
Considering that the paper is currently under the “Awaiting Editor Decision” status and will likely be accepted without another round of review, the next step will be proofreading, which will be our last opportunity to make any changes to the manuscript. If everything goes well, I expect the paper to be accepted within a few days and enter the proofreading stage in about two weeks. In other words, we need to finalize the logos and make the v0.19.0 release within the next two weeks. I think we should decide whether there are any further changes needed for the logo designs. If everything looks good, we can ask the other maintainers for final reviews. If there are still choices to be made (e.g., #4616 (comment)), we can ask the other maintainers to vote on the remaining options. |
|
@GenericMappingTools/pygmt-maintainers I think this PR is ready for final review. In summary, it implements 24 variants of the PyGMT logo. You can preview all of the proposed designs here: The only remaining point under discussion is the color of the wordmark, i.e., whether the “GMT” letters should be black/white or red (see #4616 (comment), #4627 (comment), and #4616 (comment)). Since we’d like to finalize the PyGMT logo for the upcoming v0.19.0 release, which will accompany the PyGMT paper, we’d really appreciate your feedback on the proposed designs and, in particular, your preference for the wordmark color. |
seisman
added
final review call
|
Sorry for answering late but my time is currently very limited due to parental leave. Potentially it's getting better in late July. Everything looks good to me, I really like that a logo can be used in various formats and colors very soon! |
3 participants
This PR tracks the implementation of the PyGMT logos in different versions.
Logo implementation status
Related PRs and issues
Hexagon shape
Pro
Contra
Some important comments from #3849
Figure.pygmtlogo: Initial version for the circular, colored PyGMT logo #3849 (comment)
projectionandregionparameterswidthandheightparametersKnown issues
-X+wis expected to shift the plotting origin in the x-direction by logo width, but it actually shifts more than that. It's likely an issue with theimagemodule.