Visualization Branching

[kahboom]

As we begin to consider more complex integrations that involve transformations, conditionals, and EIPs, we should open up the discussion about Kaoto's UI should handle branching, from the user perspective. This discussion should not be technically-oriented, only based on visualization of branching.

Considerations & Points of Discussion

1. Deep nesting and preventing branches from "conflicting" with one another, visually.
2. Canvas limitations. Do we allow infinite canvas for accommodating very large integrations?
3. Whether or not to allow for branches to be collapsed/expanded.

Ideas

Collapsable Branches

Though right now we are focusing on more linear integrations that are relatively small, wireframes with much more nested workflows are being made.

Collapsed

Expanded

---

Mini Steps for Deeper Nesting

[brunoNetId]

Integration processes may become large. Best practices recommend defining small Camel routes, but the reality is that users end up using the tool in ways you wouldn't have expected.
I think it is important to ensure your canvas is not limited in size, and allow users to move around it, also to zoom in/out.
It's important to be able to display the entire flow. Many customers use GUIs also as documentation tools, to export images so that they can include them in decks and documents to their colleagues and superiors.