Raffzahn

Schematics/Waveform: Rendering of Low Active Signal Names

2

# Ist: Low active signal names are usually rendered with an Overline. Recomendet implementation ( according to https://github.com/drom/wavedrom/wiki/Unicode ) is the usage of Unicode overline code sequences. While this is...

# Ist: As of now, terms are not connected ( see wavedrom/wavedrom#94 ) and can only have one output signal. # Soll: Connected terms enable the creation of multiple output...

# Ist: Right now any signal used as input for a term is implied 'created'. There should be a way to add an optional definition for every (external) input signal....

# Ist: Input signals with similar names are not connected: Example: ``` javascript { assign: ["out", ["OR", ["AND", ["INV", "a"], "b"], ["NAND", ["INV", "b"], "a"] ] ] } ``` ...

Puting input signal names into 'vonnection tas' coudl improve readability. Especially as long input signals are not front alligened.  Output signals may be handled similar. As long as there...

Align Input Signal Names

2

It'll be great if all signal names could be 'pulled left' to be alligned left hand 

# Ist: Right now it's only possible to a single term to describe a network. Seperate terms will result in seperate network. Example: ``` javascript { assign: ["out", ["OR", ["AND",...

Change INV to NOT

4

To bring term names into a more logic nameing, INV should be changed to NOT, according to the names used in IEC60617. NEG is also possible but less readable. Same...