In the Eclipse Problems view, is there a way to add additional column (i.e Justify)?
My motive is to add additional problems marker attribute, in which I should be able to add a justification to the intentionally created problems which will be displayed in this additional column.
It looks like you can do this by using the org.eclipse.ui.ide.markerSupport extension point to define a new markerField, which will correspond to a new column in the Problems View.
Related
I created a new extension "lecturers" with the TYPO3 Extension Builder (v.10.0.1).
As default actions, I added list, show and create. After creating the extension, I did not modify any of the files except the list template.
Usually, I add new data within the BE, as it can be seen in the image:
But when I open the list view, no data is shown. Also, the repository is empty (<f:debug>{lecturers}</f:debug>.
However, when I added a record within the create view, the repository as well as the list view includes that one record.
Does anyone know which lines of code I am missing, to include the BE records in my repository as well? Thank you for your help!
After removing the setting of persistence in the generated folder TypoScript/setup.typoscript it worked
I am currently using keystoneJS for a project and I have a requirement to allow admins to add additional fields for each deliverable.
I managed to find textarray, which allows me to add a single line of text but I would need something closer to adding textfields as i would need to add paragraphs of text.
Any advise/direction to extending the functionality or is it not possible?
FYI: I also tried using these two resources to no avail, perhaps due to a lack of knowledge on my end.
- https://github.com/keystonejs/keystone/wiki/Create-a-custom-field-type-for-app-development
- https://gist.github.com/JedWatson/8519769
EDIT: i wasnt able to figure out in detail, but changing the arrayfield in mixin to multiline met my use case. Now trying to include two fields in one add.
I created a hippo documenttype using a one column layout. For rendering purposes I would like to reorganize the given items into a two-columns layout.
However, no option is available to do this change, at least not by using the latest hippo cms community version.
I have already searched in google and found following information, saying that it may be possible to change the layout by using the console, but no information about how:
http://hippo.2275632.n2.nabble.com/How-to-delete-or-rename-document-types-td7579269.html
I would appreciate any hints about it.
AFAIK there is no documentation on how to do this: this is not very complicated but this is a tedious process. If you still can - for instance your document type is not used yet - I would advise to simply drop it and recreate the content type. That being said, here is how it works:
look into your project namespace in the console: the path is something like this: /hippo:namespaces/YOURPROJECT/document-type/editor:templates/_default_/root
the root nodes defines the layout. Check out the plugin.class: for a one column this will be org.hippoecm.frontend.service.render.ListViewPlugin and for a 2 column layout the plugin.class will be org.hippoecm.frontend.editor.layout.TwoColumn
for every field in your document type (that's the tedious part) you will need to define if the field placed on the right or the left.
this is configured on the node with the name of the field path, as a property wicket.id that for instance have the value ${cluster.id}.left.item. This means the item will be placed on the left side.
Your best bet is to create a 2 column example document type and look carefully at its configuration and replicate the changes in your existing field.
Have you tried the instructions on the link below ?
http://www.onehippo.org/library/concepts/document-types/custom-editor-layout.html
I want to create my own module which is an extension of sale.order. I want to have a form view which is like sale order view with few additional fields,
My problem is that when I inherit the sale order view and add say three extra fields these fields comes by default in the Original Sale Order form view too.
is this the default behaviour or am I doing something wrong ?
What should I do to achieve what I want.
If you inherit the view and add some fields using 'xpath' , than it will change the original view by installing your new module. This is the application of view inheritance. If you want to keep the original form view as it is after the installation of your module and want to define another which have some extra fields only for your customized module, you have to make a different form view without inheriting the original one. May be in future , there will be a facility of extending an existing form view, but right now you can't do that.
I think you need to check view_id in your code may be a view_id is common so you are updating a default view of sale order.
When you are inherit one view of sale order a functionality will be added in a form not whole view will be generated.
Still this is not solution send me your code i will review it.
I am trying to create a tabbed property view as per given article : The Eclipse Tabbed Properties View
As per article, org.eclipse.ui.views.properties.tabbed.propertyTabs extension point can be used to add new tabs.
<extension point="org.eclipse.ui.views.properties.tabbed.propertyTabs">
<propertyTabs contributorId="mview.views.SampleView">
<propertyTab
category="sample"
id="mview.ButtonTab"
label="Button"/>
<propertyTab
afterTab="mview.ButtonTab"
category="sample"
id="mview.AdvancedTab"
label="Advanced"/>
</propertyTabs>
</extension>
However in my case the tabs of property view vary depending on the item selected in view. So I have to add the tabs dynamically into extension depening on the item selected.
Please suggest how to do so.
Update:
One of the way to do so (I am not sure if its adviced) is using IExtensionRegistry.addContribution() method. Here I provided an inputstream object containing desired extension details. This added tabs to property view at run time. However with change in selection of item in list viewer, the property view is not updated. Please suggest if this is the right approach to do so.
Ok, I got the solution Its a two step process. Using this one can dyanamically add tabs (and their sections):
Step 1: Associate a tab descriptor provider with the view.
Add an extension point - org.eclipse.ui.views.properties.tabbed.propertyContributor to the view (if not already added). In the propertyContributor section, add a class for tabDescriptorProvider item. This class will implement ITabDescriptorProvider interface.
Step 2: Provide Tabs and Sections:
TabDescriptor provider will return array of TabDescriptors when its getTabDescriptor() method is called. Each TabDescriptor return a list of SectionDecriptors and each SectionDescriptor is linked to a Section. Finally it is the Section class that contains widgets to be displayed on screen. Each widget in Section class has a modify listner which updates the properties of selected items.
While the answer from Viral may not match the specific needs of the OP, the provided answer is likely acceptable to many.
If a tab does not have any sections to display, the default TabbedPropertySheetPage will not show that tab. Thus, if the problem domain is specified in terms of IFilter implementing classes, "dynamic" tabs may be achieved.
Tabs will be added or be removed as the selection changes depending upon whether any sections are present. A visible tab may have one or more sections present on it, and the number of sections on a visible tab may change from selection to selection.
As I came across this page with the same basic issue, I was a bit disappointed that I would need to intervene in the way the OP suggested. After some experimentation, I was able to achieve what I needed purely through the IFilter approach as suggested by Viral.
A tutorial is provided at http://www.eclipse.org/articles/Article-Tabbed-Properties/tabbed_properties_view.html
You need to define a new YourPropertySection derived fromAbstract PropertySection . Also define a filter derived from IFilter and override the select method to return true only for the desired type of selection. Then in plugin.xml write an extension point which would map your PropertySection to the required PropertyTab and will also associate your filter. So this section & tab will only show when your filter returns true.