"Eclipse plug-in Development" based on WTP development of custom JSP editors (11)

TLD Content Model analysis View

In the previous section, we analyzed the key features of WTP TLD content model, and briefly introduced the overall structure of WTP content model. In this section, we will develop a WTP TLD content model analysis view to help us more intuitively understand the so-called WTP TLD contents models. The development of this view is very similar to the previous WTP structureddocument analysis view and the WTP structured Model analysis view, and some technical implementation details can be seen in the previous section.

Demand

1, to provide a TLD content model analysis view, in a tree-like format of the current editor JSP documents corresponding to the TLD model display, each tlddocument as a separate node, tlddocument under the holding TLD element and TLD Attribute two level child node

2, Interactive (Editor---> TLD Content Model analysis View):

Activate the JSP editor to instantly update the TLD Content model analysis View

Instantly update the TLD content Model analysis view when the contents of the editor change

Empty TLD content model to parse view contents when current activation editor closes

3, Interactive (TLD Content model analysis View---> Editor)

When you double-click the TLD document node in the view, open the corresponding TLD definition file

4. Further requirements, when the cursor position in the editor changes, immediately update the TLD Content model analysis view. (Note: In the previous section, we analyzed that a TLD document has a location-related feature that gets a list of TLD lists associated with the cursor position, which is the TLD imported ^_^ that can be identified before the cursor position)

"Effect Preview"

1, location-independent TLD Content model analysis Effect preview

As shown, all the TLD Content Document is listed regardless of where the cursor is located in the editor.

2, location-related TLD Content model analysis Effect preview

As shown in the figure, the cursor is between the test1 TLD and the test2 TLD, when the profiling view enumerates only TLD information that can be identified except for the current location. In this position, the test2 TLD is not yet available, so using the tags in test2 will get a WTP error: unrecognized tag. (I think, understanding the properties associated with the TLD Content document location also makes it possible to understand how a particular label can be identified in a particular location in WTP ^_^)