[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [wtp-dev] Why Do We Need the Preference to Enable Multiple Modules per Project?
|
On 7/7/05, Arthur Ryman <ryman@xxxxxxxxxx> wrote:
>
> While using WTP to develop some Web apps, I ran into a feature of our UI
> that I find problematic, and I'd like to hear from other people about why we
> need this feature.
>
> The feature is the Flexible Project Preference. The user now has to
> explicity check a box to enable multiple modules per project.
>
> I find this problematic for several reasons:
>
> 1. It caused a usability problem. I created a project with a Web module in
> an earlier build of WTP and then worked on it with a later build which has
> this preference disabled. It caused the Web service wizard to fail [1]. This
> will be corrected, but it pointed out to me that this preference is causing
> bimodal behavior. Our code in now more complex than it needs to be and there
> is more potential for bugs and usability problems.
>
> 2. We went to a lot a development effort to upgrade the code base to allow
> multiple modules per project. This should be the WTP norm. We should promote
> this feature and improve our UI to make it very easy for users. Disabling it
> seems like a step backwards and an admission of failure.
>
[snip]...
Shouldn't this be posted to the general WTP newsgroup to get some
feedback from users who may not be following the dev mailing list?
- Rob Sanheim
--
http://www.robsanheim.com/
