On 29/10/17 16:56, Federico Capoano wrote: > > > On Fri, Oct 20, 2017 at 11:12 AM Leonardo Maccari > <[email protected] <mailto:[email protected]>> wrote: > > > > On 19/10/17 13:30, Federico Capoano wrote: >> >> >> is it ok with the CSS trick for the properties or we wait to >> have it fixed? >> >> >> I'm super busy, so if we want this to be showcased sooner rather >> than later is better to do the PR now and fix the issue later. > > Ok, so I will just do the PR. After the merge please then open an > issue so we keep track of it (I prefer you to do it rather than > myself). > >> >> >> >>>> >>> >>> Blue circles are important because they tell you >>> visually how big is the part of the network that remains >>> disconnected if you remove one cutpoint, without >>> clicking on the cutpoint (which shows the number of >>> potentially disconnected nodes). So they are not nodes, >>> but their size is important to understand what is >>> happening. maybe we can change the color, or the alpha, >>> or we may change the shape of the cutpoint (from circles >>> to diamonds). >>> I suppose for the latter thing we need to change the >>> library though. >>> >>> >>> Ok we can play with the alpha. >> >> ok, open an issue please? >> >> >> which repo? > > https://github.com/netCommonsEU/netjsongraph.js/tree/robustness_graph > > > It seems I can't open issues there, so I opened it > here: https://github.com/netjson/netjsongraph.js/issues/51 >
Ok, I enabled issues in the original project. Will check it asap, or, we can deal with it with Google Code-in. > > but openwisp-network-topology contains the model for the NetJSON > topology in the DB, right? where do you want the new topologies > models be stored? > > > Main logic is in django-netjsongraph, openwisp-network-topology is a > wrapper that integrates it in openwisp2 adding multitenancy to it. > Maybe if you take a look ata mode Ok will do. > > visualization fits better I think. > > So the pseudo-roadmap is: > - I do a PR for netjsongraph.js, as is > - you please open two tickets for the alpha and for the properties > > > Could you remind me the problem regarding CSS hack please? my understanding is that you use _netjson_networkgraph from netdiff.utils to convert a networkx graph to netjson. this returns an OrderedDict which you dump to NetJSON using json.dums(). whatever property of the node ends in the "properties" section of the NetJSON node, which means it is displayed. I hide them with CSS, but maybe there is a better way of putting them somewhere else in the node data. I am talking about the code in the example main.py, here: https://github.com/netCommonsEU/netjson-robustness-analyser/blob/master/main.py > > - i do the pipy package for the analyser module > - i start making up my mind on what modifications are needed on > django-netjsongraph and openwisp-network-topology to integrate the > view. I will need some help from you on this again, but then I > will make you a proposal. > > On a different level, I'd like to start matching, wherever > possible, the owners of the nodes with the nodes in the topology. > I don't have clear ideas now on how to do it, so we will need more > discussion. > > > Indeed this needs more discussion because the way to match depends on > different variables and we need to find a way that won't make us go crazy. Ok, one thing at a time. l. > > Federico > -- > You received this message because you are subscribed to the Google > Groups "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout. -- Leonardo Maccari, Assistant Professor @DISI, University of Trento Tel: +39 0461 285323, www.disi.unitn.it/~maccari, gpg ID: AABE2BD7 -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
