Bug 399869 - [Widgets] Papyrus shall implement extension filters on the “import…” UI
Summary: [Widgets] Papyrus shall implement extension filters on the “import…” UI
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.10.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: M7   Edit
Assignee: Camille Letavernier CLA
QA Contact:
URL:
Whiteboard: Usability
Keywords: plan
Depends on: 404918
Blocks:
  Show dependency tree
 
Reported: 2013-02-04 07:55 EST by Camille Letavernier CLA
Modified: 2013-04-23 08:26 EDT (History)
3 users (show)

See Also:
rschnekenburger: kepler+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Camille Letavernier CLA 2013-02-04 07:55:08 EST
The file browser UI enabling to import model within Papyrus shall implement extension filters (e.g. *.uml).

More generally, Papyrus Widgets for files selection (FileSystem and Workspace) should be extended to support predefined extension filters.
Comment 1 Camille Letavernier CLA 2013-04-15 07:36:00 EDT
The "All" filter (*) must always be available.

The following features require a specific filter:

- Import Package from Workspace ("Import Package from user model"): *.uml, *.profile.uml
- Import stylesheet from Workspace (StylesheetReference#path): *.css
- Apply profile (From workspace): *.profile.uml, *.uml

The following features already have a filter, and rely on a different mechanism:

- Choose an Icon for a Stereotype
- Document Hyperlink

The "Import" and "Apply" from registered Package/Profile do not need an extension filter as they rely on a catalog.
Comment 2 Camille Letavernier CLA 2013-04-23 07:15:54 EDT
Initial contribution in r10937
Comment 3 Camille Letavernier CLA 2013-04-23 07:22:31 EDT
Minor adjustments in r10938
Update CDO contribution in r10939
Comment 4 Camille Letavernier CLA 2013-04-23 08:26:43 EDT
Unless I've forgotten a case, this task is done.