Bug 561742 - [AF] Editor (Diagram/Table/Model2Doc) model creation must have a larger common API
Summary: [AF] Editor (Diagram/Table/Model2Doc) model creation must have a larger commo...
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Others (show other bugs)
Version: 4.7.0   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: 6.0.0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: api, consistency, plan
Depends on: 561371
Blocks:
  Show dependency tree
 
Reported: 2020-04-03 11:19 EDT by Vincent Lorenzo CLA
Modified: 2020-12-10 08:02 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Lorenzo CLA 2020-04-03 11:19:27 EDT
Currently in Papyrus, each editor (Diagram, Table, DocumentStructureTemplate) use its own API to create the new editor and register it in the notation file (or in another place), and to open or not, the created editor. 

The purpose of this bug is to create a new clean, clear, useful and well defined API for the editor creation, with minor required override for each specific editor. 

here some existing commands (which implement AbstractHandler and I think it should not at this leavel)...: 
org.eclipse.papyrus.infra.gmfdiag.common.AbstractPapyrusGmfCreateDiagramCommandHandler
org.eclipse.papyrus.infra.nattable.common.internal.command.ITableCreationCommand
org.eclipse.papyrus.infra.nattable.common.handlers.PolicyDefinedTableHandler
org.eclipse.papyrus.model2doc.documentview.ui.menu.handler.CreateDocumentViewEditorHandler

More generally, the editor (Diagram/Table/Model2Doc) must share more API.