3 Answers, 1 is accepted
0
Hello tomas,
It really depends on your scenario but unfortunately I don't think that this will work very well - you'll be able to create it but it'll take a lot of time and the application won't have good responsiveness.
The layout of 2500 shapes won't be an issue but the routing of 10 000 edges will definitely be a big problem (especially in Silverlight). Also the initial load time of 12 000+ items will be a lot although there are a couple of customizations that can speed up this process.
In a summary - the biggest problem will be the routing and the sheer number of items.
I hope I was able to answer your question and if you need further assistance feel free to ask.
Regards,
Zarko
Telerik
It really depends on your scenario but unfortunately I don't think that this will work very well - you'll be able to create it but it'll take a lot of time and the application won't have good responsiveness.
The layout of 2500 shapes won't be an issue but the routing of 10 000 edges will definitely be a big problem (especially in Silverlight). Also the initial load time of 12 000+ items will be a lot although there are a couple of customizations that can speed up this process.
In a summary - the biggest problem will be the routing and the sheer number of items.
I hope I was able to answer your question and if you need further assistance feel free to ask.
Regards,
Zarko
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
tomas
Top achievements
Rank 1
Rank 1
answered on 24 Oct 2014, 10:03 AM
Hello Zarko,
If Silverlight is a bad technology, why another should be better. I think html
5 would be much worse in case of client side rendering using some kind of
templates... There is much more layers of indirection.
For me it is not necessary to have the diagram "at once". User can
wait, that is not problem. In case of this big diagram, user can wait 5 minutes.
What I need is:
- Layout for nodes should be close to the “best possible"
- Routing must avoid of crossing another nodes.
- All ends of edges must be visible = orientation of edges is importantEdges must have visible labels
Routing should be some king of bezier or orthogonal.
Thank you.
Tom
0
Hi tomas,
My Silverlight remark was more in the light that in WPF (or Winforms) this will work considerably faster and as for HTML 5 - it really depends on the implementations. If you're interested you can taka a look at our kendo and ajax diagrams.
For the connection routing you can read this help article and for the layouts you can examine our SDK demo and this article.
I've attached a sample project demonstrating a tree layout with around 1000 shapes and 1000 connections so that you can get an idea about the performance (please note that in the project the connections are not using routing and this greatly improves the performance).
I hope I was able to help you.
Regards,
Zarko
Telerik
My Silverlight remark was more in the light that in WPF (or Winforms) this will work considerably faster and as for HTML 5 - it really depends on the implementations. If you're interested you can taka a look at our kendo and ajax diagrams.
For the connection routing you can read this help article and for the layouts you can examine our SDK demo and this article.
I've attached a sample project demonstrating a tree layout with around 1000 shapes and 1000 connections so that you can get an idea about the performance (please note that in the project the connections are not using routing and this greatly improves the performance).
I hope I was able to help you.
Regards,
Zarko
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.