added for node rendering with various cases (active/neighbor/normal/grey), then made the labels renderer call the node renderer

(it fixes the black color init cases)

show nbClasses and nbNodes side by side, don't count N/A class in nbClasses if empty, rename vars to be clearer

translations for the color menu can be specified in TW.conf.facetOptions + make clusterColoring work for string-labeled clusters + allow user to choose if colors are randomized each time

assumed that source gexf file was equivalent to having a 'name' node attribute, which is not the case in specifications?

global var selections removed and stored inside SystemState + transformed into an array everywhere (was inconsistent) + fixed changeType selection materialization ; possible TODOES: better setState function, possible integration of opposite side neighbors in SystemState too

heatmap coloring, better facetOptions cases, better handling NaN in attributes and renamed coloring functions

we consider an attribute is numeric if a large % of it is numeric (by default: 98%)... in this case we can still operate binning and the NaN values are grouped and isolated in a grey legend item

added binning mode 'samerange' + new syntax for choosing it in settings + finished replacing atts_2_exclude + possibilities for better string cluster mapping TODO: color functions per settings

but we should rather use the sigma.exporters.gexf.js

renamed to TW.states and TW.gui + fixed old sliders caching bug + fixed node normalization in parsing

variables init was obscuring settings file + moved AjaxSync back to globalUtils + fixed selector engine instance scope

renamed (topPapers to relatedDocs, divFlags to moduleFlags...), fixed several config effects that were disconnected (sizeMult, tagcloud sizes, colorsByAtt), generalized the TW.conf prefix

reordered params inside settings_explorerjs with new packaging in TW.conf property and more meaningful/transparent variable names + newurl param sourcemode

facets (ie clusters and other searchable/colorable attributes) should work with bipartite case, but it meant factorizing facetsBinning() and updateValueFacets() from commit 71507331

we adapt the functions that currently need only one element (ie colors, legends) instead of adapting activetypes expression

this boolean array symbolizes for each node type if yes or no it is displayed, with effet also on edges)... It apparently replaced around 2015 the earlier convention with types A, B, AB... it is often used (symbolizing for each node type if yes or no it is active)... it was sometimes named states (very confusing with the other 'states' that record user interaction steps and that also contain info about these activetypes) or type (misleading singular)

old initListeners split in three: initGUIListeners and initSearchListeners that are run once at page load, and initSigmaListeners that is run for each new graph open from local file... also env function and CSS for the local graph file input

in other words we try to distinguish between what needs to be initialized once and what needs to be initialized each time we get new graph data... this use case wasn't covered before and will need some more re-designing, but it's convergent with modularising the app