Use this dialog to add a new property definition to Sisulizer's visual editor.
Specifies the name of the property. The name can contain wild cards (* and ?).
Specifies the default value of the property. Use it if the file does not contain properties having the default value.
VCL: In VCL for example the most used values of properties are not saved. Those values are defined as default values. When a property of a certain component is read the default value will be used if no other value has been saved. The default Alignment property of TLabel control is taLeftJustify. This value is not written to the resource file. The other possible values are taCenter and taRightJustify. If value is one of those it will be written to the resource file.
Normally when you map your own Label-control the default value is usually taLeftJustify. On the other hand if you have a component that's default value should be laCenter you should define Default Value as 1 (the ordinal value of taCenter). If not defined Sisulizer will use taLeftJustify as a default value.
Specifies the type of the property. Some resource formats such as VCL contain type information so Sisulizer can figure out the type of the property even it it belongs to a 3rd party component. However XAML (WPF) resource files, .xaml, do not contain type information. If you map a 3rd party WPF component and it contains a custom property that is not a string type, select the type of the property from the combo box.
.NET: This is visible only of the platform does not provide type information of the property. Windows Forms in .NET contain such information but WPF does not. However because a .NEt project can contains mixed Windows Forms and WPF data this type in show even on pure Windows Forms projects.
Specifies the mode of the property rule. Possible choices are:
|Excluded||Property is ignored when scanning.|
|Included||Property is included when scanning.|
|Structured data||Property contains structured data. Use definitions to specify the data format.|
Check this if you want to scan multi line text into separate rows in the project. By default this is unchecked and multi line text is scanned as one entity.
Contains lines that specify the structure of data. Sisulizer can scan the following structured data:
|Combined strings||Property contains a string that contains a combined string. Enter the regular expression describing the data in the line(s).|
|HTML||Property contain an HTML file. Enter string 'HTML' to the first line.|
Property contain an XML data. Enter one line for each element or attribute that you want to localize. Each line contains the path and name of the element/attribute. Parent and child element are separated by @ character. Attribute name start with # characters. Do not include the name of the root element.
For example if we have the following XML data as property value:
<?xml version="1.0"?> <data caption="Name"> <header>Header</header> <footer>Footer</footer> <sub author="Writer"> <value>Value</value> </sub> </data>
and we want to localize strings marked with bold typeface we need to enter following lines: