[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[wtp-dev] FW: WTP and usability
|
Here is some usability feedback from Wayne Beaton of The Eclipse
Foundation comparing Eclipse/WTP and NetBeans. I opened enhancement
requests for each of the points that he makes.
Do we need separate "Static" and "Dynamic" web project wizards?
https://bugs.eclipse.org/bugs/show_bug.cgi?id=173901
Should we create a bundle that includes WTP and Tomcat?
https://bugs.eclipse.org/bugs/show_bug.cgi?id=173923
Xdoclet library setup usability issues
https://bugs.eclipse.org/bugs/show_bug.cgi?id=173925
Provide a graphical editor for web.xml and application.xml
https://bugs.eclipse.org/bugs/show_bug.cgi?id=173924
- Konstantin
-----Original Message-----
From: Wayne Beaton [mailto:wayne@xxxxxxxxxxx]
Sent: Friday, February 09, 2007 3:34 PM
To: mike.milinkovich@xxxxxxxxxxx; 'Ian Skerrett'; 'Wayne Beaton'; 'Ralph
Mueller'; 'Bjorn Freeman-Benson'; donald.smith@xxxxxxxxxxx; 'Jochen
Krause'; Jess Garms
Subject: RE: WTP and usability
NetBeans' UI has some bizarre-ness to it as well.
Here are some thoughts about WST:
I've always found it annoying that--when a create a 'web' project--I
have to
choose between a "static web project" and a "dynamic" one. Is the
distinction really necessary?
This is more of a packaging issue, but I often hear of frustrations that
Eclipse doesn't ship an application server. Recommendation: bundle
Tomcat.
It might be cooler to bundle some of the server-side Equinox stuff...
If you choose to use Xdoclet, you need to download an install it.
However,
this not made clear to the user. It'd be handy if it was either bundled
or
if there was some mechanism to go and get it. At very least, some
guidance
from the UI to tell you that you need to do this.
NetBeans has a web.xml editor. Frankly, I think it's terrible, but it's
better than editing straight XML (especially if the file starts to get
large). I think Eclipse would benefit from having even a simple web.xml
file
editor. The package explorer displays servlet mappings and such, but
provides nothing for editing them or adding to them (short of defining
them
using Xdoclet or editing the web.xml file directly). I realize that
having
an editor and annotation processing support can result in some
weirdness...
Bug 152355 has to go away. Even though it's not our/your fault.
That's what I have for now. Next week, I'll go through a full exercise
of
building/deploying a Java EE application with servlets, JSPs, EJBs, and
Web
Services and should have more to report.
Wayne
--
Wayne Beaton
The Eclipse Foundation
wayne.beaton@xxxxxxxxxxx
http://www.eclipse.org
http://wbeaton.blogspot.com/
http://www.planeteclipse.org/planet/
> -----Original Message-----
> From: Mike Milinkovich [mailto:mike.milinkovich@xxxxxxxxxxx]
> Sent: February 7, 2007 3:59 PM
> To: 'Ian Skerrett'; Wayne Beaton; 'Ralph Mueller'; 'Bjorn
> Freeman-Benson'; donald.smith@xxxxxxxxxxx; Jochen Krause
> Subject: FW: WTP and usability
>
> If you could please take a few moments out of your busy day
> to give me a couple of pointers on this topic, I would appreciate it.
>
>
>
> Mike Milinkovich
>
> Office: +1.613.224.9461 x228
>
> Mobile: +1.613.220.3223
>
> mike.milinkovich@xxxxxxxxxxx
>
>
>
> From: Jess Garms [mailto:jgarms@xxxxxxx]
> Sent: Wednesday, February 07, 2007 1:53 PM
> To: Mike Milinkovich
> Subject: WTP and usability
>
>
>
> Mike - during our discussion last week you mentioned WTP's
> usability as really hurting Eclipse in comparisons against
> Netbeans. I've certainly run across some of WTP's UI
> problems, but would like to know if you have any specific
> gripes, or if you've run across websites or blogs that call
> out some of these problems.
>
>
>
> Thanks,
>
> Jess
>
> ______________________________________________________________
> _________
> Notice: This email message, together with any attachments,
> may contain information of BEA Systems, Inc., its
> subsidiaries and affiliated entities, that may be
> confidential, proprietary, copyrighted and/or legally
> privileged, and is intended solely for the use of the
> individual or entity named in this message. If you are not
> the intended recipient, and have received this message in
> error, please immediately return this by email and then delete it.
>
