You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Sierra is distributed via Maven Central at [org.httprpc:sierra](https://central.
14
14
15
15
A [DTD](sierra.dtd) is provided to assist with editing. It is not used for validation and is not required.
16
16
17
-
A custom DTD can be generated using the [DTD encoder](sierra-tools/dtd-encoder) tool. An interactive [preview tool](sierra-tools/previewer) is also available.
17
+
A custom DTD can be generated using the [DTD encoder](sierra-tools/dtd-encoder) tool. An interactive [previewer](sierra-tools/previewer)tool is also available. Both can be downloaded [here](https://github.com/HTTP-RPC/Sierra/releases).
18
18
19
19
# Sierra Classes
20
20
Sierra provides the `UILoader` class, which can be used in conjunction with the following types to to declaratively establish a hierarchy of user interface elements:
The first argument represents the path to a properties file containing the custom bindings. Keys represent markup tags, and values are the fully qualified class names to which the tags will be bound. For example:
10
+
11
+
```properties
12
+
chart-panel = org.jfree.chart.ChartPanel
13
+
```
14
+
15
+
The second argument is the path to a directory containing the dependencies (typically the JAR files containing the types to be bound).
16
+
17
+
Both arguments are relative to the current directory.
18
+
19
+
If no arguments are provided, the standard Sierra DTD will be generated.
0 commit comments