Bug 354485

Description Will Smythe 2011-08-11 09:11:09 EDT

Build Identifier: 

As part of the "Web client  xx" EGL project template, we allow the developer to select a widget library/version when a project is created (these widget libraries are contributed via extension points, and others can contribute their own widget libraries that will appear in this dialog). However, once the project is created, it becomes very difficult for the developer to switch to a different widget library (if the library does not already exist as a project in the workspace) and/or to switch to a different version of the same library. Assuming we support the concept of a library version (see Bug 351279), we should make it easy for the developer to choose different library(ies) for a project that has already been created.

Here's what I am thinking in terms of flow:

1. Developer creates a new "Web client with services" project and selects 1 or more widget libraries to include (by include, this means importing the widget library project into the workspace if needed and setting the build path appropriately for the new project)

2. Developer upgrades to a later version of EDT (e.g. 0.8) that includes newer versions of the previously selected libraries.

3. Developer right-clicks on the previously created project, selects Properties, and then selects RUI Wdiget Library (this is new properties page).

4. A table (comparable to the same panel displayed when the project was created) is displayed, showing all registered widget libraries in the IDE. Checkboxes appear next to the widget libraries already in the direct build path of the project. 

5. Developer selects a different version for a widget library already associated with the project (e.g. developer chooses EGL Dojo 0.8)

6. Developer clicks OK.

7. The selected widget library project is imported into the workspace (if it does not already exist) and the project's build path is updated appropriately.

In order for a developer today to use a later version of a widget library, he/she must create a dummy project which brings this project into the workspace. This proposed functionality would save the developer from creating a "dummy" project in order to get the latest Dojo widget library (for example) into the workspace. It also makes it a lot easier to add additional libraries to a project (i.e. add the widget library into the build path of the project) that may get contributed to the IDE via third-party plug-ins.

Although this does not completely replace the need to configure the build, it does provide an alternative way to configure which widgets are available to a RUI project.

Reproducible: Always