We'd love to know what you think of Ruby®
Hi,
I’d like to suggest a few enhancements for the API upload endpoints that could improve both functionality and workflow efficiency.
1. Job Time Calculation Option
When uploading design files using an Import Profile, under Processing Steps, if the "Save as Job" option is selected, it would be beneficial to include an additional option to calculate the job time. This would provide better planning and visibility for production tasks right from the import stage.
2. Handling Multiple Design Uploads & Layout Constraints
Currently, when uploading multiple designs, Ruby creates a single job and uses the positioning values defined in the Import Profile to determine the layout. In this scenario, the configured X and Y offsets apply as expected.
To improve flexibility and automation during this process, I suggest adding the ability to define a "Plate Size" — a fixed working area (e.g., 12 inches by 12 inches) that constrains where designs can be positioned within a job.
Once the plate size is set, Ruby could automatically arrange the uploaded designs within that space using a left-to-right, top-to-bottom layout approach. This would involve placing designs starting from the top-left corner, moving horizontally across the width of the plate, and then continuing on the next row below — similar to a grid layout. This ensures organized placement and efficient use of the material area.
If there are more designs than can fit within the defined space, the system could either:
Automatically create a new "Child Job" and continue placing the remaining designs using the same layout logic, or
Allow the user to optionally add another "Design" (which itself contains multiple smaller designs) to the same job, provided the combined layout still fits within the defined 12x12 area. This would help maintain alignment with material size while supporting flexible design grouping.
This approach would streamline the job creation process, reduce manual layout adjustments, and ensure all content stays within the material boundaries.
Let me know your thoughts on these suggestions or if you'd like any further clarification.
| Ruby Version | 2.1 |