Moini wrote:* I prefer having it in Animation, I think that's going to make it easier to find for the average user.
Easier to find, but more confusing, I think. You and I know that Inkscape doesn't do animation natively, but a new user doesn't. It's not a problem while the extension needs manual installation, as I think you can assume a reasonable amount of familiarity with the program in that case. But if it ever makes it into a release build (and I think it would be a great extension to be in the default set), I can see new users easily getting confused.
Moini wrote:* As for the last suggestion: It's because I have groups of paths that can be animated at once, so I need an ID. Of course, I could make up a random one, but then users cannot modify an existing animation. It's intentional, to allow for later modification without having to remove all, then reselect everything (see README). It also helps when you just want to remove a specific animation. I cannot list them in an extension dialog, so users need a way to know what they have.
I see what you're saying, but I wonder if you've over-complicated the simple use case in order to support a more complex one that may not be necessary.
As it stands, if I want to separately animate several lines I have to manually keep track of the animation name for each one, and make sure I update the dialog if I want to change the settings on any of them. This, in my view, makes it too easy to accidentally overwrite one path's settings with another's, or to lose track of what name you've used for which path. (I recognise that the issue here is with the limited capability of the extensions UI, and the fact that you can't retrieve the existing ID to put into the dialog)
For the multiple path case, there are several possible alternatives, including:
- Make the animation ID optional. If it's not supplied, create separate animations for each selected path.
- Don't try to handle multiple paths at all. Just let the user set the same settings on each one. It's a pain to update or edit them all in this case, and adds redundant entries in the CSS, but it's simple and avoids some potential problems with multiple edits.
- A way to link to an existing path's animation. Perhaps a second extension: select the path with the animation, then select all the others, and choose Animation > Link Path Animations.
- Require multiple paths to be in a group, and use the group's ID as the basis of a calculated value.
- Require multiple paths to be turned into a single compound path with Path > Combine, reducing the problem back down to animating a single path.
I suspect that most use-cases can be met with just single path animation and the requirement to combine multiple paths if you want them all to share an animation. Once you go beyond the cases that can be covered by that, you're probably well into the realm of wanting either a proper animation tool, or being prepared to wade directly into the CSS in a text editor.