... | ... | @@ -76,8 +76,10 @@ The proposed View Specification could look like the following: |
|
|
|
|
|
### Observations:
|
|
|
* Label information is moved out of the Item Definition and Placed in the Specification which seems to make more sense
|
|
|
* Name="*" is a shortcut to refer to all children
|
|
|
* Style=Spatial3D" refers to a specific Item Widget Factory. In this case this factory creates a Widget that is tied to a 3D Point Widget in the Spatial Views. If Style is nit specified then the Basic Item Widget Factory based on the Item Type is used. For example Name uses DefaultStringItemWdiget - Note that the Factory for generating the GUI for the View could override these defaults when processing its components
|
|
|
* Pattern="*" is a shortcut to refer to all child items of the attribute (in their order given by the attribute). This may cause issues with the advance level — did you mean all items or only non-advanced ones. Also, "advance level" may disappear from attributes in the future since it is a markup.
|
|
|
* Style=Spatial3D" refers to a specific Item Widget Factory. In this case this factory creates a Widget that is tied to a 3D Point Widget in the Spatial Views. If Style is not specified then the Basic Item Widget Factory based on the Item Type is used. For example Name uses DefaultStringItemWidget - Note that the Factory for generating the GUI for the View could override these defaults when processing its components. Use cases that may require extensions down the road include:
|
|
|
* When GUI widgets (3d or otherwise) present more or fewer values than an item accepts/requires. An example would be color, where a GUI may only provide 3 values (HSL) while the item may want 4 values (HSL+alpha). Similarly, a GUI widget might provide RGBA values for color where an item only wants RGB.
|
|
|
* It is possible that multiple items will want to share a single GUI widget (3d or otherwise).
|
|
|
* Additional Information can now be specified - for example setting the length for the Name Item
|
|
|
* When an Item has the possibility of generating multiple widgets based on having children items or multiple values, there needs to be an option to control if a single or multiple widgets would be returned.
|
|
|
|
... | ... | @@ -93,7 +95,7 @@ In the case of processing Group Items - it should be possible to indicate if its |
|
|
<Item Name="Point" Style="Spatial3D" OptionPlacement="Widget" GroupValues="true"/>
|
|
|
<Item Name="Group1" GroupChildren="false">
|
|
|
<Layout Type="Form">
|
|
|
<Item Name="*"/>
|
|
|
<Item Pattern="*"/>
|
|
|
</Layout>
|
|
|
</Item>
|
|
|
</Layout>
|
... | ... | |