Created attachment 783253 [details] Data modeler editor Description of problem: If you compare attached screenshots for different editors you find out that different editor contains different File menu. Version-Release number of selected component (if applicable): 6.0.0.CR1 How reproducible: Steps to Reproduce: 1. open BPMN2 process 2. open Enumeration 3. open Form Buider 4. open Project Explorer 5. open Data Modeler Actual results: BPMN2 process - designer contains button in toolbar, which groups Save and Delete operation Enumeration - all file operation is represented by own button in active tab (closed to "X" button) Form Builder - contains just Save button in the own tab menu Project Explorer - menu File in active tab contains only one operation "Save" Data Modeler - menu Data Modeler in active tab contains 'new object', 'Save' Expected results: All these editors should implements same GUI interface for basic operations. User should know where finds these operation in all assets, not just in one. I think that File operation as "New Item", "Delete" ("Copy", "Rename") should be a part of Project Explorer/File Explorer, because these operation are independent on asset. I hope that it is just about File System. Of course, this means that project/file explorer needs some mechanism how select particular file(s) (checkboxes, mark element as selected (CTRL+click on element), etc.) The implementation of the operation Save can be different for a different asset, but still all assets should be able to save. I think that this button should be in active tab (same position as in Enumeration). I hope that this should be resolved by the inheritance of super class - Editor (Panel), which contains a default implementation of operation save and each editor can override this method. Of course, it is ok, if asset has own toolbar (like designer, data modeler), which contains operation save. The main idea is that there exists one approach which is same for all editors. Additional info:
Created attachment 783254 [details] Enumeration editor
Created attachment 783255 [details] BPMN2 editor
Created attachment 783256 [details] Form Builder editor
Created attachment 783257 [details] Project editor
Tony, could you please ensure Project Editor is consistent with the Enumeration Editor (which has the same menus as all drools-wb editors) - or at least the menu items it needs, but laid out the same (i.e. CRUD are not in a drop-down). Once you're done (and commented your commits on this ticket) please re-assign to one of the other parties. Thanks.
The default look for the Drools side is not what the image for Enum editor has, except we have spaces between the menu items. Passing this to Kris.
QE considers this optional for 6.0.1.
Fixed in 6.2.0.GA. All mentioned asset types use unified toolbar style.