docs: Update figures related to GUI #5651
Conversation
github-actions
bot
added
GUI
There was a problem hiding this comment.
This is a nice screenshot, check though that the color in the legend does not correspond to the map displayed. That might be confusing.
There was a problem hiding this comment.
By mistake I used the plain dtm for legend 🙄 thanks for catching @veroandreo!
|
I don't think you can put the images into subfolders without modifying the makefile, so I would avoid that. |
I will find out how much work it is to change in makefiles but if it is not too much, I would do that. Images scattered all over the place among other files don't look good. |
|
I think that it would be nice to engage the community a bit. I suggest sending the post on GRASS dev and LinkedIn: 📣 Help us improve the GRASS GIS documentation! We're currently updating the documentation for GRASS GIS and are looking for screenshots of various tools in the Single-Window GUI (version 8.0 and above). Some of these screenshots may also be included in the updated gallery on the official GRASS website, which highlights the many ways GRASS is used in real-world analysis. 🔧 Screenshots most needed: 🔗 These tools currently have outdated visuals in the documentation. 📌 If you also have other interesting screenshots from your work with GRASS, feel free to send those too — we'd be happy to include a broader range of examples in the gallery. Please send your screenshots — ideally with a short description of what they show — to: Thank you! Even a single image can make a big difference in helping others discover and learn GRASS GIS. 💚 @veroandreo, @petrasovaa What do you think? Feel free to edit. |
There was a problem hiding this comment.
The font between legend and scale bar is inconsistent. I would use a sans serif font. The size in KB is rather large, I would try to reduce it (reduce colors, optimize or even use jpg). See what the size of the other figures are.
Hmmm, I think I wouldn't promise including it in the gallery, people (if they send something) could include all kinds of garbage. The gallery is not super effective anyway, we need more actionable content so that people know how to recreate those images. |
I edited it to not include the part with the gallery: 📣 Help us improve the GRASS GIS documentation! We're currently updating the outdated visuals in the documentation for GRASS and are looking for interesting screenshots of various tools in the Single-Window GUI (version 8.0 and above) which highlights the many ways GRASS is used in real-world analysis. You can see the current screenshots under the "Graphical user interface" section. 🔧 Screenshots most needed: 🔗 Please check whether you might have something more up-to-date and send your screenshots ideally with a short description for a caption to: Thank you! Even a single image can make a big difference in helping others discover and learn GRASS GIS. 💚 @veroandreo could you please share it on LinkedIn? Maybe, I could also make a short lighting call and people here on the summit may help... |
| $(HTMLDIR)/images/help_project_structure.png \ | ||
| $(HTMLDIR)/images/grass_start.png \ | ||
| $(HTMLDIR)/icons/grassdb.png \ | ||
| $(HTMLDIR)/icons/location.png \ | ||
| $(HTMLDIR)/icons/location-add.png \ | ||
| $(HTMLDIR)/icons/location-download.png \ | ||
| $(HTMLDIR)/icons/mapset.png \ | ||
| $(HTMLDIR)/icons/raster-import.png \ | ||
| $(HTMLDIR)/icons/vector-import.png |
There was a problem hiding this comment.
Images vs icons, is this intended?
There was a problem hiding this comment.
We can create just the images folder, no prob - the main goal was to get rid of the mess a bit and have the images separately.
| $(HTMLDIR)/images/help_project_structure.png \ | ||
| $(HTMLDIR)/images/grass_start.png \ | ||
| $(HTMLDIR)/icons/grassdb.png \ | ||
| $(HTMLDIR)/icons/location.png \ | ||
| $(HTMLDIR)/icons/location-add.png \ | ||
| $(HTMLDIR)/icons/location-download.png \ | ||
| $(HTMLDIR)/icons/mapset.png \ | ||
| $(HTMLDIR)/icons/raster-import.png \ | ||
| $(HTMLDIR)/icons/vector-import.png |
There was a problem hiding this comment.
In our makefiles, directories are usually created beforehand, and need to be run before copying to it. Is it needed here too?
And for htmldir image files, does CMakeLists.txt need to be kept in sync? @nilason do you have a preference?
Roadmap of paths for updating GUI images in the new docs (all items under the Graphical user interface combobox in https://grass.osgeo.org/grass-devel/manuals/interfaces_overview.html):
WIP