[Issue 2] New - Deployment

[ryahn@tigris.org]

http://mrsg.tigris.org/issues/show_bug.cgi?id=2
                  Issue #:|2
                  Summary:|Deployment
                Component:|mrsg
                  Version:|current
                 Platform:|All
               OS/Version:|All
                      URL:|
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|FEATURE
                 Priority:|P3
             Subcomponent:|editor
              Assigned to:|ses
              Reported by:|ryahn






------- Additional comments from ryahn@tigris.org Fri Sep 17 17:34:44 -0700 2004 -------
Currently, the deployment of the GXL plug-in, through an update site, adds
this plug-in to the native Eclipse editor, rather than adding the plug-in as a
perspective.  Deploying the plug-in in this manner creates several problems.
  First, this plug-in provides action buttons, specific to the GXL Editor, to
the native Eclipse toolbar.  If other plug-ins deployed in the same manner, it
would lead to overcrowding of the Eclipse toolbar.  This issue could be resolved
by removing the action buttons.  However, user functionality may be lost.
  Second, the GXL editor adds a GXL Menu to the native Eclipse Menu bar.  Again,
other plug-ins deploying in the same manner could overcrowd the Menu bar. 
Similarly, the GXL Menu could be removed, but user functionality may be lost.
  Finally, to remove the plug-in from Eclipse, the user must uninstall or
disable the plug-in.  If, by mistake, the user reverts back to a previous state
rather than uninstalling or disabling the plug-in, Eclipse will have to be
completely removed and reinstalled before the plug-in can be reinstalled.
  The appropriate solution to this issue is to deploy the GXL plug-in as a
perspective rather than an add-in, allowing the user to open or close the
perspective without disabling or uninstalling the plug-in from the platform.