-
Type: Task
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.9
-
Component/s: None
-
Tags:
-
Backlog priority:545
We don't want to let the user continue editing the current "Summary layout" tab in Document feature, neither the Content view tabs. Those two features are superseded by the Tabs designer.
For target platform >=5.6 and for which there is no former summary tab or content vie tab:
- Summary layout is not displayed
- Under the Tabs tab of Document feature, we want
- Default Tabs filtering (this would require improvements, not in the current scope)
- Custom tabs: This tab would at least have a presentation text so as to redirect to the Tabs feature, and at best, would list the currently declared custom tabs that can potentially be displayed on the document type of the considered Type feature instance (because there is no filtering rule on the type attribute, or because the filtering rule returns true for the current type). If the option with the list is chosen, tabs names should be clickable to go the feature editor.
For projects who have switched to 5.6 and who have former summary layout and content view tab already configured,
we should force the display, with a deprecated warning (like for the theme) and a button to migrate. As we are sure (contrary to the theme) that the result will be 100% identical, it is not necessary to implement the switch back, but we should invite the user to commit/tag before doing the migration. Another approach could be automatic migration, but I find it a bit over-automated for the end user, who wouldn't know what happened (This is to be discussed, the latter option could be ok if it is too much work otherwise, but we should have a generic approach for this kind of problem). Maybe it could good also to force the user to click on the migration feature before being able to build the project (and even more generally, to prevent from building the project if there is an Error (red one).