My comments, from the viewpoint of the plan we've worked out with Aaron:
- Live Effects need to work with opening and saving a file, so they need
to be stored somewhere. I was thinking we could add a "inkscape:live-effect" node in the defs section to define each live effect and read them when the file is opened.
Do you mean storing the code of the effect? We didn't yet plan on that, just using one of the predefined effects coded in Inkscape. Which one is used is specified in an extension attr. It's all compatible with SVG renderers, of couse, what they see is the path with that effect already applied.
- Live Effects should be triggered when the original objects are edited,
so we need to mark who those are. Probably by node ID.
It's already coded in SPShape which is the parent of shapes and paths. No need to use element ids, just each effected object stores its effect name and parameters and it's all automatically reapplied and updated.
- If one of those nodes is deleted in the process of running the effect,
then it should be stored in the live-effect node so that when re-running the effect it can be placed back on the canvas temporarily.
No, you seem to have quite a different idea of effects than we did. I will now forward my messages to Aaron explaining how our idea should work.
- We need to keep track of the objects that are created by the effect,
so we can delete them before rerunning the effect. I think this could also be accomplished through a node ID.
Our effects do not (yet) create any objects, just modifying existing paths. Effects that create objects (eg blends) would be the next step.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org