Well, this sounds like we should take a look at the Meta package that wraps nodes and gives them mandatory and optional attributes, adding "typing" to the node space. Sadly there, is not much information on the Wiki on that yet, but the code is fully functional at https://trac.neo4j.org/browser/components/neo-meta, at test is for example at https://trac.neo4j.org/browser/components/neo-meta/trunk/src/test/java/org/neo4j/neometa/model/TestOOModel.java
That makes it much more convenient to lay out the NeoClipse representation, but we cannot assume that people are using it since it is optional. We maybe could put NeoMeta support in there by being able to point out the Meta structure and act accordingly? /peter On Thu, Jun 5, 2008 at 11:05 AM, Peter Haensgen <[EMAIL PROTECTED]> wrote: > Hi there, > >> What about showing the relationship type in the Neo Graph view of >> Neoclipse? > > Makes sense. However, this could be a mess in larger graphs, so the user > should be able to switch it on / off. Could be done in the view menu, > similar to the layout selection. > >> Another suggestion is to replace the "Node" text in the graph and add >> some default property value instead (when it exists). The property >> should of course be configurable. > > The problem is that we don't know much about the nodes of the graph. > Unlike relationships, there is no "NodeType", which we could use to > classify nodes and to identify the property that would be useful to > represent the node. > Currently, giving a node a meaning is left to the application developer > (for example by adding some "type"-property). So without some more > meta-information it is hard to tell which property should be displayed > in the graph for which kind of node, as the kind of node is unknown to > the graph viewer. Using the "NAME" (as in your example) makes sense for > a specific kind of nodes, but there may be other nodes in the graph > representing other types of objects, which may have other identifiers... > > Maybe we should stick with your suggestion for now, like a configurable > list of fallbacks: > - first try "NAME", if not found: > - try "name", if not found: > - try "identifier", ... and so on > > Hmm. > > I also would like to see a color coding for nodes, e.g. nodes of same / > different types are shown in same / different color. Similar problem. > :-/ > > Wouldn't it be good to introduce a general "NodeType" in Neo? > > Ciao, > Peter > > _______________________________________________ > Neo mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > > -- GTalk: neubauer.peter Skype peter.neubauer ICQ 18762544 GTalk neubauer.peter Phone +46704 106975 LinkedIn http://www.linkedin.com/in/neubauer http://www.neo4j.org - New Energy for Data - the Graph Database. http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
