CarlosJuncher03 commented on issue #6094:
URL: https://github.com/apache/hop/issues/6094#issuecomment-3591733001

   Let me clarify the current behavior and the feature request.
   
   Current behavior
   
   When I create a new pipeline, the canvas starts with a relatively small, 
fixed area.
   
   I can only pan within that limited area.
   
   If I want more space, I have to drag a step to the edge of the canvas; when 
the step reaches the border, the canvas auto-expands a little in that direction.
   
   This means I need to keep pushing steps against the borders, little by 
little, to gradually reveal more space.
   
   Requested behavior
   
   I would like the pipeline canvas to behave more like an “open” or “infinite” 
workspace.
   
   From the start, I should be able to freely pan in any direction, even where 
there are no steps yet.
   
   The available area should feel large and unconstrained, instead of only 
expanding in small increments when a step hits the border.
   
   This is similar to how tools like n8n handle their workflow canvas, where 
you can freely pan and position nodes in a large virtual space from the 
beginning.
   
   Why this would be useful
   
   Better UX for large pipelines: When working with complex pipelines, you 
often need to plan the layout in advance. A more open/infinite canvas makes it 
easier to group related steps, keep branches visually separate, and avoid 
overlapping flows.
   
   Faster design workflow: Today I need to repeatedly drag steps to the borders 
just to create space, which is time-consuming and breaks the flow of modeling. 
With free panning and a larger virtual area, I can place steps directly where I 
want them.
   
   Consistency with modern tools: Many modern orchestration/ETL/workflow tools 
(such as n8n) already provide an “infinite” or very large canvas. Adopting a 
similar navigation model would make Hop feel more familiar and comfortable for 
users coming from these tools.
   
   Cleaner, more readable pipelines: When space is constrained, it is tempting 
to place steps too close together, which hurts readability and maintainability. 
Having more room by default encourages clearer layouts that are easier to 
understand later.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to