chenbo007 / svg-edit

Automatically exported from code.google.com/p/svg-edit
0 stars 0 forks source link

Object Explorer Tree #96

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
SVG-edit should have a tree control in a side panel that shows the entire
SVG DOM tree (with all element nodes).

1) The explorer panel should be unobtrusive (i.e. only present if the user
wants it)

2) Selecting a node in the canvas should highlight that node in the tree

3) Selecting a node in the tree should select that node in the canvas and
update the contextual panels, etc

4) The object explorer should NOT display the internal SVG elements that we
use (selectorParentGroup or its children)

5) Icons for each type of element would be nice.  IDs should be displayed
in another column.

Original issue reported on code.google.com by codedr...@gmail.com on 17 Aug 2009 at 3:26

GoogleCodeExporter commented 9 years ago
Issue 95 has been merged into this issue.

Original comment by codedr...@gmail.com on 17 Aug 2009 at 3:33

GoogleCodeExporter commented 9 years ago

Original comment by codedr...@gmail.com on 17 Aug 2009 at 3:33

GoogleCodeExporter commented 9 years ago
Wow, GMTA I guess. :) 

Not entirely sure it should be the same thing, though...while this would be a 
very
helpful tool and would certainly cover issue 95, I'm wondering if it's a good 
idea to
require the tree for all users.

I'm assuming that some users will just want to use this tool as a vector editor,
without having to know what goes on in the source SVG. This user might be 
confused by
a complex SVG tree and which element name refers to what. 

What do you think? Do we only want to cater to SVG-knowledgeable individuals or 
also
provide a simpler interface for others?  

Original comment by adeve...@gmail.com on 17 Aug 2009 at 3:48

GoogleCodeExporter commented 9 years ago
I agree - this would be invisible for the lay-user.  See reqt 1 above:  the 
explorer
would only be visible if the user clicked a button or something.

If you think issue 95 is different, than please feel free to un-dupe it.

Original comment by codedr...@gmail.com on 17 Aug 2009 at 3:51

GoogleCodeExporter commented 9 years ago
Issue 95 has been merged into this issue.

Original comment by adeve...@gmail.com on 17 Aug 2009 at 8:37

GoogleCodeExporter commented 9 years ago

Original comment by adeve...@gmail.com on 29 Sep 2009 at 11:12

GoogleCodeExporter commented 9 years ago

Original comment by codedr...@gmail.com on 9 Jan 2010 at 11:06

GoogleCodeExporter commented 9 years ago

Original comment by codedr...@gmail.com on 27 Jan 2010 at 9:30