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: docs/classic-ui/views.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,19 @@ Views are usually a combination of:
18
18
- a Python class, which performs the user interface logic setup, and
19
19
- corresponding {ref}`plone:classic-ui-templates-label`, or direct Python string output.
20
20
21
+
```{eval-rst}
22
+
.. graphviz::
23
+
:align: center
24
+
25
+
digraph viewstructure {
26
+
{
27
+
node [margin=5,shape=box]
28
+
}
29
+
ZCML -> {Python, Template};
30
+
}
31
+
```
32
+
33
+
21
34
Templates should kept simple and logic kept in a separate Python file. This enhances readability and makes components more reusable. You can override the Python logic or the template file, or both.
22
35
23
36
When you are working with Plone, the most common view type is `BrowserView`
0 commit comments