cornercorner
FeaturesPluginsDocs & SupportCommunityPartners

MergeFromScratchAndFromExistingSourcesNewProjectWizards

Revision as of 13:24, 5 November 2009 by Admin (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

Merge "from scratch" and "from existing sources" New Project Wizards

Having two wizards for creating one project type can be confusing for user. The only difference between those two wizards is that one is used when user already has some source files.

Current "from scratch" wizard panel

Use Case:

  • The project doesn't exist
  • User provides Project Name and Project Location path
  • Project folder is created as Project Location + Project Name
  • There is no conflict of build script name

Wizard Panel:

Image:JavaProject_MergeFromScratchAndFromExistingSourcesNewProjectWizards.png

Current "from existing sources" wizard panel

Use Case:

  • Some project with sources already exists
  • User provides Project Name and possibly already existing Project Folder
  • No folder is created by the wizard - project metadata are stored in provided folder
  • There might be conflict of build script name, because default build.xml might exists in provided folder - user needs to provide own build script name

Wizard Panel:

Image:JavaProjectWithExSrc_MergeFromScratchAndFromExistingSourcesNewProjectWizards.png

Solution - merging panels together

Solution 1 - all together

One solution where all UI elements were simply put together is shown on next figure:

Image:JavaProjectV1_MergeFromScratchAndFromExistingSourcesNewProjectWizards.png

Drawbacks: Text fields "Project Location" and "Project Folder" are kind of redundant and they both in fact modify one path to place where project metadata will be stored. Setting Project Location and Project Folder can be very confusing - both are editable and user might think that both needs to be set.

Solution 2 - no project location - This solution seems to be preferred

The other solution is shown on next figure where in fact UI copies the "from existing sources" wizard panel.

Image:JavaProjectV2_MergeFromScratchAndFromExistingSourcesNewProjectWizards.png

Drawbacks: User has to provide Project Folder path on the place where he was used (for couple of years) to provide Project Location - it can lead to project metadata stored on places where actually project folder should be created (personal experience!) and possibly to other project metadata corruption.

Filechooser dialog that would be opened to pick Project Folder in this case will look like the following figure:

Image:ProjectChooser_MergeFromScratchAndFromExistingSourcesNewProjectWizards.jpg

"Append Project Name" checkbox will allow users to decide if they want to pick already existing project folder or new project folder will be created with name of the project.

Solution 3 - either project location or project folder

This solution allows either to set project location or project folder (the other UI is disabled). When Project Location is selected then project folder will be created as Project Location + Project Name.

Image:JavaProjectV3_MergeFromScratchAndFromExistingSourcesNewProjectWizards.png

Drawbacks: User needs to select by checking radio button what he would provide.

Open Questions

  • Does the Build Script Name text field needs to be provided always or only when such colliding script name is found?

All project types that have "from existing sources" project templates:

Java

  • Java Project with Existing Sources

Web

  • Web Application with Existing Sources

Entreprise

  • Entreprise Application with Existing Sources
  • EJB Module with Existing Sources
  • Entreprose Application Client with Existing Sources

Mobility

  • Mobile Project from Existing MIDP Sources

Ruby

  • Ruby Application with Existing Sources
  • Ruby on Rails Application with Existing Sources

C/C++

  • C/C++ Project from Existing Code