[ https://issues.oasis-open.org/browse/OSLCCORE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Amsden updated OSLCCORE-10:
---------------------------------
Proposal:
Normalize Preview and Dialog:
1. use four Link headers: smallPreview, largePreview, creationDialog, selectionDialog - all referencing some DialogDescriptor
2. Use one DialogDescriptor class for all dialogs - preview, selection, creation
3. DialogDescriptor::oslc:dialog would reference the actual HTML dialog.
This makes dialog management more uniform, simpler, and eliminates an extra hop for Compact>Preview>document to access one of the preview dialogs.
Compact would no longer refer to the Preview.
was:
Normalize Preview and Dialog:
1. use four Link headers: smallPreview, largePreview, creationDialog, selectionDialog - all referencing some DialogDescriptor
2. Use one DialogDescriptor class for all dialogs - preview, selection, creation
3. DialogDescriptor::oslc:dialog would reference the actual HTML dialog.
This makes dialog management more uniform, simpler, and eliminates an extra hop for Compact>Preview>document to access one of the preview dialogs
> Normalizing Preview and Dialog
> ------------------------------
>
> Key: OSLCCORE-10
> URL: https://issues.oasis-open.org/browse/OSLCCORE-10
> Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
> Issue Type: Bug
> Reporter: James Amsden
> Assignee: James Amsden
> Priority: Minor
>
> Resource-preview uses Compact, Preview and oslc:document to manage previews. Compact defines the preview descriptor and contains properties for small and large previews. Preview contains the size hings and oslc:document link to the actual HTML preview dialog.
> Dialogs-v3 uses Dialog and oslc:dialog with different Link headers for the creationDialog and selectionDialog.
> Should we consider normalizing these different approaches to dialog management?
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
