Statistics:Posted by hassan1990 — 09 Apr 2011 13:20
Statistics:Posted by admin — 07 Apr 2011 19:29
I think there is already a lot of things to do with that. But you can also include UI changes if you like.hassan1990 wrote:- In this year, all that is required is just to create the new visualization API, integrate the visualization engine with Gephi and some context menu actions. no UI will be changed?
Statistics:Posted by apatriarca — 07 Apr 2011 17:01
Statistics:Posted by hassan1990 — 07 Apr 2011 15:36
Statistics:Posted by apatriarca — 03 Apr 2011 18:03
Statistics:Posted by apatriarca — 28 Mar 2011 19:19
Nothing wrong. The code of the new engine is completely different from the old one and it's difficult to reuse the old octree implementation. Moreover, the old engine use the Picking API to implement selection. The new engine shouldn't use it, picking should be implemented tracing rays or calculating intersections with frustums or cones. This is because those parts of OpenGL has been dropped in newer OpenGL versions. I think it's easier to implement a new spatial data structure than reuse the old code, but you can implement an octree and the performance should be quite good.Also it seems to me that Gephi currently uses Octrees as a spatial data structure. What's wrong with this? Is it too slow or difficult to operate?
Statistics:Posted by vojtech_b — 28 Mar 2011 18:04
Nothing wrong. The code of the new engine is completely different from the old one and it's difficult to reuse the old octree implementation. Moreover, the old engine use the Picking API to implement selection. The new engine shouldn't use it, picking should be implemented tracing rays or calculating intersections with frustums or cones. This is because those parts of OpenGL has been dropped in newer OpenGL versions. I think it's easier to implement a new spatial data structure than reuse the old code, but you can implement an octree and the performance should be quite good.Also it seems to me that Gephi currently uses Octrees as a spatial data structure. What's wrong with this? Is it too slow or difficult to operate?
I don't know. You can surely take inspiration and copy some code fragments from the old code, but I think it may be hard to copy entire classes. It really depends on how much those classes depends on the legacy visualization engine architecture.Lastly are there any parts of the old API that could be reused such as the StandardGraphIO or StandardVizEventManager classes?
Statistics:Posted by apatriarca — 27 Mar 2011 20:19
The event system is pretty good, I think we can reuse it, but it needs to be properly exposed in the VisualizationAPI. Currently it's only in the VisualizationModule.I would like to know more about the new visualization API. What are the main reasons for not being able to use the old event architecture in new API?
Yes, we use an Octree and it does its job with good performances. If its compatible with the new architecture, I think we can simply reuse it in the first place and maybe improve it later if we have time. Antonio?Also it seems to me that Gephi currently uses Octrees as a spatial data structure. What's wrong with this? Is it too slow or difficult to operate?
We can certainly reuse some of this code for the new engine. It's great you are looking at the legacy code, that will help a lot while working on the new engine.Lastly are there any parts of the old API that could be reused such as the StandardGraphIO or StandardVizEventManager classes?
Statistics:Posted by mbastian — 27 Mar 2011 19:05
Statistics:Posted by vojtech_b — 27 Mar 2011 18:51
Statistics:Posted by apatriarca — 26 Mar 2011 16:40