-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend to use as process flow #49
Comments
No work that I know of, no, and doing so would be a substantial complication/rewrite - the linear nature of the diagram means I could make a lot of assumptions in putting things together that would break with a more arbitrary flow. I've definitely had people ask about this before, but it's not something I'm willing to do myself. The library as it stands does what I need it to do. ^_^ |
I understand. I've been loking for a while for a way to horizontally reflect workflows and Railroad diagrams are so space efficient (because they flow in the same direction as text) I thought they'd work nicely. I've been able to "sort of" make it work for simple workflows (see attached) but obviously they still miss some things and will never allow for complex interactions. I still believe they could be a solid foundation for a simplified and space-efficient workflow layout. I'll see if I can tweak Mermaid's horizontal workflow layout but I won't hold my breath. I assume this is undoable or it would've been done by now :D (the diagram only shows the main actions -rounded boxes- and states -straight boxes- for a simple ticketing system, direction, decision points and owners are obviated, as I want to use it to show where a worfklow in a detail view and/or as a dashboard of workflows stationed in each state) |
Definitely not undoable, just more difficult to do. ^_^ |
Are you aware of work to extend this library into a simple workflow diagram generator?
I've always liked railroad diagrams for their cleannes and would love to use them as a basis for simple flowchart-type process maps.
The only problem is that railroad diagrams have a couple of assumptions and clash with diagram flows:
Of the two the second poses a visual challenge, and probably would require being able to optionally reference individual sections to be able to point to them from other points.
Other limitations are more aesthetic (diferentiating a decision point visually, for example). And other requirements from a workflow are already covered (repetition, selection, etc.)
The text was updated successfully, but these errors were encountered: