I see that the Element autocomplete is based on the document itself and does not reference the schema. However how does the attribute completion work. I have elements in a file with attributes, however if I create a new element of the same type XML Copy Editor does not suggest attributes from those elements.
For example
<entity table="mytable">
</entity>
<entity (table is not suggested at this point, some other attributes found nowhere in the document are)
Thanks
Tim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The answer is not entirely straightforward. If your document is attached to a W3C schema, attributes should autocomplete as intended.
The same _should_ hold for DTDs.
RELAX NG currently draws on the document itself unfortunately.
I thought autocomplete of the kind you describe should pick up new terms after saving (though not before saving as that would mean a significant overhead that isn't justified until I _finally_ get full background validation running).
Either way I'm sorry the application doesn't work as intended in the use case you describe! Part of the problem is the complexity of different schema languages, which isn't helped by the fact that no parser can handle all schema languages, leading to a patchwork of parser commands.
Regards,
Gerald
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I see that the Element autocomplete is based on the document itself and does not reference the schema. However how does the attribute completion work. I have elements in a file with attributes, however if I create a new element of the same type XML Copy Editor does not suggest attributes from those elements.
For example
<entity table="mytable">
</entity>
<entity (table is not suggested at this point, some other attributes found nowhere in the document are)
Thanks
Tim
Thanks Tim.
The answer is not entirely straightforward. If your document is attached to a W3C schema, attributes should autocomplete as intended.
The same _should_ hold for DTDs.
RELAX NG currently draws on the document itself unfortunately.
I thought autocomplete of the kind you describe should pick up new terms after saving (though not before saving as that would mean a significant overhead that isn't justified until I _finally_ get full background validation running).
Either way I'm sorry the application doesn't work as intended in the use case you describe! Part of the problem is the complexity of different schema languages, which isn't helped by the fact that no parser can handle all schema languages, leading to a patchwork of parser commands.
Regards,
Gerald