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.
A nice feature to have: autocompletion when editing an attribute of type IDREF. The set of possible completions would be the set of values of attributes of type ID in the same document, restricted to those that start with the current value of the IDREF attribute being edited. Of course this should also catch IDs in parsed entities referenced in the docment. Does that make sense?
Generally, it makes sence. Could you explicitly say what document type you are editing? Does it heavily uses ID - IDREFS? Is it a widely used standard? The use case will determine priority. Thanks a lot
Sure: I'm using DocBook. That's probably a pretty general use case (and increasingly so) ... in any case we use it for all of our documentation here. When you enter an <xref linkend="req.func"/> cross-reference, the linkend attribute is an IDREF and refers to the id attribute (of type ID) of some <section> or <figure> or such. Project documentation (such as requirements specifications and design documents) as well as technically-oriented user documentation tends to be heavily loaded with cross-references ... I probably write an <xref> every two minutes or so when I'm in the doc mode.
Thanks, it is definitelly worth to implement it. DocBook is widely recognized.
Let these are considered while planning next release.
Target milestone was changed from not determined to TBD
Another dTD features worth to support are: - complete enumerated attribute value - support sequence content models
For 3.5 I accepted following bug #30095. It's the same as your original and it is the first step while implementing this enhancement.
BTW I think all of these things would be useful for Ant code completion too: 1. <classpath refid="@ [@ = cursor at time of Ctrl-Spc] should offer the IDs of <path> elements in the script. 2. <zip whenempty="@ should offer "skip", "create", "fail" according to the EnumeratedAttribute. Not sure if these things would be implemented completely independently in the Ant grammar module, or whether the XML module would provide a foundation for doing this that would also be used by DTD completion.
I guess standalone solution (similar to XSLTGrammar) should be used in Ant. Regarding IDs I plan to add hook at Check and Validate actions so a grammar could hook itself and rescan declared IDs once document is well-formed. Another possible, better and long-term solution is to add support for model listeners so grammars could listen on new attributes, removed attributes, etc.
Unscheduling from my todo list. New owner is gladly welcome. Meanwhile assigning to abstract issues@xml.netbeans.org owner.