<div dir="ltr">Hi Sergey,<div> </div><div>Thanks for you email. There is a lot of interesting topics, I'll try to answer to all of them :)</div><div> </div><div>For the view complexity of the topology, you're right, that's why we started to rewrite the D3 view to bring something more stable in term of node placement but also being able to leverage the filtering mechanism we have to reduce the number of elements present in the view and sent by the server. Currently we don't have anything ready yet, just a POC.</div><div> </div><div>For the "different view thing", there is a way to achieve this which is for sure not perfect. We do have this "graph" object listening the websocket connection and dispatching message to layouts. Currently two layouts are listening the graph events, the "standard" topology view and the Openflow rules view. The last one displays only the flow rules. That is for sure something we need to rework in order to make it more flexible and more clear.</div><div> </div><div>It seems to me that we already have some of what you suggested but not clearly identified and decoupled. That's where we want to push efforts. The typescript migration will help on this.</div><div> </div><div>Do you think you can share the work you did around the typescript migration ? We think that this conversion we will be the first step toward a better architecture.</div><div> </div><div>Another question a bit out of topic, do you think you can share in which context you used Skydive ?</div><div> </div><div>Thanks,</div><div>Sylvain</div><div> </div><div> </div></div><div class="gmail_extra"> <div class="gmail_quote">On Thu, May 10, 2018 at 5:26 PM, Sergey Glazyrin <<a href="mailto:s.glazyrin@partner.samsung.com" target="_blank">s.glazyrin@partner.samsung.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div class="m_8365125739118221217WordSection1">Hello guys! This is a follow up of discussion we started with Sylvian month ago.Sorry Sylvian, was busy. How do we extend skydive frontend if customers want to customize it ?Problems/Use cases:• Network topology sometimes very complicated, what if want to show only nodes between two network elements ? A and B ? Customers/People want to have a simplified interface.• We may need to show only part of Metainformation for network elements. How can we do that ?• Will the browser behave good if we show network topology for 2000 hosts? Will it have a problem with memory ? Solve performance problem• Introduce different levels of detalization: host detalization, concrete host detalization. Then we may need only small datasets, if we have 2000 hosts, we may need only a hosts and network elements which connect hosts to each other. Solve problem of different layouts/views.Here we may introduce another abstraction: workload which will be responsible for transformation data sets/simplification/another custom user needs. Skydive frontend new architecture <img width="1243" height="360" id="m_8365125739118221217Picture_x0020_3" src="cid:image002.png@01D3E884.00FF3A10"> Conclusion I believe such approach would help us to have a lot of different views/workloads and easiest usage of frontend PS: Around 20-30% we migrated to typescript but then we stopped migration because of tight deadline. Sylvian reply:<div style="border:none;border-left:solid #1f497d 1.0pt;padding:0in 0in 0in 4.0pt;margin-left:.5in;margin-right:0in">Hi Sergey, Great ! As we wanted to provide other views for the topology, the D3 things implemented as a library is really something interesting, especially using typescript. Do you have any code available or something ? Tests would be really useful too.About the "more user-friendly" frontend, do you have anything that you can share, it will help us to improve it :) Regards,Sylvain</div> Previous email: <div style="border:none;border-left:solid #1f497d 1.0pt;padding:0in 0in 0in 4.0pt;margin-left:.5in;margin-right:0in">Hello guys!I do like your skydive stuff but I need to customize frontend of skydive to make it more userfriendly for customers + my own stuff, a bit differnet data, etc....I started rewriting javascript frontend on TypeScript.But then I realized I've no time to finalize it because we have a tight deadline.It's not a problem.In general I love skydive, love frontend, especially D3 related stuff. But I'd like to work on moving this D3 related stuff, getting information from websockets in this npm package, without any Vue things, etc. Would be that interesting for you ? If I implement it with tests, etc, would you consider to to migrate to this npm package ?</div><img width="1" height="1" id="m_8365125739118221217Picture_x0020_1" src="cid:image001.gif@01D3E883.A6E6F4F0" alt="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif"> Best, SergeySamsung R&D Institute PolandSamsung ElectronicsCell: +48731810674 </div><table id="m_8365125739118221217bannersignimg"><tbody><tr><td> </td></tr></tbody></table><table id="m_8365125739118221217confidentialsignimg"><tbody><tr><td> <img style="border:0px solid currentColor;width:520px;height:144px;display:inline-block" src="cid:cafe_image_0@s-core.co.kr"> </td></tr></tbody></table></div><img src="http://ext.w1.samsung.net/mail/ext/v1/external/status/update?userid=s.glazyrin&do=bWFpbElEPTIwMTgwNTEwMTUyNjIzZXVjYXMxcDIzNzljMDQ4MTI4YjQzMTBmMzBmNjkzNzQ4OGYzYjViYyZyZWNpcGllbnRBZGRyZXNzPXNhZmNoYWluQHJlZGhhdC5jb20_" border="0" width="0" height="0" style="display:none"></blockquote></div> </div>