Currently Web UI extensions have to be defined/loaded in ext/extension.js in order to work. This approach don't work well with multiple extensions packed in separate rpms. Extension code also do not have good means to change out-of-the-box FreeIPA UI pages structure or content. For example - adding a new field to Host detail page.
We need to introduce a mechanism which will: 1. Detect and load Web UI extensions in a form of additional files 2. Allow plugin to add a completely new pages 3. Allow plugin to add new UI fields to existing pages - by modifying page spec - by extending already created pages
More extensible navigation is already requested in #3236.
Regression testing only.
This is a part of 3.2 Web UI refactoring which is already being worked on. Moving to the right bucket.
Petr, please add a design page.
136 commits pushed to master.
first: f0c1c62 last: aedded8
Metadata Update from @pvoborni: - Issue assigned to pvoborni - Issue set to the milestone: FreeIPA 3.2 - 2013/04-05 (GA)
Login to comment on this ticket.