Changes between Version 17 and Version 18 of FDORfc60

Timestamp:

04/13/11 09:25:51 (14 years ago)

Author:

gregboone

Comment:

--

FDORfc60

@@ -716 +716 @@
 }}}
 
+==== Filtering on Features with Annotation Properties ====
+
+TBD…
+
+Q: Can you filter on Annotation values? Join? Computed Values? Do we need to define a textual representation of an Annotation property and subsequently update the FDO filter parser to recognize the new constructs?
+
+==== Accessing Annotation Text Element Stylization ====
+
+Each Annotation object will contain references to its Text Elements exposed through an associated collection of !FdoAnnotationTextElement objects. Text Attributes will be supported for individual Text Entities using XML descriptive text that will be supported through a set of XML serializable objects that allow all of the attributes to be programmatically accessed. 
+
+As mandated by the OGC Simple Feature Access Specification, each Text Element associated to an Annotation will allow attributes to be specified for Style and Layout. Style attributes will include properties for Font, Fill, Stroke and Decoration. Layout attributes will include properties for Alignment, Justification and Spacing. In the FDO API, these properties will be exposed on two new classes !FdoTextElementStyle and !FdoTextElementLayout.
+
+
+{{{
+class FdoTextElementStyle 
+{
+public:
+    FdoString* FontFamily;
+    double FontSize;
+    FdoFontWeightType FontWeight;
+    FdoFontStyleType FontStyle;
+    FdoTextDecorationType TextDecoration;
+    FdoString* FillColor;
+    double FillOpacity;
+    FdoString* StrokeColor;
+    double StrokeWidth;
+    double StrokOpacity;
+};
+}}}
+
+{{{
+class FdoTextElementLayout 
+{
+public:
+    FdoHorizontalAlignmentType HorizontalAlignment;
+    FdoVerticalAlignmentType VerticalAlignment;
+    FdoMultilineJustificationType MultilineJustification;
+    double MultilineSpacing;
+};
+}}}
+
+These two sets of properties shall be exposed through another new Interface !FdoTextElemnetAttributes. This interface will allow both sets of properties to be grouped together yet still allow each group to be accessed separately. Instances of !TextElementAttributes will be associated to the FDO Annotation as a whole through the "!TextDefaultAttributes" property, and to each FDO Text Element through its "!TextAttributes" property.
+
+{{{
+class FdoTextElementAttributes
+{
+public:
+    FdoTextElementStyle* TextStyle;
+    FdoTextElementLayout* TextLayout;
+};
+}}}
+
+===== Processing Text Element Attributes =====
+
+Using the select example preciously documented to query Annotations, we can continue to flush out the on and show how the de-serialized XML string elements can be accessed using the classes described above. 
+
+{{{
+// Since OGC allows text elements to inherit their style
+// from previously defined elements, we will need to save a 
+// "parent" style information as we work down the element array
+FdoTextElementStyleP parentTextStyle;
+FdoTextElementLayoutP parentTextLayout;
+
+// Each Annotation has 0...n Text Elements that are the actual text values
+FdoAnnotationTextElementCollectionP textElements = annotation->GetTextElements();
+for (FdoInt32 i=0; i<textElements->GetCount(); i++)
+{
+    // Get the n’th Text Element and read its style values
+    FdoAnnotationTextElementP textElement = textElements->GetItem(i);
+
+    // As seen above, the XML text will need to be parsed into its API clases
+    FdoStringP textAttributes = textElement->GetTextAttributesAsXml();
+
+    // Convert the FdoString to a char array and stream it into memory
+    const char* charArrayA = (const char*)textAttributes;
+    FdoIoMemoryStreamP streamA = FdoIoMemoryStream::Create();
+    streamA->Write( (FdoByte*) charArrayA, strlen(charArrayA) );
+    streamA->Reset();
+
+    // Create the extended style object (initially empty) and read the style
+    // attributes into it from the XML stream.
+    FdoTextElementAttributesP attributes = FdoTextElementAttributes::Create();
+    attributes->ReadXml(streamA);
+
+    // Extract the text style info. If defined for this element process and display it.
+    // NOTE: The OGC specification allow for elements higher in the display
+    // list to dictate style if the element lower in the array has no style 
+    // information specified. Therefore, save the parent and use it later in the 
+    // array iteration if needed. This applies for the next 3 types as well
+    FdoTextElementStyleP textStyle = attributes->GetTextStyle();
+    if (textStyle) 
+    {
+        ProcessTextStyle(textStyle);
+        parentTextStyle = textStyle;
+    }
+    else if (parentTextStyle)
+        ProcessTextStyle(parentTextStyle);
+       
+    // Extract the layout style. If defined for this element process it for display
+    FdoTextElementLayoutP textLayout = attributes->GetTextLayout();
+    if (textLayout)
+    {
+        ProcessLayoutStyle(textLayout);
+        parentTextLayout = textLayout;
+    }
+    else if (parentTextLayout)
+        ProcessLayoutStyle(parentTextLayout);
+}
+}}}
+  
 
 == Implications ==