[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cross-project-issues-dev] Europa impressions (screenshots)
|
Thank you all for the suggestions. I've created two
bugzilla entries to capture the discussion and we'll discuss on the Monkey
mailing list to see what options we can pursue. Further discussion on the bug
entries is appreciated.
Best,
Ingo
I think the scripting support would
fit nicely into the "Run" menu, rather than a separate top level menu.
Here is an example of an extension declaration from the
org.eclipse.ui.externaltools plugin, which also makes contributions to the run
menu for Ant and other external scripting tools. I suggest defining a similar
menu group within the run method for scripting, and place the scripting actions
there: <extension point="org.eclipse.ui.actionSets"> - <actionSet label="%ActionSet.externalTools" visible="true" id="org.eclipse.ui.externaltools.ExternalToolsSet"> -
<menu
label="%Menu.run" path="additions" id="org.eclipse.ui.run">
<separator name="ExternalToolsGroup"
/> </menu> <action definitionId="org.eclipse.ui.externalTools.commands.OpenExternalToolsConfigurations" label="%ActionDefinition.openExternalToolsConfigurations.name" class="org.eclipse.ui.externaltools.internal.menu.OpenExternalToolsConfigurations" id="org.eclipse.ui.externaltools.OpenExternalToolsConfigurations" />
</actionSet>
</extension> -John
"Ingo Muschenetz"
<ingo@xxxxxxxxxx> Sent
by: cross-project-issues-dev-bounces@xxxxxxxxxxx
06/01/2007 01:42 PM
Please respond
to Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx> |
|
To
| "Cross project issues"
<cross-project-issues-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [cross-project-issues-dev]
Europa impressions (screenshots) |
|
Hi All, We use the early startup infrastructure enable
users to run scripts on startup so that they can configure the workspace. This
is something we use in our own scripts, so it is a useful feature. With regards
to the Monkey top-level menu, we use that as a convenient place to allow people
to access scripts they have run, since they may be triggered via key commands.
These actions do not generally do the same things a "New" or "Import" wizard
would do, so placing them there would likely be more confusing than helpful. One
idea we've had is to contribute scripts to existing menus and toolbars, but
there isn't an obvious place to relocate the scripts menu wholesale.
Other
suggestions are appreciated. Our plugins are quite small, so the hope is that
our contribution to startup times would be negligible, but we will check to make
sure. Best, Ingo
From:
cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Boris
Bokowski
Sent: Friday, June 01, 2007 9:47 AM
To: Cross
project issues
Subject: Re: [cross-project-issues-dev] Europa
impressions (screenshots)
Interesting. I see that Buckminster and Monkey still contribute a
top-level menu for every perspective, with only a few items. There must be
a better place for you to place your actions, don't you think? For example, in
the case of Eclipse Monkey, have you considered using the New or Import wizard
infrastructure?
Also, for those who register early startup runnables:
Why do you have to do this eagerly? You are causing unnecessary long
startup times.
Boris
On 6/1/07, Pascal
Rapicault <Pascal_Rapicault@xxxxxxxxxx>
wrote:
(See attached file: europa resource
perspective.JPG)(See attached file:
early
startup.JPG)
_______________________________________________
cross-project-issues-dev
mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev
mailing
list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev