Eclipse Community Forums: Sapphire » Tree-like property editor

Home » Archived » Sapphire » Tree-like property editor

Tree-like property editor [message #1691788]

Thu, 09 April 2015 12:01

Eclipse User

I guess this might be related to the existing request: https://bugs.eclipse.org/bugs/show_bug.cgi?id=373163

I'm trying to figure out what's the best way to present a hierarchical model structure in case I don't want or even can't at all use the Outline master/detail (if I understand correctly, Sapphire doesn't provide any kind a tree presentation except the Outline part).

There are two use-cases in our app I'm now not sure how to handle using Sapphire:
1) Inside a dialog. The UI should be simple and ideally consist of something like a treeview to select an element and a detail section to provide specific options for such element.
2) Inside an editor. The model is quite complex and the Outline thing is already used for - let's say - a different part of it. I still need to be able to view a group of arbitrary elements with its children inside a detail node.

What's the best way to do this in Sapphire?

[Updated on: Thu, 09 April 2015 12:02] by Moderator

Re: Tree-like property editor [message #1691798 is a reply to message #1691788]

Thu, 09 April 2015 13:21

Eclipse User

Sapphire does not currently include a tree property editor. Note that the adopter can implement a custom property editor where needed and plug it into the overall Sapphire UI.

Re: Tree-like property editor [message #1691846 is a reply to message #1691798]

Fri, 10 April 2015 02:52

Eclipse User

Ok, thanks! Do you think it's possible to make a generally usable tree property editor or should I stick with one or more model-specific implementations? Could you share a little more about the design decision to omit the tree editor in Sapphire? I'm just thinking about possible issues I may face.

Re: Tree-like property editor [message #1691951 is a reply to message #1691846]

Fri, 10 April 2015 13:28

Eclipse User

A tree property editor doesn't exist primarily because there wasn't a strong enough need for one to drive development. It would be a very complicated property editor, if it is to cover a variety of usecases. A custom property editor for a specific model and requirements would be much simpler.

Previous Topic:	Loss of data when changing detail part too quickly
Next Topic:	"DateTimeBrowseActionHandler" is not a valid Java type name

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Sep 07 01:08:57 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter