Comment

Comment by ororroro

Getting a good layout is too dependent on the order of definition. I can see that becoming unsolvable for the user for large diagrams but seems ok for small ones. For example the following gives an ugly yet valid layout of the example:

  [more loot] no ->[<end>e]
  [<start>start] -> [<state>plunder] -> [<choice>more loot] -> [start]

  [Pirate|
    [foul mouth]<:-[beard]
    [parrot]--[beard]
  
  ]
  
  [<table>mischief| bawl | sing || yell | drink ]
  [<abstract>Marauder]<:--[Pirate]
  
  [Pirate] - 0..7[mischief]
  [<actor id=sailor>Jolly;Sailor]
  
  [sailor]->[rum]
  [Pirate]-> *[rum|tastiness: Int|swig()]
  [sailor]->[Pirate]
parent ororroro 3 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton