1. XML Editor:
   
   1. Some sort of intelligent guesses as to the tags, name spaces, attributes, and values that the user wants.
      
      1. As you type, it would list valid values that it knows of in a drop down.
      2. If you enter something it thinks is invalid for that location, it would use something like a tooltip to warn you. (I have put the id of an attribute that I was creating manually in the tag field. This would help.) However, it would let you put that value in as it might have an out of date version of what is allowed.
   2. If the user attempts to move a node outside a top-most layer that should be in a layer (like a path), warn the user with a tooltip-popup. (That is something I did on accident. I then spent some time looking for it. )
   3. If the user attempts to put a node inside another node, check to see if that combination makes sense. A path within a rect? Warn the user with another tooltip-style popup.
   4. When the user is dragging and dropping text, emulate Firefox 3.x's method of showing the user where they are dropping. The existing system hides the drop point.
   5. When the user is dragging and dropping nodes, emulate Google Earth's latest method of showing the user where they are dropping. The existing system makes it too easy to drop the dragged object into another object. I accidentally moved a object into a path. For this reason, I found it more convenient to use the move up/down buttons than to drag.
   6. When you are editing the value of an attribute, the text box lets you press Enter/Return and it will put a newline into the string. This doesn't make sense to me. Rather, I would like to see Enter/Return trigger the Set button.
   7. When the user changes the name of an attribute in the attribute name field, set the value to blank.
2. Animation: Even if the UI for adding animation is no more advanced than the existing UI for adding links (that is, you manually edit each field), Inksacpe must have a built-in means of previewing the animation.
3. XLinks:
   
   1. Merge the XLink properties window into the Object properties window (which would change depending on the object type.
   2. Have that window list valid values for each field
   3. Have it show reserved fields as blank boxes showing just "reserved". If the user clicks it, a message box appears reminding the user that the field is reserved. It would have a button that would allow the user to state they want to put a value there anyway.
   4. Same with fields that have only one known value, only the value would be shown.
4. Document properties window: Put in a new tab listing the name spaces that are declared by the document.

xxxDex wrote:I really would like resizable "save as" window.