issue219:inkscape
Différences
Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentesRévision précédente | |||
issue219:inkscape [2025/07/30 07:15] – d52fr | issue219:inkscape [2025/07/30 09:22] (Version actuelle) – d52fr | ||
---|---|---|---|
Ligne 4: | Ligne 4: | ||
The category list on the left corresponds to the top-level entries in the Extensions menu. As with the Filters Gallery, selecting one will restrict the displayed thumbnails as you would expect. Hiding the list using the toggle at the top-left switches back to show all the Extensions – which is a sensible design choice, in my view. But if you then toggle back again, you’re left with a view that shows all the extensions, but a list that has a single category selected. Once more, not a major problem, but a silly UX oversight nevertheless.** | The category list on the left corresponds to the top-level entries in the Extensions menu. As with the Filters Gallery, selecting one will restrict the displayed thumbnails as you would expect. Hiding the list using the toggle at the top-left switches back to show all the Extensions – which is a sensible design choice, in my view. But if you then toggle back again, you’re left with a view that shows all the extensions, but a list that has a single category selected. Once more, not a major problem, but a silly UX oversight nevertheless.** | ||
+ | |||
+ | Le mois dernier, j'ai examiné la nouvelle boîte de dialogue « Galerie des filtres ». Ce mois-ci, je vais commencer par la boîte de dialogue « Galerie des extensions », | ||
+ | |||
+ | Cette conception commune implique qu' | ||
+ | |||
+ | La liste des catégories à gauche correspond aux entrées de niveau supérieur du menu « Extensions ». Comme pour la Galerie des filtres, la sélection d'une catégorie limitera les vignettes affichées, comme prévu. Masquer la liste à l'aide du bouton en haut à gauche revient à afficher toutes les extensions, ce qui est, à mon avis, un choix de conception judicieux. Mais si vous cliquez à nouveau, vous vous retrouvez avec une vue qui affiche toutes les extensions, mais avec une seule catégorie sélectionnée dans la liste. Encore une fois, ce n'est pas un problème majeur, mais un oubli absurde dans cette interface. | ||
+ | |||
**It’s worth noting that, unlike the Filters menu, some of the entries in the Extensions menu also contain submenus. These are not reflected in the category list. For example, selecting the ‘Render’ category mixes all the extensions together, including those from the 3D, Barcodes, Gear, and Grid submenus. The actual location of the extension in the menu hierarchy is shown to the left of the Run button when you select a thumbnail, and also in a tooltip when you hover the mouse over one. Again, not a problem as such, but if the hierarchical position is important enough to display at all, then surely it’s important enough to reflect somewhere more obvious in the UI, perhaps by grouping thumbnails through the use of an additional badge or some color coding. | **It’s worth noting that, unlike the Filters menu, some of the entries in the Extensions menu also contain submenus. These are not reflected in the category list. For example, selecting the ‘Render’ category mixes all the extensions together, including those from the 3D, Barcodes, Gear, and Grid submenus. The actual location of the extension in the menu hierarchy is shown to the left of the Run button when you select a thumbnail, and also in a tooltip when you hover the mouse over one. Again, not a problem as such, but if the hierarchical position is important enough to display at all, then surely it’s important enough to reflect somewhere more obvious in the UI, perhaps by grouping thumbnails through the use of an additional badge or some color coding. | ||
Initially I thought that there was some use of badges to indicate categories, when I noticed the flash of triangles at the top-left of some of the thumbnails. This marker indicates that these are all part of the Color category, but there are no such markers used for any of the other categories. Some do have more of a common style within their group, such as the lined notepad design in the Text category. But even here the style isn’t applied consistently across all the extensions.** | Initially I thought that there was some use of badges to indicate categories, when I noticed the flash of triangles at the top-left of some of the thumbnails. This marker indicates that these are all part of the Color category, but there are no such markers used for any of the other categories. Some do have more of a common style within their group, such as the lined notepad design in the Text category. But even here the style isn’t applied consistently across all the extensions.** | ||
+ | |||
+ | Il est important de noter que, contrairement au menu Filtres, certaines entrées du menu Extensions contiennent également des sous-menus. Ceux-ci ne sont pas reflétés dans la liste des catégories. Par exemple, sélectionner la catégorie « Rendu » mélange toutes les extensions, y compris celles des sous-menus 3D, Codes-barres, | ||
+ | |||
+ | Au départ, je pensais que des badges servaient à indiquer les catégories, | ||
+ | |||
**In the Filter Gallery, the thumbnails roughly displayed what the effect of the filter might look like (subject to a few caveats, as I described last month). But for many extensions this isn’t really a practical option, so the thumbnails tend to be more abstract representations of their functionality. On the whole, I would say that the developers have done an excellent job in this respect… with one glaring exception. Of all the categories that could actually have been represented with thumbnails that show the effect of each extension, surely it’s the Raster section? This contains extremely filter-like tools to manipulate bitmap images, with extensions such as Blur, Oil Paint, and Swirl. And yet what we’ve ended up with is a whole category of arbitrary puzzle pieces – presumably the fallback design used when no specific thumbnail has been created. | **In the Filter Gallery, the thumbnails roughly displayed what the effect of the filter might look like (subject to a few caveats, as I described last month). But for many extensions this isn’t really a practical option, so the thumbnails tend to be more abstract representations of their functionality. On the whole, I would say that the developers have done an excellent job in this respect… with one glaring exception. Of all the categories that could actually have been represented with thumbnails that show the effect of each extension, surely it’s the Raster section? This contains extremely filter-like tools to manipulate bitmap images, with extensions such as Blur, Oil Paint, and Swirl. And yet what we’ve ended up with is a whole category of arbitrary puzzle pieces – presumably the fallback design used when no specific thumbnail has been created. | ||
Ligne 14: | Ligne 26: | ||
I’m also going to point out a couple of even more petty issues: Notice how the descender of the ‘g’ in the ‘Oil Painting’ label is cut off? That’s not bad cropping on my part when taking the screenshot – it’s how all the labels with descenders appear in both dialogs. Some of the labels are okay if you select a smaller thumbnail size, but even at the smallest option some are still cut off.** | I’m also going to point out a couple of even more petty issues: Notice how the descender of the ‘g’ in the ‘Oil Painting’ label is cut off? That’s not bad cropping on my part when taking the screenshot – it’s how all the labels with descenders appear in both dialogs. Some of the labels are okay if you select a smaller thumbnail size, but even at the smallest option some are still cut off.** | ||
+ | |||
+ | Dans la Galerie des filtres, les vignettes affichaient approximativement l' | ||
+ | |||
+ | À titre de comparaison, | ||
+ | |||
+ | Je vais également souligner quelques problèmes encore plus mineurs : sur l' | ||
+ | |||
**And the second petty issue? On my AppImage version, at least, the top entry in the categories list says ‘All Effects’ rather than ‘All Extensions’. Does this hint at a Path Effects Gallery to come? Or is it just a typo? | **And the second petty issue? On my AppImage version, at least, the top entry in the categories list says ‘All Effects’ rather than ‘All Extensions’. Does this hint at a Path Effects Gallery to come? Or is it just a typo? | ||
Ligne 20: | Ligne 39: | ||
It might work better if selecting a thumbnail displayed a good description of what the extension does. In some cases there is a description shown on the tooltip, and to the right of the ‘Run’ button when selected. But those descriptions are often so terse as to be useless, and when they are longer, the space next to the ‘Run’ button is far too small to hold them. See, for example, this screenshot with the ‘Level’ extension selected. Compare the description in the tooltip with the useless version next to the ‘Run’ button.** | It might work better if selecting a thumbnail displayed a good description of what the extension does. In some cases there is a description shown on the tooltip, and to the right of the ‘Run’ button when selected. But those descriptions are often so terse as to be useless, and when they are longer, the space next to the ‘Run’ button is far too small to hold them. See, for example, this screenshot with the ‘Level’ extension selected. Compare the description in the tooltip with the useless version next to the ‘Run’ button.** | ||
+ | |||
+ | Et le deuxième petit problème ? | ||
+ | |||
+ | Bien que j' | ||
+ | |||
+ | Il serait peut-être plus efficace d' | ||
+ | |||
**Still, at least the tooltip shows the complete description, | **Still, at least the tooltip shows the complete description, | ||
Ligne 26: | Ligne 52: | ||
Running the extension opens a dialog with four main options that can be toggled with checkboxes. Each of these has a single parameter, controlled by a slider and spinbox combination. The fourth also has a couple of additional parameters.** | Running the extension opens a dialog with four main options that can be toggled with checkboxes. Each of these has a single parameter, controlled by a slider and spinbox combination. The fourth also has a couple of additional parameters.** | ||
+ | |||
+ | Au moins, l' | ||
+ | |||
+ | Puisque nous parlons des extensions, examinons l' | ||
+ | |||
+ | L' | ||
+ | |||
**I had hoped to demonstrate the usefulness of this extension, and how the additional controls make it better than Path > Simplify. But the truth is that I was unable to get this extension to work particularly well with my test images. The reason my screenshot shows the first and fourth checkboxes un-ticked is because enabling either of those usually led to Python error messages and the extension failing to do anything on my machine. On a few occasions Inkscape itself crashed entirely. | **I had hoped to demonstrate the usefulness of this extension, and how the additional controls make it better than Path > Simplify. But the truth is that I was unable to get this extension to work particularly well with my test images. The reason my screenshot shows the first and fourth checkboxes un-ticked is because enabling either of those usually led to Python error messages and the extension failing to do anything on my machine. On a few occasions Inkscape itself crashed entirely. | ||
Ligne 32: | Ligne 65: | ||
This issue will be more or less pronounced depending on your specific path, but I think the underlying problem is that the cut-off lengths are measured in document units, per the note at the bottom of the dialog. Perhaps the option to use units that are proportional to the bounding box perimeter might be more useful, as that should result in ranges that have a similar effect regardless of the absolute size of the path object.** | This issue will be more or less pronounced depending on your specific path, but I think the underlying problem is that the cut-off lengths are measured in document units, per the note at the bottom of the dialog. Perhaps the option to use units that are proportional to the bounding box perimeter might be more useful, as that should result in ranges that have a similar effect regardless of the absolute size of the path object.** | ||
+ | |||
+ | J' | ||
+ | |||
+ | Des deux options qui ont fonctionné, | ||
+ | |||
+ | Ce problème sera plus ou moins prononcé selon votre chemin, mais je pense que le problème sous-jacent réside dans le fait que les longueurs de coupure sont mesurées en unités de document, comme indiqué au bas de la boîte de dialogue. L' | ||
+ | |||
**The ‘Information’ tab of this extension has this to say about it: “Originally created to clean up paths for cutters/ | **The ‘Information’ tab of this extension has this to say about it: “Originally created to clean up paths for cutters/ | ||
Ligne 38: | Ligne 78: | ||
The ‘Close subpaths’ option felt like it needed another control, to determine exactly how to close the subpath. In this example, a copy of the green path did, indeed, have its subpaths closed. But where I had expected an extra line segment to be added, leaving the nodes un-moved, instead the two end nodes were replaced with a single node placed at the average position between them.** | The ‘Close subpaths’ option felt like it needed another control, to determine exactly how to close the subpath. In this example, a copy of the green path did, indeed, have its subpaths closed. But where I had expected an extra line segment to be added, leaving the nodes un-moved, instead the two end nodes were replaced with a single node placed at the average position between them.** | ||
+ | |||
+ | L' | ||
+ | |||
+ | L' | ||
+ | |||
+ | L' | ||
+ | |||
**Finally, the ‘Join end nodes’ option – which failed on the complex path – seemed quite happy to do its job on a much simpler one, healing the break between the two halves of the green path to create the orange version. | **Finally, the ‘Join end nodes’ option – which failed on the complex path – seemed quite happy to do its job on a much simpler one, healing the break between the two halves of the green path to create the orange version. | ||
Ligne 46: | Ligne 93: | ||
This extension certainly has potential, but is currently a little too unstable to recommend as the solution to cleaning up all your messy bitmap traces. By all means play around with it to see how it fares with your own images – just make sure to save frequently!** | This extension certainly has potential, but is currently a little too unstable to recommend as the solution to cleaning up all your messy bitmap traces. By all means play around with it to see how it fares with your own images – just make sure to save frequently!** | ||
+ | |||
+ | Enfin, l' | ||
+ | |||
+ | La modification de l' | ||
+ | |||
+ | L' | ||
+ | |||
+ | Cette extension a certainement du potentiel, mais elle est actuellement un peu trop instable pour être recommandée comme solution pour nettoyer toutes vos traces bitmap désordonnées. N' | ||
issue219/inkscape.txt · Dernière modification : 2025/07/30 09:22 de d52fr