Lines Matching refs:a
8 "StructuredDocument" API. There isn't exactly a lot of documentation on
9 this out there, so this is a short explanation of how it works, totally
10 based on _empirical_ evidence. As such, it must be taken with a grain of salt.
16 1- Get a document instance
19 To get a document from an existing IFile resource:
28 Also note that this parses the content of the file on disk, not of a buffer
31 There is a counterpart for non-existent resources:
36 the place that we wanted to modify and then generate a TextFileChange
37 for a refactoring operation. Consequently this document doesn't say
47 The document contains a list of region collections, each one being
48 a list of regions. Each region has a type, as well as text.
144 inside a tag.
146 Note that an XML_CONTENT region is actually the whitespace, was is known as a TEXT in the w3c DOM.
148 Also note that each outer region has a type, but the inner regions also reuse a similar type.
149 So for example an outer XML_TAG_NAME region collection is a proper XML tag, and it will contain
150 an opening tag, a closing tag but also an XML_TAG_NAME that is the tag name itself.
158 here, the only case where it matters is in a tag such as <string name="my_string">: for the
176 Given a region collection, you can also browse regions either using a getRegions() list, or
180 There are a few other methods available in the regions classes. This was not an exhaustive list.