Improve readability with new line as terminator and whitespace

[chrisalley]

It would be nice to (optionally) end statements without a semicolon and use a new line instead. For example, instead of this:

graph LR;
    A[Hard edge]-->|Link text|B(Round edge);
    B-->C{Decision};
    C-->|One|D[Result one];
    C-->|Two|E[Result two];

you could just write:

graph LR
    A[Hard edge]-->|Link text|B(Round edge)
    B-->C{Decision}
    C-->|One|D[Result one]
    C-->|Two|E[Result two]

The latter is more readable as it is less dense on the eyes.

Furthermore, you could improve readability by allowing optional spaces between parts of a statement. e.g.

graph LR
    A[Hard edge] -->|Link text| B(Round edge)
    B --> C{Decision}
    C -->|One| D[Result one]
    C -->|Two| E[Result two]

[knsv]

I like the syntax. Readability is important. Will give this some thought.

[vijay40]

Hi knsv,

If nobody is currently working on this issue, I like to work on it.

[knsv]

Great! It is yours.
Good luck!

[vijay40]

I have created a pull request for allowing spaces between vertices and link.

The another issue discussed here is about ending a statement with a newline instead of semicolon. I can do that too, but it requires the last statement of the graph to either end with a semicolon or have some special symbol to represent the end of graph. If we can discuss and decide about that then it will be great, before starting to work on it.

[knsv]

Sounds good! I have added a comment statement that does not require a semi colon at the end. The same structure could be used for the other statements. Let me merge and clean things up before you go at it. Will post here when done!

[knsv]

Ok Vijay thanks for your pull-reqest. I have merged it and refactored the token lists a bit to avoid duplications. In order to avoid conflict when merging next pull request It good if you get the latest version before the elimination of ; requirement

[knsv]

Good work Vijay. Included in release 0.2.16