[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [wtp-dev] Please vote: "project feature" name
- From: "Konstantin Komissarchik" <kosta@xxxxxxx>
- Date: Tue, 20 Sep 2005 15:30:06 -0700
- Delivered-to: email@example.com
- Thread-index: AcW+KiZt1MhS75YHSCiEQIfqzisKowABxJyw
- Thread-topic: [wtp-dev] Please vote: "project feature" name
As you vote consider both the perspective of the end user as well as the
perspective of a plugin developer. Despite Ted's comment, having a
different term for the ui from the one that's used in the api is
unlikely to happen since that would create even more confusion. I would
assume that the term that you are voting for will be used in both
Having said that, consider whether the term will convey an intuitive
meaning to someone who has never used wtp/eclipse before. Try using it
in a sentence such as "Please select <term>s to install." or "<term>
Struts 1.0 depends on <term> Web Module 2.4."
From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ted Bashor
Sent: Tuesday, September 20, 2005 2:28 PM
Subject: [wtp-dev] Please vote: "project feature" name
Well it's primary day here in Washington State, and to share that
democratic vibe, we're asking you to vote on your favorite class name
for use in the "project features" api.
If you haven't already, please take a look at the spec
as well as
and maybe even peruse and run the org.eclipse.wst.common.features.*
plugins in in WTP's CVS common component repository.
The candidate list is:
A couple points:
1) this is a vote for the api name for these things, the UI name
*could* end up being different.
2) "Feature" and "Capability" are terms already used by the Eclipse
platform, so voting for them means that you think the project qualifier
is sufficient to avoid confusion.
Please send me ( tbashor@xxxxxxx ) your three favorites listed in
preference order. Your first choice gets 3 votes, the second gets 2,
and the last gets 1 vote. Voting is open for the next 24 hours.
wtp-dev mailing list