Bug 468707 - Refactor GEF4 Cloudio, consider splitting SWT-, JFace-, and UI-related code into own modules/bundles.
Summary: Refactor GEF4 Cloudio, consider splitting SWT-, JFace-, and UI-related code i...
Status: NEW
Alias: None
Product: GEF
Classification: Tools
Component: GEF Cloudio (show other bugs)
Version: 0.1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: gef-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 473693 473695
Blocks: 470635
  Show dependency tree
 
Reported: 2015-05-28 15:42 EDT by Alexander Nyßen CLA
Modified: 2016-05-29 06:45 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Nyßen CLA 2015-05-28 15:42:53 EDT
The currently exposed API of GEF4 Cloudio does not seem to be very concise. The distribution of classes to the respective packages does not seem to be reasonable and some classes should probably remain internal.
Comment 1 Alexander Nyßen CLA 2015-06-20 00:28:13 EDT
Furthermore, based on what is discussed in #470635, it could make sense to split GEF4 Cloudio into the following modules/bundles:

org.eclipse.gef4.cloudio (core parts, i.e. abstractions like Word, etc.)
org.eclipse.gef4.cloudio.swt (TagCloud widget and related implementations)
org.eclipse.gef4.cloudio.jface (TagCloudViewer and related implementations)
org.eclipse.gef4.cloudio.ui (TagCloudView and related implementations)

The org.eclipse.gef4.cloudio.examples.ui could be split accordingly.
Comment 2 Alexander Nyßen CLA 2015-07-27 16:47:34 EDT
Added dependencies to bug #473693 and bug #473695, which should be addressed before the actual refactoring.
Comment 3 Alexander Nyßen CLA 2016-01-26 15:13:54 EST
As Word is dependent on SWT as well, it would probably not make sense to factor out a org.eclipse.gef4.cloudio bundle.