|
@@ -67,13 +67,26 @@
|
67
|
67
|
# EmFields defines what kind of datas can be stored in EmTypes. Actually its the associationg with an EmFieldtype ( see @ref lodel2_fieldtypes )
|
68
|
68
|
# that really defines what kind of datas can be stored.
|
69
|
69
|
#
|
70
|
|
-# @subsection lodel2_arch_edmod_fig Editorial model figures
|
|
70
|
+# @section lodel2_arch_ui Lodel2 user interfaces
|
71
|
71
|
#
|
72
|
|
-# @subsubsection lodel2_arch_edmod_fig_components Editorial model main components
|
|
72
|
+# All access to datas are made via UI. UI actions are composed with 3 or 4 elements :
|
|
73
|
+# - user
|
|
74
|
+# - action (Crud actions ?)
|
|
75
|
+# - target
|
|
76
|
+# - sometimes datas
|
|
77
|
+#
|
|
78
|
+# Each actions are send to Lodel2 ACL that check permissions and forward the actions to leapi. leapi send back a reply to the
|
|
79
|
+# UI. And the response get formatted by UI templates. ( see @ref lodel2_arch_ui_fig )
|
|
80
|
+#
|
|
81
|
+# @section lodel2_arch_fig Figures
|
|
82
|
+#
|
|
83
|
+# @subsection lodel2_arch_edmod_fig_components Editorial model main components
|
73
|
84
|
# @image html graphviz/em_components.png
|
74
|
|
-# @subsubsection lodel2_arch_edmod_fig_relations Editorial model relations between components
|
|
85
|
+# @subsection lodel2_arch_edmod_fig_relations Editorial model relations between components
|
75
|
86
|
# @image html graphviz/em_relations.png
|
76
|
|
-# @subsubsection lodel2_arch_edmod_fig_hierarchy Hierarchical relations between EmTypes given a classtype
|
|
87
|
+# @subsection lodel2_arch_edmod_fig_hierarchy Hierarchical relations between EmTypes given a classtype
|
77
|
88
|
# @image html graphviz/em_types_hierarch.png
|
78
|
|
-# @subsubsection lodel2_arch_edmod_fig_em_example Example of editorial model
|
|
89
|
+# @subsection lodel2_arch_edmod_fig_em_example Example of editorial model
|
79
|
90
|
# @image html graphviz/example_em_graph.png
|
|
91
|
+# @subsection lodel2_arch_ui_fig Lodel2 UI schema
|
|
92
|
+# @image html graphviz/lodel2_ui.png
|