Message-ID: <1935453049.11630.1711636167445.JavaMail.appbox@confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11629_944843382.1711636167445" ------=_Part_11629_944843382.1711636167445 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Structure Concepts, Developer's Perspective

Structure Concepts, Developer's Perspective

This article provides an introduction to the main concepts used in Struc= ture. Before starting your work on integration with Structure, please famil= iarize yourself with these concepts.

<= span class=3D"nh-number">1. Basic Concepts Overview

Concept Short Definition API Classes to Check
Structure A named container for a hierarchical list.

Structure, S= tructureManager

Forest A hierarchical list.

Forest, Fore= stService

Row A row is a unique, atomic element = of a forest.

StructureRow, RowManager

Item An item is a user-level object (li= ke Issue) that is displayed in a row.

ItemIdentity, CoreIdentities

Attribute An attribute provides values of a = certain type and meaning for forest rows. AttributeSpec, = StructureAttributeService
Column A column loads one or more attribu= tes and displays information about forest rows. ViewSpecification
View A view is a named collection of co= lumns. StructureView, = StructureViewManager

Important points:

2. A Note on Extensibility

Structure is built with extensibility in mind. It is possible for a sepa= rate add-on to add new item types, attributes, columns and other extensible= elements to Structure, at runtime.

 

------=_Part_11629_944843382.1711636167445--