search

eclipse-qvto / org.eclipse.qvto

Eclipse Public License 2.0
0 stars 0 forks source link

Improve wizard visibility #211

Open eclipse-qvt-oml-bot opened 3 days ago

eclipse-qvt-oml-bot commented 3 days ago

| --- | --- | | Bugzilla Link | 245108 | | Status | NEW | | Importance | P3 enhancement | | Reported | Aug 25, 2008 08:27 EDT | | Modified | Aug 26, 2008 10:18 EDT | | Reporter | Richard Gronback |

Description

I'm creating a 'DSL Toolkit' for Amalgam and ran into an old problem. I have defined a set of capabilities to hide the standard Modeling project wizards in order to reorganize/rename them in a more consistent manner, but cannot redefine the QVT wizards as the main wizard classes are internal. Some options here are:

  1. Expose wizards as public API
  2. Declare the org.eclipse.amalgam.dsltk.ui plug-in as a friend
  3. Create a small public (API) main wizard class for QVTO that can be used for such cases as mine
  4. Copy the internal wizard and supporting classes to Amalgam and maintain in parallel

After some discussion, it seems starting with 2 and moving toward 3 is the approach we will take.

eclipse-qvt-oml-bot commented 3 days ago

By Richard Gronback on Aug 26, 2008 10:18

Actually, taking a look at org.eclipse.m2m.qvt.oml.ui's exported packages, all the internal packages are already exported. This allows me to invoke the wizards, but we should move toward not exporting these packages in the future, and providing the proper wizard API as discussed. In the meantime, leaving as-is and not declaring amalgam.ui as a friend seems fine, to me.