[
https://jira.nuxeo.org/browse/NXS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anahide Tchertchian updated NXS-227:
------------------------------------
Description:
In studio, we should be able to define content views in a new feature (new item
on the tree, like virtual navigation for instance)
Edition screen:
---> Provide form layout with query operator
The way it works today for advanced search configuration should be kept.
---> Configure an action filter
We already have such interfaces.
---> Provide the NXQL query, with dynamic access to the context
It is not clear to me what context we would have access to, although this
is very important and we need to define it accurately.
---> Design the resultset screen
* to design a result set, the user should drop fields in a one-line table.
* there would be built-in static widgets, such as live edit link, download
link, pdf transfo, path, ...
* for a given widget, it is possible to configure whether it is sortable
or not (the default sort is given in the query configuration, not here)
was:
In studio, we should be able to define content views in a new feature (new item
on the tree, like virtual navigation for instance)
Edition screen:
---> Provide form layout with query operator
The way it works today for advanced search configuration should be kept.
---> Configure an action filter
We already have such interfaces.
---> Provide the NXQL query, with dynamic access to the context
It is not clear to me what context we would have access to, although this
is very important and we need to define it accurately.
---> Design the resultset screen
* to design a result set, the user should drop fields in a one-line table.
* there would be built-in static widgets, such as live edit link, download
link, pdf transfo, path, ...
* for a given widget, it is possible to configure whether it is sortable
or not (the default sort is given in the query configuration, not here)
* a preview would be enabled. How do I see it working ? When
contributing a new document type, we would provide a sample set of values for
all the fields. the preview in studio would be an iframe that renders the
configured layout, puting the document with the sample values in it. There
would be a dropdown box to change the tested document type.
> Add new "content views" feature in studio
> -----------------------------------------
>
> Key: NXS-227
> URL: https://jira.nuxeo.org/browse/NXS-227
> Project: Nuxeo Studio
> Issue Type: Sub-task
> Reporter: Anahide Tchertchian
> Assignee: Anahide Tchertchian
> Fix For: 1.6
>
>
> In studio, we should be able to define content views in a new feature (new
> item on the tree, like virtual navigation for instance)
> Edition screen:
> ---> Provide form layout with query operator
> The way it works today for advanced search configuration should be
> kept.
> ---> Configure an action filter
> We already have such interfaces.
> ---> Provide the NXQL query, with dynamic access to the context
> It is not clear to me what context we would have access to, although
> this is very important and we need to define it accurately.
> ---> Design the resultset screen
> * to design a result set, the user should drop fields in a one-line
> table.
> * there would be built-in static widgets, such as live edit link,
> download link, pdf transfo, path, ...
> * for a given widget, it is possible to configure whether it is sortable
> or not (the default sort is given in the query configuration, not here)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
