From bbd4a794525bef76a72f017903732ca89a995a39 Mon Sep 17 00:00:00 2001 From: nathan Date: Thu, 12 Dec 2024 11:07:57 -0700 Subject: [PATCH] Some docs on disabled vs readonly vs hidden --- .../pages/getting-started/widgets.md | 27 ++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/doc/etemplate2/pages/getting-started/widgets.md b/doc/etemplate2/pages/getting-started/widgets.md index 3a1054d54e..70fd029f21 100644 --- a/doc/etemplate2/pages/getting-started/widgets.md +++ b/doc/etemplate2/pages/getting-started/widgets.md @@ -21,4 +21,29 @@ If you just want to use existing widgets, you can put them in your .xet template ``` -Rendered example template \ No newline at end of file +Rendered example template + +## Attributes + +Widget behaviour is customised by setting attributes + +### ID + +// TODO, maybe some notes about content & namespaces. + +### Disabled vs Readonly vs Hidden + +Disabled widgets are fully shown, but in a way that indicates the value cannot be changed. + +Readonly widgets are shown in a special way that displays a value, but is not interactive. Often we switch to a +different component for faster performance, such as a simple +label. It is impossible to change the value of a readonly widget. + +Hidden widgets are not visible. + +```html:preview + + + + +``` \ No newline at end of file