Checkbox visualization for multiple-value aggregation types

[jri]

Should be configurable by introducing another View Configuration setting.

[jri]

Originally a quick thought suggests the envisioned checkbox renderer would be just another FieldRenderer? implementation. But actually the checkbox renderer is not covered by the TopicRenderer? framework as it is: while a field renderer processes a *single* simple topic the checkbox renderer would render *multiple* topics.

A solution would be to extend the TopicRenderer? framework by the concept of a MultiRenderer?. A MultiRenderer? would be responsible for rendering "cardinality many" fields. The default MultiRenderer? would render multi fields as they are rendered now: as a sequence with additional "add another" and "remove" buttons. The new checkbox renderer would be an optional MultiRenderer? implementation.

So, the focus of this ticket is now:

• introduce the MultiRenderer? concept
• repackage the current multiple value render logic as the "DefaultMultiRenderer?",
• provide another MultiRenderer? implementation: CheckboxRenderer?.

BTW: it is evident for a while that even another type of renderer would be required to complete the picture: a CompositeRenderer?. This would renderer composite values like a Person or an Address. This will be addressed in a separate ticket.

[Jörg Richter]

Webclient: introduce MultiRenderer? concept (#270).

There is a new view configuration setting: "Multi Renderer URI".

See ticket 270.

• Changeset: 0f03a2f545f581ca59cf1cddb2b8e8acc7b65316
• URL: ​https://github.com/jri/deepamehta/commit/0f03a2f545f581ca59cf1cddb2b8e8acc7b65316

[Jörg Richter]

Webclient: introduce MultiRenderer? concept (#270).

There is a new view configuration setting: "Multi Renderer URI".

See ticket 270.

• Changeset: 7fe0a806b68e42d95dc489683d20efe9b4bf16d4
• URL: ​https://github.com/jri/deepamehta/commit/7fe0a806b68e42d95dc489683d20efe9b4bf16d4

[Jörg Richter]

Webclient: introduce MultiRenderer? concept (#270).

There is a new view configuration setting: "Multi Renderer URI".

See ticket 270.

• Changeset: 0f03a2f545f581ca59cf1cddb2b8e8acc7b65316
• URL: ​https://github.com/jri/deepamehta/commit/0f03a2f545f581ca59cf1cddb2b8e8acc7b65316

[Jörg Richter]

Webclient: checkbox multi-renderer (#270).

Page rendering and form rendering works.
Form processing is pending.

See ticket 270.

• Changeset: ca9a505e4c153f57840b7e53db6f520e19939b6c
• URL: ​https://github.com/jri/deepamehta/commit/ca9a505e4c153f57840b7e53db6f520e19939b6c

[Jörg Richter]

Webclient: refactor page model (#270).

The page model classes are unified.
There is just one class: PageModel?.
The FieldModel? class is dropped.

The page model is represented by a hierarchy of PageModel? instances.
There are 3 types of PageModel? instances:

• SIMPLE
• COMPOSITE
• MULTI

Checkbox multi-renderer form processing is still pending.

See ticket 270.

• Changeset: a90df304402cf9eba7030dfabd54d2cc4ded57d6
• URL: ​https://github.com/jri/deepamehta/commit/a90df304402cf9eba7030dfabd54d2cc4ded57d6

[Jörg Richter]

Pluggable multi-renderer form reading func (#270).

See ticket 270.

• Changeset: 9ae265a5ab76b5acd10653c6d1341aa9018258d8
• URL: ​https://github.com/jri/deepamehta/commit/9ae265a5ab76b5acd10653c6d1341aa9018258d8

[Jörg Richter]

Webclient: the Checkbox Renderer works (#270).

The (form rendering aspect of the) Checkbox Renderer allows the user to select one or more items. The set of possible items comprises all the topic instances of a certain type -- the item type. The item type must be aggregated to a parent type. If a parent's type instance is rendered the checkboxes appear.

To use the Checkbox Renderer enter "dm4.webclient.checkbox_renderer" in the item type's "Multi Renderer URI" view configuration.

Note: for the Checkbox Renderer to work 2 requirements must be met:

1) the item type is associated to its parent type via "Aggregation Definition"

It's in the nature of the Checkbox Renderer that "Composition Definition" doesn't work.

2) parent type -> item type must be a "Many" relationship.

Again, it's in the nature of the Checkbox Renderer that "One" makes no sense.

Technically the Checkbox Renderer is a "Multi" renderer (new concept).
A multi renderer is responsible for rendering the multiple values resulting from a "Many" relationship.

Layout and other minor issues remain.

See ticket 270.

• Changeset: 6c4d87ad42488f2a35327a396d6813a6acbc6734
• URL: ​https://github.com/jri/deepamehta/commit/6c4d87ad42488f2a35327a396d6813a6acbc6734

[Jörg Richter]

Webclient: tweak multi renderer layout (#270).

See ticket 270.

• Changeset: a4c7c5e6dc0ea02b413364758d667362c8ac3fa7
• URL: ​https://github.com/jri/deepamehta/commit/a4c7c5e6dc0ea02b413364758d667362c8ac3fa7

[Jörg Richter]

Webclient: introduce MultiRenderer? concept (#270).

There is a new view configuration setting: "Multi Renderer URI".

See ticket 270.

• Changeset: 7fe0a806b68e42d95dc489683d20efe9b4bf16d4
• URL: ​https://github.com/jri/deepamehta/commit/7fe0a806b68e42d95dc489683d20efe9b4bf16d4

[Jörg Richter]

Webclient: checkbox multi-renderer (#270).

Page rendering and form rendering works.
Form processing is pending.

See ticket 270.

• Changeset: ca9a505e4c153f57840b7e53db6f520e19939b6c
• URL: ​https://github.com/jri/deepamehta/commit/ca9a505e4c153f57840b7e53db6f520e19939b6c

[Jörg Richter]

Webclient: refactor page model (#270).

The page model classes are unified.
There is just one class: PageModel?.
The FieldModel? class is dropped.

The page model is represented by a hierarchy of PageModel? instances.
There are 3 types of PageModel? instances:

• SIMPLE
• COMPOSITE
• MULTI

Checkbox multi-renderer form processing is still pending.

See ticket 270.

• Changeset: a90df304402cf9eba7030dfabd54d2cc4ded57d6
• URL: ​https://github.com/jri/deepamehta/commit/a90df304402cf9eba7030dfabd54d2cc4ded57d6

[Jörg Richter]

Pluggable multi-renderer form reading func (#270).

See ticket 270.

• Changeset: 9ae265a5ab76b5acd10653c6d1341aa9018258d8
• URL: ​https://github.com/jri/deepamehta/commit/9ae265a5ab76b5acd10653c6d1341aa9018258d8

[Jörg Richter]

Webclient: the Checkbox Renderer works (#270).

The (form rendering aspect of the) Checkbox Renderer allows the user to select one or more items. The set of possible items comprises all the topic instances of a certain type -- the item type. The item type must be aggregated to a parent type. If a parent's type instance is rendered the checkboxes appear.

To use the Checkbox Renderer enter "dm4.webclient.checkbox_renderer" in the item type's "Multi Renderer URI" view configuration.

Note: for the Checkbox Renderer to work 2 requirements must be met:

1) the item type is associated to its parent type via "Aggregation Definition"

It's in the nature of the Checkbox Renderer that "Composition Definition" doesn't work.

2) parent type -> item type must be a "Many" relationship.

Again, it's in the nature of the Checkbox Renderer that "One" makes no sense.

Technically the Checkbox Renderer is a "Multi" renderer (new concept).
A multi renderer is responsible for rendering the multiple values resulting from a "Many" relationship.

Layout and other minor issues remain.

See ticket 270.

• Changeset: 6c4d87ad42488f2a35327a396d6813a6acbc6734
• URL: ​https://github.com/jri/deepamehta/commit/6c4d87ad42488f2a35327a396d6813a6acbc6734

[Jörg Richter]

Webclient: tweak multi renderer layout (#270).

See ticket 270.

• Changeset: a4c7c5e6dc0ea02b413364758d667362c8ac3fa7
• URL: ​https://github.com/jri/deepamehta/commit/a4c7c5e6dc0ea02b413364758d667362c8ac3fa7

[Jörg Richter]

Webclient: introduce MultiRenderer? concept (#270).

There is a new view configuration setting: "Multi Renderer URI".

See ticket 270.

• Changeset: 0f03a2f545f581ca59cf1cddb2b8e8acc7b65316
• URL: ​https://github.com/jri/deepamehta/commit/0f03a2f545f581ca59cf1cddb2b8e8acc7b65316

[Jörg Richter]

Webclient: introduce MultiRenderer? concept (#270).

There is a new view configuration setting: "Multi Renderer URI".

See ticket 270.

• Changeset: 7fe0a806b68e42d95dc489683d20efe9b4bf16d4
• URL: ​https://github.com/jri/deepamehta/commit/7fe0a806b68e42d95dc489683d20efe9b4bf16d4

[Jörg Richter]

Webclient: checkbox multi-renderer (#270).

Page rendering and form rendering works.
Form processing is pending.

See ticket 270.

• Changeset: ca9a505e4c153f57840b7e53db6f520e19939b6c
• URL: ​https://github.com/jri/deepamehta/commit/ca9a505e4c153f57840b7e53db6f520e19939b6c

[Jörg Richter]

Webclient: refactor page model (#270).

The page model classes are unified.
There is just one class: PageModel?.
The FieldModel? class is dropped.

The page model is represented by a hierarchy of PageModel? instances.
There are 3 types of PageModel? instances:

• SIMPLE
• COMPOSITE
• MULTI

Checkbox multi-renderer form processing is still pending.

See ticket 270.

• Changeset: a90df304402cf9eba7030dfabd54d2cc4ded57d6
• URL: ​https://github.com/jri/deepamehta/commit/a90df304402cf9eba7030dfabd54d2cc4ded57d6

[Jörg Richter]

Pluggable multi-renderer form reading func (#270).

See ticket 270.

• Changeset: 9ae265a5ab76b5acd10653c6d1341aa9018258d8
• URL: ​https://github.com/jri/deepamehta/commit/9ae265a5ab76b5acd10653c6d1341aa9018258d8

[Jörg Richter]

Webclient: the Checkbox Renderer works (#270).

The (form rendering aspect of the) Checkbox Renderer allows the user to select one or more items. The set of possible items comprises all the topic instances of a certain type -- the item type. The item type must be aggregated to a parent type. If a parent's type instance is rendered the checkboxes appear.

To use the Checkbox Renderer enter "dm4.webclient.checkbox_renderer" in the item type's "Multi Renderer URI" view configuration.

Note: for the Checkbox Renderer to work 2 requirements must be met:

1) the item type is associated to its parent type via "Aggregation Definition"

It's in the nature of the Checkbox Renderer that "Composition Definition" doesn't work.

2) parent type -> item type must be a "Many" relationship.

Again, it's in the nature of the Checkbox Renderer that "One" makes no sense.

Technically the Checkbox Renderer is a "Multi" renderer (new concept).
A multi renderer is responsible for rendering the multiple values resulting from a "Many" relationship.

Layout and other minor issues remain.

See ticket 270.

• Changeset: 6c4d87ad42488f2a35327a396d6813a6acbc6734
• URL: ​https://github.com/jri/deepamehta/commit/6c4d87ad42488f2a35327a396d6813a6acbc6734

[Jörg Richter]

Webclient: tweak multi renderer layout (#270).

See ticket 270.

• Changeset: a4c7c5e6dc0ea02b413364758d667362c8ac3fa7
• URL: ​https://github.com/jri/deepamehta/commit/a4c7c5e6dc0ea02b413364758d667362c8ac3fa7