Seems like your index key contains characters illegal on your current file
system... would it be possible to see the code? or could you supply which
index keys you use to index your comments?
2010/10/12 Tobias Ivarsson tobias.ivars...@neotechnology.com
Hi Paul,
Comment is not a reserved word,
That would be super cool. 3D could be beautiful, and possibly allow more
interesting visualizations of a graph. In addition to an overview of the
scene, it would be fun to play with 1st person and 3rd person views of the
current node.
What would be an easy proof-of-concept?
/Andreas
On Oct
Wow, i tought exactly about the same thing today.
I checked on google, found this mail and ... noticed that it's from yesterday :)
i'm really out of spare-time to try this and it's not on my priority list.
But if anyone is working on it, please tell, i'll be glad to help if i can :)
*hugs*
--
I think that the most tricky thing will be the algorithm, that places the
nodes and associations in a 3D space.
Christopher
Am 2010 10 12 11:08 schrieb Andreas Kollegger
andreas.kolleg...@neotechnology.com:
That would be super cool. 3D could be beautiful, and possibly allow more
interesting
Hello all,
We are pleased to announce the first milestone towards the 1.2 release of Neo4j
-- 1.2.M01. Our current focus is on usability, which means improving the
overall experience of getting, installing, and using Neo4j. We're starting with:
- a bi-weekly release schedule, for quick
Googling around for force directed layout java reveals Graphael, which might
be an option -- http://graphael.cs.arizona.edu/
On Oct 12, 2010, at 12:24 PM, Alex Averbuch wrote:
Hey,
igraph already supports 3D layouts and makes the vertex coordinates
programmatically accessible. Maybe Jung or
Or possibly linloglayout -- http://code.google.com/p/linloglayout/
Now that I'm thinking about this, visualization comes up so often that perhaps
we could/should start a labs project for the java algorithm bits.
On Oct 12, 2010, at 12:24 PM, Alex Averbuch wrote:
Hey,
igraph already supports
Great. Seems that this in general has something to do with:
http://en.wikipedia.org/wiki/Force-based_algorithms_(graph_drawing)
Check out these examples: http://code.google.com/p/webglsamples/ working
with dev version of Chrome.
Flying through a 3D graph would be really fancy :)
Am 2010 10 12
Hi.
It's not a web app, but we built a prototype of 3D graph visualizer before:
http://d.hatena.ne.jp/keiono/20081122/1227423548
However, the problem is it is very difficult to create an intuitive
and easy to use user interface to browse a 3D space. Also, it is a
bit vague what the significant
Hi.
Except small and sparse graph, 3D force-directed/spring model
automatic layouts creates big hairball and it is very hard to browse.
I've tried igraph and it creates nice 3D visualizations, but in many
cases, our users (mostly scientists) say, it's cool...but what's the
point? Does it give us
Mathieu, I saw your screenshots - awesome.
Do you have any experience with HTML5/WebGL? The advantage would be
that the model could be completely created and rendered in a Browser
(simply using the REST interface). This is, of course, heavy
JavaScript programming :)
Christopher
On Tuesday,
The first thing that comes to mind as a possibly useful 3D graph
visualization is to lay the graph on a (non-planar) surface, rather than
just in free space. Ie, over some sort of topography.
The topography could represent a geographical landscape of mountains,
hills, canyons, and valleys...
Like Kei, I'm very suspect of the value 3D brings if the relationships
themselves are more or less 2D or dimensionless, and the number of data
elements (and relationships) is relatively large. For that matter, even 2D
representations of the total graph space are not all that communicative.
What
Hi Christopher.
My point is, 3D graph visualization is worth trying (because it's cool
:-) ), but still an open question even for researchers in data
visualization field. Although this is a hard problem, but I've
already got some use cases. In general, graph database users wants
visualization
All,
Sorry for the false alarm. It turns out that the actual field name that I was
using was Comment\n (literal newline at end of string), not Comment. We do
not have a requirement to index properties with newlines in their name, so you
can ignore this post.
Thanks for looking it to it.
Not necessarily a false alarm...since you *should* be able to index such a
creature. Full text should certainly be able to contain whitespace
characters, and the lucene reader/filter or your own reader/filter should
strip them out. I was under the impression that the default reader/filter
was
16 matches
Mail list logo
