Use of non-reduced form for dynamic Action and Signal names

[justparking]

Due to a legacy restriction of the frontend at the time, the nodel backend automatically "reduces" the names of dynamic actions and events.

The key place where this occurs is in ManagedToolkit.java line#742ish:

    public NodelServerEvent createEvent(String eventName, Binding metadata) {
...
            NodelServerEvent event = new NodelServerEvent(_node.getName(), new SimpleName(Nodel.reduce(eventName)), metadata);
...

Note the Nodel.reduce(eventName) which takes place in that method and others (createAction(...)).

Ideally it should not be reduced and left as is. The backend of nodel quite happily deals with the longer forms but, as mentioned, the frontend had issues dealing with spaces, hypens or underscores sometimes when dynamic actions & events were introduced. Previously they were defined declaritively as part of python variable names (e.g. local_event_Output1Volume) so they had inherent naming restrictions. When they're dynamically created naming restrictions are not needed (e.g. Output 1 Volume).

The issue is I'm not sure how the rest of the frontend code (Javascript) copes with un-sanitised names of actions and events so this needs to be tested thoroughly.

It's possible their names need to be processed before they can be dealt with efficiently. Note, that whatever method is decided it need to be highly efficient and able to cope with high quantities of actions of events.

Using the non-reduced form should make bindings much more readable and likely more "matchable" when using the fuzzy-logic autofill method. And I'm hoping with the proposed search behaviour improvement in #283, it should assist with completing mass bindings.

(@scroix, @mcartmel, @dargs FYI)

[morimoriysmoon]

A new branch added. It also supports improved search.
https://github.com/morimoriysmoon/nodel/tree/feat-standardise-search