For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 5 replies, 3 voices, and was last updated 21 years, 10 months ago by
.
-
Posts
-
When I create a new XML Schema, there is no code assist in the source editor. The only options it displays are to add a </schema> tag for the entire document (regardless of where in the document the cursor is and regardless of the fact that there is already a </schema> closing tag) and to add a comment. What needs to be done or what attribute values need to be present in the <schema> or <xs:schema> tag to allow MyEclipse to provide code assist for the new schema document?
Typing a “<” should prompt for an <element>, <annotation>, etc. using namespace prefixes as appropriate. Typing a “</” should close the appropriate tag as in normal XML documents.
Thank you for your time and help.
Talanari,
At the moment, code assist in the source editor for schemas simply isn’t supported because a much richer capability is available visually in the Outline View, the Properties View, and the editor’s Graph page. Schemas can be so complex to get correct that the visual tools are highly recommended to ensure that they’re correct. I think you’ll find it much easier to use them than simply typing in source.
I would also say that the code the visual editor creates is very clear and nicely formatted, its not horrifc by any means.
Avoiding a discussion on visual tools and source tools, my colleague and I are interested in editing the schemas with the source editor. It seems to me that this functionality should be either inherit, or almost trivial to add, to the schema source editor. Correct me if I am wrong, but my understanding is that when I edit an XML document, the XML editor uses the appropriate .xsd or .dtd file to provide code assist for that XML document. I’m assuming that MyEclipse uses the attributes of the root tag to determine which schema, .xsd file, it needs to use to validate the document and provide code assistance. I don’t understand why the schema editor cannot use the exact, or almost exact, same code to process the XMLSchema.xsd file, which is the schema for a schema file, to validate the new schema and provide code assist. In other words, why can’t MyEclipse use XMLSchema.xsd to provide code assist for new schemas in the same way it uses other .xsd files to provide code assist for other XML documents?
Thank you for your time and help.
