create a popup / dialog composite on eclipse startup - eclipse

I want to display a popup on eclipse startup without clicking any button.
I have a plugin class which implements org.eclipse.ui.IStartup but from there i dont know how to create a popup which can be launched as soon as eclipse launches. Condition is popup should be shown without clicking anywhere, but just on the eclipse launch.

Related

Open eclipse view along with custom editor in PDE

I have created a custom eclipse editor and want a view to be opened in the event the editor is active. If the view is already open then nothing should be done. I also want this functionality for the console in that the console should be open in the event my custom editor is active. Is this possible to do in Eclipse plugin development environment?
You can open the view in the init method of your editor using something like:
IWorkbenchPage page = PlatformUI.getWorkbench().getActiveWorkbenchWindow().getActivePage();
page.showView("org.eclipse.ui.console.ConsoleView");
This will open the view if it is not open or make it the active view if it is already open.

How to programmatically (or via eclipse plugin.xml) enable context menu which is disabled by eclipse IDE?

In CDT, How can I programmatically (or via eclipse plugin.xml) enable the context menu of a project "Build Project" when It is right clicked. So that I can make the Build Action enabled in order to solve this problem.
Please Check this forum link for more information:
https://www.eclipse.org/forums/index.php/m/1709440/#msg_1709440
I have tried MenuManager but it returns the top menu? I want to access the pop-up menu when it is right clicked on a project.
What I experienced so far is I can programatically get the flow of program when I right-click a project via CommonActionProvider by defining a class at org.eclipse.ui.navigator.navigatorContent at plugin.xml under which I have a defined actionProvider. Now at this ActionProvider I can halt at debug when I right click the project first at setContext method via ActionContext parameter. And this is the point where I want to get access to the right-click menu of selection.
I can acess the selection I get it from context at this point and because I right-clicked at it the context menu will hapen but how I get the access to this right click menu programatically ? When I right click the project after selecting it via control button I get now the access to method fillContextMenu with parameter IMenuManager menu but the bug is not at this part so I dont need to do anything at this method. I need the access to right click menu when I right click an unselected project (via holding control button). Any idea?
I solved the bug via an actionProvider (enablement for a instanceof IProject.) Here in the class that I extended from CommonActionProvider at the method setContext I got the command via commandService and getCommand method. Then calling buildCommand.isEnabled(); solved the bug.

Eclipse RCP - remove command from the popup

I am working on a tool (which is built over Eclipse). In that there is a popup menu called "Edit Properties" if a object is right clicked. I need to hide this menu command. Provided that it should not be gets hided from the standard menu, should only be hide from the popup.
How to do this? Can anyone suggest me?

The Eclipse "select workspace" dialog disappears when I switch to a different virtual desktop (VirtuaWin) - how to restore it?

When eclipse starts up, it first show its splash screen and then pops up a dialog for selecting the desired workspace to open. If at this point I switch to a different virtual desktop and then come back later, only the splash screen is visible but the dialog is gone and I haven't found a way to get it back. I have to kill the eclipse process and start again.
Is there a way to recover from that problem whithout killing eclipse?
My setup:
Windows XP
VirtualWin 4.0.1
Eclipse Helios
I'm not sure why it prompts you the first time Eclipse starts up but not after using a different virtual desktop. I assume you did not select "Use this as the default and do not ask again" on the "select workspace" dialog. If you don't mind waiting a bit, you can avoid killing Eclipse by loading the current workspace and then going to File > Switch Workspace.
Start Eclipse.
Invoke Window menu on Workspace Launcher window. For example by clicking the middle mouse button on the window title bar, see Setup Dialog's Enable middle button window menu activation setting in VirtuaWin Help.
Click Add Window Rule.
Leave class name there e.g.: #32770.
Erase Window name and Process name.
Select Always manage windows of this type.
Click Add button.

How to create default debug and run configuration in Eclipse?

Whenever I hit Debug or Run in Eclipse, I get a dialog asking me what configuration I want to use.
How do I set a default configuration and bind a keyboard shortcut?
Maybe this article from Eclipse One Tips will help you:
How to run the last launched application
The answer lies in a preference hidden on the Run/Debug page:
Go to Window > Preferences > Run/Debug > Launching.
Select the option Always launch the previously launched application. It’s located at the bottom of the dialog.
The preference should look something like this:
Now you’re free to press
F11, Ctrl+F11 or click the Run/Debug
icons on the toolbar with confidence, knowing it’s going to run what
you expect it to run.
One question arises: How do you quickly run a class as a specific
application (eg. a JUnit test) if you can’t press F11 to
run it? You have some options available:
The fastest way is to use keyboard shortcuts. Eclipse allows you to launch classes using a keystroke, including JUnit tests, Java
applications, etc using Alt+Shift+X.
Alternatively, right-click on the class and select Run As. The submenu will show available options for launching the class.
Lastly, you could click the pulldown arrow on the run/debug icons in the toolbar and select Run As. The submenu once again shows
available options for launching the class.
Eclipse plug-ins that add new project types may contribute 'Launch Configurations' to control how Eclipse executes the application. For example, J2EE based projects need to publish content and start the application server. Contrast this with simply starting a JVM for a regular Java application.
When you select a configuration, Eclipse records this for future use. You can access these by selecting the 'Run/Run Configurations' menu item or selecting 'Run Configurations' from the little drop down menu next to the run and debug toolbar buttons. You can also add new launch configurations through the Run/Debug Configurations dialog that opens. In this dialog, you should see one or more configurations that you previously launched. Selecting one reveals all the info Eclipse uses to launch your application. One tab called 'Common' contains options for controlling the your favorites menu. Checking the box next to Run or Debug will add this launch configuration to the top of its corresponding menu.
If you only have a single configuration in your menu then Eclipse will launch it when you click the associated button. If you have more than one then Eclipse launches (sometimes) the most recently used. I say sometimes because, occasionally, one launch configuration causes another to launch, which cause the last used configuration to be the second one when you would expect it to be the first one. Usually this happens to me when I launch an application, which needs to be built and the build launches a tool. When this happens, just select the correct launch configuration from the drop down menu.
You can bind a keystroke combination to the Run and Debug commands through the 'Windows/Preferences' menu item. Then select 'General/Keys' in the tree control on the left.