This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 144827 - XSD-design editor should be redesigned with the new NetBeans Visual Library
Summary: XSD-design editor should be redesigned with the new NetBeans Visual Library
Status: NEW
Alias: None
Product: xml
Classification: Unclassified
Component: Schema Tools (show other bugs)
Version: 6.x
Hardware: All Windows Vista
: P3 blocker with 2 votes (vote)
Assignee: Samaresh Panda
Depends on:
Reported: 2008-08-22 10:51 UTC by puce
Modified: 2008-08-22 17:05 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description puce 2008-08-22 10:51:51 UTC
I think the XSD-design editor should be redesigned. Have a look at how XMLSpy does it! It's quite intuitive and very
comfortable in most cases. (Unfortunatly very expensive, too.) A good graphical view of an XSD is very important,
especially if the file is bigger. Maybe this should be realized with the new NetBeans Visual Library.
Comment 1 Samaresh Panda 2008-08-22 15:40:29 UTC
Do you have some reasons to justify or just want this as a face-lift?
Comment 2 puce 2008-08-22 16:31:50 UTC
Both: There are so many basic features missing, it's hard to know where to start. And though the tree-view is not that
bad, I think the graph-view like in XMLSpy shows the information more clearly. Of course, the missing features are more
important than this change in view, but since there are so many features missing and NetBeans has this powerful Visual
Library, it might be worth to migrate to the graph-view right from the beginning.

I really suggest to have a look at the XMLSpy editor, if you have the chance. There's nothing bad to learn from others. ;-)

PS: There are also things in the NetBeans XSD-design editor, which I like better than the way XMLSpy does it eg. the
inline attribute-editor. So, of course, there should not be a stupid 1-to-1 copy of XMLSpy. Just get some inspiration. ;-)
Comment 3 Samaresh Panda 2008-08-22 17:05:42 UTC
XML Schema is not a simple language to begin with.

The DV philosophy in NB is completely different from Spy or JDeveloper for that matter. The idea was to allow user to
draw the outline of the eventual XML document (for which s/he intends to write a schema) and generate schema code
underneath. This is not the same in those tools. They want you to author schemas as though you're an expert in schema
language. OTOH, DV doesn't expect you to be an expert. It has been designed for folks who are not experts in Schema
language nor want to be expert. If you're an expert, use the column/tree view.

And certainly, it can be improved and a lot of things can be added. It certainly has a lot of short-comings. Please
share you thoughts on the missing pieces and we'll see what we can do.