The original goal of this ticket was to be able to customize the views used in the nuxeo-results used by nuxeo-document-content so users would rely on a visual table editor to easily configure listings for folderish documents. Something along these lines:
<nuxeo-document-content> <nuxeo-data-grid>..</nuxeo-data-grid> <nuxeo-data-table>...</nuxeo-data-table> </nuxeo-document-content>
However, nuxeo-document-content's customization would still be very verbose. It would require about as much effort as the new approach we adopted: just using the nuxeo-results directly along with the behavior that encapsulates a most of the logics of nuxeo-document-behavior.
The element nuxeo-document-content still exists solely as a means to prevent duplicated code on Web UI. People wanting to create a custom document content should create an element that:
- Has a nuxeo-page-provider
- Has a nuxeo-results
- Has at least one view inside the results element with class .results
- Uses the Nuxeo.DocumentContentBehavior
- is related to
-
NXDOC-2034 Explain the risk around building custom nuxeo-results elements
- Open
-
NXS-5108 BROWSE_ACTIONS slot deprecated in Web-UI
- Resolved
- is required by
-
NXS-4994 Improve support for listings in folderish doctypes
- Resolved