[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-dev] Please help me stop the context menu abuse
|
We currently don't have a good story for adding/removing natures (and
additional stuff like builders and builder-specific configuration files,
.classpath, ...).
Please see and vote for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=102527 .
If we urge others to move their actions into the Project menu, then we
should also move the 'PDE Tools > Convert Projects to Plug-in Projects...'
action.
Markus
"Max Rydahl Andersen" <max.andersen@xxxxxxxxxx>
Sent by: eclipse-dev-bounces@xxxxxxxxxxx
2008-05-09 09:57
Please respond to
"General development mailing list of the Eclipse project."
<eclipse-dev@xxxxxxxxxxx>
To
"wtp-dev@xxxxxxxxxxx" <wtp-dev@xxxxxxxxxxx>
cc
"General Dali EJB ORM developer discussion." <dali-dev@xxxxxxxxxxx>,
"General development mailing list of the Eclipse project."
<eclipse-dev@xxxxxxxxxxx>
Subject
[eclipse-dev] Please help me stop the context menu abuse
Hi,
I just opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=231257 and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=231258 against
WebTools and Dali.
It is about them adding "project enablement" menu items to the context
menu. This should be banned by law! :)
I know it is late in the game, but I honestly believe it is important we
try and stop the "random adding" to the context menu.
In JBoss Tools we have done these things by instead putting them under
Properties but I realize that just moves the issue to the profileration of
project properties.
So I actually did not have a better suggestion until today where I
realized that Eclipse has this nice "Project" menu which fits perfectly
for these kind of operations and we actually already have "Convert to a
dynamic web project..." in there.
I suggest that we push for getting such "project enablement" items moved
to that menu instead and maybe even create a "Enable >" sub menu under it.
WDYT ? If this is the wrong list to push this then please let me know
where else to push to get this into Eclipse 3.4 and not wait another
year... ;)
/max
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev
