The way you edit images in articles seriously decreases the final quality of articles
-
Dear Editors: The way you edited my article [1] and decreased the size of images permanently, seriously damages the quality of the article and decreases the quantity and quality of info for readers. I have noticed that in the article [1] you edited it so that images are permanently decreased in size to ~640 pixels and are no longer clickable, which were in the past resulting in the pop-up full-size image. The result is that images are so small that are not readable and the quantity and quality of info for the reader is diminished. I think you are doing damage to articles in that way by applying a “uniform look” to the articles. The article is about different GUI solutions, meaning comparing GRAPHICAL representations of different tools. I invested time and effort to select proper screenshots and marked with arrows points of interest. The result was maybe 30 images, from 200-1000 pixels and I uploaded them to the article. I DELIBERATELY didn’t shrink them as I wanted them to be clickable (a feature offered by your editor) so the reader can click and see all details. Now they are shrunk and useless. I saw that your article editor suggests shrinking images to 700 pixels, but most people today have monitors 1500+ pixels wide and want to see all details. Maybe your policy of 700 pixels images is outdated since today many readers want to see more details and have hardware for that. I noticed a similar problem with other articles when showing class diagrams, if they are shrunk, they get unreadable. I think that allowing images to be clickable and pop up in full size is beneficial for articles that contain a lot of images, for example, articles about GUI tools. I like the way it is still in the article [5]. [1] https://www.codeproject.com/Articles/5338960/Git-Comparing-Visual-Studio-2022-with-MeGit-EGit-a [2] https://www.codeproject.com/Articles/5338678/Git-6-Free-GUI-Clients [3] https://www.codeproject.com/Articles/5339681/Git-Multiple-Visual-Studio-Solutions-in-a-Single-G [4] https://www.codeproject.com/Tips/5339527/Git-Visual-Studio-2022-v17-3-0-Line-Staging [5] https://www.codeproject.com/Tips/5339590/Git-Error-Refusing-to-Merge-Unrelated-Histories [6] https://www.codeproject.com/Tips/5339591/Git-Push-from-GUI-Client-Returns-Authentication-Fa
-
Dear Editors: The way you edited my article [1] and decreased the size of images permanently, seriously damages the quality of the article and decreases the quantity and quality of info for readers. I have noticed that in the article [1] you edited it so that images are permanently decreased in size to ~640 pixels and are no longer clickable, which were in the past resulting in the pop-up full-size image. The result is that images are so small that are not readable and the quantity and quality of info for the reader is diminished. I think you are doing damage to articles in that way by applying a “uniform look” to the articles. The article is about different GUI solutions, meaning comparing GRAPHICAL representations of different tools. I invested time and effort to select proper screenshots and marked with arrows points of interest. The result was maybe 30 images, from 200-1000 pixels and I uploaded them to the article. I DELIBERATELY didn’t shrink them as I wanted them to be clickable (a feature offered by your editor) so the reader can click and see all details. Now they are shrunk and useless. I saw that your article editor suggests shrinking images to 700 pixels, but most people today have monitors 1500+ pixels wide and want to see all details. Maybe your policy of 700 pixels images is outdated since today many readers want to see more details and have hardware for that. I noticed a similar problem with other articles when showing class diagrams, if they are shrunk, they get unreadable. I think that allowing images to be clickable and pop up in full size is beneficial for articles that contain a lot of images, for example, articles about GUI tools. I like the way it is still in the article [5]. [1] https://www.codeproject.com/Articles/5338960/Git-Comparing-Visual-Studio-2022-with-MeGit-EGit-a [2] https://www.codeproject.com/Articles/5338678/Git-6-Free-GUI-Clients [3] https://www.codeproject.com/Articles/5339681/Git-Multiple-Visual-Studio-Solutions-in-a-Single-G [4] https://www.codeproject.com/Tips/5339527/Git-Visual-Studio-2022-v17-3-0-Line-Staging [5] https://www.codeproject.com/Tips/5339590/Git-Error-Refusing-to-Merge-Unrelated-Histories [6] https://www.codeproject.com/Tips/5339591/Git-Push-from-GUI-Client-Returns-Authentication-Fa
By default, when you upload a large image the article should only display a tinier one, which, upon clicking, would show the full size version. The only reason we ever intervene to change the image is if this is not working properly. Which happens from time to time. I've made a note to the editorial team to not shrink down your images, and if they must do so, to make sure they link to a bigger image when you click it. Do you happen to have backup images for these articles? If you email them to me (sean@codeproject.com) I'd be happy to fix them all.
Thanks, Sean Ewington CodeProject
-
Dear Editors: The way you edited my article [1] and decreased the size of images permanently, seriously damages the quality of the article and decreases the quantity and quality of info for readers. I have noticed that in the article [1] you edited it so that images are permanently decreased in size to ~640 pixels and are no longer clickable, which were in the past resulting in the pop-up full-size image. The result is that images are so small that are not readable and the quantity and quality of info for the reader is diminished. I think you are doing damage to articles in that way by applying a “uniform look” to the articles. The article is about different GUI solutions, meaning comparing GRAPHICAL representations of different tools. I invested time and effort to select proper screenshots and marked with arrows points of interest. The result was maybe 30 images, from 200-1000 pixels and I uploaded them to the article. I DELIBERATELY didn’t shrink them as I wanted them to be clickable (a feature offered by your editor) so the reader can click and see all details. Now they are shrunk and useless. I saw that your article editor suggests shrinking images to 700 pixels, but most people today have monitors 1500+ pixels wide and want to see all details. Maybe your policy of 700 pixels images is outdated since today many readers want to see more details and have hardware for that. I noticed a similar problem with other articles when showing class diagrams, if they are shrunk, they get unreadable. I think that allowing images to be clickable and pop up in full size is beneficial for articles that contain a lot of images, for example, articles about GUI tools. I like the way it is still in the article [5]. [1] https://www.codeproject.com/Articles/5338960/Git-Comparing-Visual-Studio-2022-with-MeGit-EGit-a [2] https://www.codeproject.com/Articles/5338678/Git-6-Free-GUI-Clients [3] https://www.codeproject.com/Articles/5339681/Git-Multiple-Visual-Studio-Solutions-in-a-Single-G [4] https://www.codeproject.com/Tips/5339527/Git-Visual-Studio-2022-v17-3-0-Line-Staging [5] https://www.codeproject.com/Tips/5339590/Git-Error-Refusing-to-Merge-Unrelated-Histories [6] https://www.codeproject.com/Tips/5339591/Git-Push-from-GUI-Client-Returns-Authentication-Fa
Actually it seems the originals are there. Hold on, let me see if I can fix them.
Thanks, Sean Ewington CodeProject
-
Dear Editors: The way you edited my article [1] and decreased the size of images permanently, seriously damages the quality of the article and decreases the quantity and quality of info for readers. I have noticed that in the article [1] you edited it so that images are permanently decreased in size to ~640 pixels and are no longer clickable, which were in the past resulting in the pop-up full-size image. The result is that images are so small that are not readable and the quantity and quality of info for the reader is diminished. I think you are doing damage to articles in that way by applying a “uniform look” to the articles. The article is about different GUI solutions, meaning comparing GRAPHICAL representations of different tools. I invested time and effort to select proper screenshots and marked with arrows points of interest. The result was maybe 30 images, from 200-1000 pixels and I uploaded them to the article. I DELIBERATELY didn’t shrink them as I wanted them to be clickable (a feature offered by your editor) so the reader can click and see all details. Now they are shrunk and useless. I saw that your article editor suggests shrinking images to 700 pixels, but most people today have monitors 1500+ pixels wide and want to see all details. Maybe your policy of 700 pixels images is outdated since today many readers want to see more details and have hardware for that. I noticed a similar problem with other articles when showing class diagrams, if they are shrunk, they get unreadable. I think that allowing images to be clickable and pop up in full size is beneficial for articles that contain a lot of images, for example, articles about GUI tools. I like the way it is still in the article [5]. [1] https://www.codeproject.com/Articles/5338960/Git-Comparing-Visual-Studio-2022-with-MeGit-EGit-a [2] https://www.codeproject.com/Articles/5338678/Git-6-Free-GUI-Clients [3] https://www.codeproject.com/Articles/5339681/Git-Multiple-Visual-Studio-Solutions-in-a-Single-G [4] https://www.codeproject.com/Tips/5339527/Git-Visual-Studio-2022-v17-3-0-Line-Staging [5] https://www.codeproject.com/Tips/5339590/Git-Error-Refusing-to-Merge-Unrelated-Histories [6] https://www.codeproject.com/Tips/5339591/Git-Push-from-GUI-Client-Returns-Authentication-Fa
Should be all fixed! When creating the article make sure you use the (insert) button for each image to specify the larger dimensions. Otherwise it creates its own default max width of 640 pixels. I have communicated this to the editorial team as well.
Thanks, Sean Ewington CodeProject
-
Should be all fixed! When creating the article make sure you use the (insert) button for each image to specify the larger dimensions. Otherwise it creates its own default max width of 640 pixels. I have communicated this to the editorial team as well.
Thanks, Sean Ewington CodeProject
-
Thank you so much for fixing this issue. I think it is much better this way for the reader because the theme and content are debating the graphical interfaces and advantages vs. deficiencies.
When creating the article make sure you use the insert the button OfGfor each image to specify the larger dimensions. Otherwise it creates its own default max width of 640 pixels. I have communicated this to the editorial team as well.
