Re: A question about the New Java Project wizard

To get my 2c in before rework happens .. I disagree with consolidating 
the basic/empty with the project from existing sources. We would like 
our users to get through wizards as quickly as possible, and I think 
this distinction in templates is helpful up front.

This allows the user interested in starting a fresh project to start up 
quickly, without having to pause and understand the concept of "Java 
roots" or consider adding source or resource directories. If the user 
creates a empty/basic project and picks a project home that contains 
files, then perhaps we launch into Project from Existing Sources at that 
point if they confirm they indeed are trying to create a new project 
with those sources. The situation I'd like to avoid is that a user ends 
up with a hybrid project - part of their sources, with sample app files.

-ann

cL wrote:

> sure, this sound fine. the spec will get a major update after the 
> usability test results are compiled and analyzed and i will add this 
> to the bits that need to be re-worked.
>
> thanks,
> cL
>
> Petr Jiricka wrote:
>
>> Team,
>>
>> I have one question about creating new Java projects. According to 
>> the UI spec, there will be two wizards: one for new empty/basic 
>> project, and  one for project from existing sources. Well, is this 
>> really necessary ? Couldn't it work if there was just one wizard, 
>> which would decide which root to take, based on whether the home 
>> directory entered by the user already contains sources or not ?
>> The way it is now, the user needs to make the choice, when in fact 
>> the machine could make the choice for her. Another advantage would be 
>> that this would decrease the amount of clutter in the project 
>> selector UI.
>>
>> Thanks
>> Petr
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>