Dynamic UI optimization (refactoring)

Registered by Timur Sufiev on 2014-01-10

Currently, all form definition parsing, fields creation and form instantion are done in ServiceConfigurationForm instance __init__ method, which was not good indeed. This was done partly due to a need to rapidly develop and debug dynamic_ui, partly due to the opinion that using properties and attribute mappings (both of them are stored inside the instantiated form) prevents separating form layout creation from instantiating this form.

It is very desirable to separate form's fields creation (i.e. form class definition) from form instantiation, because form is instantiated much more often (by django) than its class is defined.

Blueprint information

Status:
Complete
Approver:
Ekaterina Chernova
Priority:
Undefined
Drafter:
Timur Sufiev
Direction:
Approved
Assignee:
Timur Sufiev
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Ekaterina Chernova
Completed by
Timur Sufiev

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:dynamic-ui-sessions,n,z

Addressed by: https://review.openstack.org/63640
    Move most of code for dynamic UI form creation into metaclass.

Gerrit topic: https://review.openstack.org/#q,topic:bp/per-tenant-isolation,n,z

Gerrit topic: https://review.openstack.org/#q,topic:bp/dynamic-ui-optimization,n,z

Addressed by: https://review.openstack.org/68339
    Cherry-pick the following commits from master:

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.