Community
Participate
Working Groups
For the property view, it will be nice to have a custom editor at the root node other than the child nodes. There is a way to create custom editor for child node, such as checkbox (image) and combo-box already, but why not allowing custom control at the parent nodes as well. Not sure if this is already implemented for 3.2+, I am using 3.2 and I have added this capability in the proerty view to my local copy of eclipse.
Created attachment 66769 [details] patch this is how you use it. Create a container and add the descriptor info to the container and than set the input of the viewer with the container object. Each text descriptor, checkbox descriptor, and textbox descriptor are custom descriptor, with lable provider and cell editor implemented. ----------- PropertyContainer container = new PropertyContainer(); PropertyContainer nestedTextContainer = new PropertyContainer("foo"); nestedTextContainer.addDescriptorInfo(new PropertyDescriptorInfo(new ComboBoxPropertyDescriptor("nestedText_ComboBoxID", "comboBox", new String[] {"first", "second", "third"}), 0)); nestedTextContainer.addDescriptorInfo(new PropertyDescriptorInfo(new CheckBoxPropertyDescriptor("nestedText_CheckBoxID", "checkBox"), Boolean.TRUE)); nestedTextContainer.addDescriptorInfo(new PropertyDescriptorInfo(new TextPropertyDescriptor("nestedText_TextID", "text"), "myText")); container.addDescriptorInfo(new PropertyDescriptorInfo(new TextPropertyDescriptor("nestedTextContainerID", "nested text container"), nestedTextContainer));
Created attachment 66770 [details] screen capture of result
Assuming nothing was done about this for 3.4. Clearing target milestone.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
