How to Programmatically Add Items to Eclipse's Problems View - eclipse

I'm developing an Eclipse plugin where I need to add custom items to Eclipse's problems view. Custom items under maybe custom categories (for example list a bunch of problems under a category named "security").
I have looked into marker, but these are for file editors. I want to add custom items to the problems view without having to do anything with a source editor. Is that possible? Or do I have to create my own view?
Thanks!

I think you just need to add the problem view to your plug-in.
org.eclipse.ui.views.ProblemView

You can create markers on Folders/Projects. You don't need to have a File to create a marker. The markers can be grouped via the type of Marker in the Problems View

The Problems view only supports displaying markers.
Markers are associated with resources (usually files) but any plugin can create them, they don't have to done by editors.

Related

How to link the selections in Nattable shown in a custom editor view to the sirius property view in eclipse?

I have a question regarding the linkage of the selection made on the nattable in a custom editor view and the sirius property view. Any ideas, how should i go for it, it will be really kind of you if you can highlight the steps in an easy to understand manner, because i have researched a lot on it and nothing is concrete enough to get me started to solve this task.
I am attaching two screenshots describing, what is the nature of the issue i am facing and what i want to implement.
Screenshots>
1. https://imgur.com/bVqfGc4
In the first screenshot, when i click on the element in the model explorer , its properties show up in the sirius properties view, and they should as that is how sirius property view works
2. https://imgur.com/DKsFQBi
In the second screenshot, when i click on any element on the nattable in a custom editor view containing my nattable, the sirius property view does not respond to the selection made on the nattable in that custom editor view.
I want to implement a solution where when i click on any element in the nattable, its properties hsow up in the sirius property view.
Your help and guidance in this regard will be highly appreciated. Thanks in advance.
Best Regards,
Abu
You need to implement and register an ISelectionProvider. NatTable provides currently only row based providers like the RowSelectionProvider or the E4SelectionListener.
The corresponding examples can be found here:
https://github.com/eclipse/nebula.widgets.nattable/blob/master/org.eclipse.nebula.widgets.nattable.examples/src/org/eclipse/nebula/widgets/nattable/examples/_500_Layers/_505_Selection/_5054_SelectionProviderExample.java
https://github.com/eclipse/nebula.widgets.nattable/blob/master/org.eclipse.nebula.widgets.nattable.examples.e4/src/org/eclipse/nebula/widgets/nattable/examples/e4/part/SelectionListenerExample.java

How can I add a custom column menu tab in ag-grid?

Is there a way to add a custom column menu tab with my own favourite icon which on click would render my custom react component?
something like
myColDef.menuTabs: ['generalMenuTab', 'filterMenuTab', 'myCustomMenuTab']
FYI I'm using v12.0.2
What you're after can't be done I'm afraid. The grid supports React components in all sorts of ways (renderers, editors, filters etc), but not via the column menu.
I've updated the docs page to remove the gibberish issue - it'll be fixed properly in the next release, thanks for highlighting this.
This would be helpful to have. In particular for us, we'd like to filter based off row properties, and not row values. Creating our own tab to filter by cell colors that we have assigned with our own set of labels would be useful.
I agree that it would be a nice feature to have. Apparently, there's no quick out-of-the-box solution to do it. The only workaround I see is to implement your own custom Header component which would display any buttons your want.
There you can put a button to open your own custom menu, which you can implement as any regular UI component. It also means you'll need to manually implement all standard menu options that Ag-Grid provides out of the box if you need them.

Eclipse: Add GroupBy Menu to Custom Marker View

I am developing an Eclipse plugin and I have created my own custom marker view for my own custom markers. Now I want to add a GroupBy-menu to the view like the GroupBy-menu of the Eclipse Problems-view where I can group markers by type, location etc. I know that I have to use the markerGrouping of the markerSupport-Extension point but I don't know how it works.

How can I customize partstack header in rcp application

I am trying to customize PartStack header of a view in rcp application. My goal is to customize the coloring of the header and to add date and time to it and hide minimize and maximize buttons. Buttons can be hidden using css but other goals give me hard time. At the moment I am looking to use a custom renderer by overriding some methods in StackRenderer class. Is that a right approach or is there another renderer that I shoud use?
If you don't want the min/max buttons then do not include MinMaxAddon in the Add On list in the Application.e4xmi.
Using a custom renderer for StackRenderer is useful for changing the text of the part tabs items. If you want to put text elsewhere on the part stack line you will probably need to look at the MinMaxAddon to see how it does that.

Showing markers programmatically

Is there a way to (programmatically) make a certain IMarker be shown in the problem view, similar to what happens when the user selects "View in..." from the context menu? I have a wizard which may cause markers to appear, and I would like to make these markers visible in the problem view when the wizard is complete.
You will just have to make your markers to be problems. However there are separate Markers view that shows all the markers.
To show marker you can use MarkerViewUtil.showMarker(..)
Ignoring all good API rules, you could look into the internals of FiltersConfigurationDialog to create a new resource filter in the problems view programmatically. But I repeat: there is no API for creating problems filters and this might then break at any time.