Bug 243452 - Zest: creating custom GraphNode's directly by content provider
Summary: Zest: creating custom GraphNode's directly by content provider
Status: NEW
Alias: None
Product: GEF
Classification: Tools
Component: GEF-Legacy Zest (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: gef-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-07 12:21 EDT by marco CLA
Modified: 2015-01-22 02:43 EST (History)
5 users (show)

See Also:
irbull: iplog+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description marco CLA 2008-08-07 12:21:58 EDT 
Build ID: I20080617-2000

Zest use a ContentProvider to make GraphNode objects from business-model objects. (see the internal and "only-package-visible" org.eclipse.zest.core.viewers.internal.AbstractStructuredGraphViewer.addGraphModelNode(Object) method..).

It isn't possible to create a custom nodes instead of GraphNode class (i.e. instances of GraphContainer) using only business-model/content provider mechanism.

I think this should be possible through ContentProvider ...
Comment 1 Hannes Erven CLA 2009-11-16 17:37:30 EST 
Is there any progress on this issue? I'm currently evaluating ZEST and would also like to create GraphContainers my beans of the ContentProvider.

This bug was originally opened - it seems - on request of Ian in this thread: http://www.eclipse.org/forums/index.php?t=msg&goto=244804&S=d737f352605f0393bd6e57f04a7e7c0b (including URL for reference).

(PS.: I'd be willing to contribute if my skills permit and help is wanted.)
Comment 2 John Conlon CLA 2010-10-18 13:31:15 EDT 
(In reply to comment #0)
> I think this should be possible through ContentProvider ...

In my ContentProvider I implement an INestedContentProvider which (from the Javadoc) is: 

A content provider for nested graphs. Any entity based content provider (IGraphEntityContentProvider or IGraphEntityRelationshipContentProvider) can
also implement this interface. Any node that "hasChildren" will be rendered as a container.
Comment 3 Alexander Nyßen CLA 2015-01-22 02:43:36 EST 
Re-assigning back to inbox, as Ian is no longer active committer.