Open-source SVG-based data merge engine (Inkscape). Looking for VDP/prepress feedback

I was going to mention QR codes and barcode generations.
Layout generations would be another roadmap feature for sure.
I have honestly never messed around with Inkscape so I am about to dig into that tonight...
Great work though, this is turning out well!
 
Thank you very much @Printssistant

Okay, I'll focus on QR codes and barcodes.

The system actually works almost entirely with a mini-language on the dataset that allows you to define any layout composition.

For example, if in the first column we put:

{A4^ b=15}.Layout{3x4 g=1 s=creditcard}

This defines a landscape A4 layout with a 15mm margin, and a layout of 3 columns and 4 rows, separated by 1mm, and adapts our template to fit a credit card.


Although it's very powerful and allows you to customize many parameters (arrangement order, sizes, gaps, repetitions, backgrounds, etc.), I don't think it's geared towards what's typically done in VDP. Even so, in many ways, Layout probably offers now far more possibilities than any VDP system.
 
If you could find an intuitive way to do dutch cut imposition that would be pretty huge.

I just looked up "Dutch cut" online, and I'm not sure if I understood correctly.

In PnPInk, if you do:
.L{2x3}
you get:
1 2
3 4
5 6

If you do: .L{-2x3}
2 1
4 3
6 5
(reverse the column order)

If you do: .L{2x-3}
5 6
3 4
1 2
(reverse the file order)

If you do .L{-2x-3}
6 5
4 3
2 1

In PnPInk, "^" is a rotation symbol.

If I use Page{letter}, it will use a vertical letter size, but if I use Page{letter^}, it will be landscape.

If I use:
L{2x3^}, it will change the order of the page layout (rows first, then columns)
1 4
2 5
3 6

(I think this is the configuration you're referring to).

If I use L{?x?^}, it will calculate the number of rows and columns that will fit inside the paper+margins depending on the size of the template, and impose like above.

And I can also make various combinations like L{-3x?^)
And many more (gaps between templates, automatic gaps, hextiles, hexgrids, offsets between rows and columns),

I'm sure it's easy to see what would happen if I use
Layout{3x3 shape=creditcard^}

I don't know if what I've said makes it clear how it works.
 

A common issue for example is 4x6 postcards only fit 4up on a 12x18 sheet with a standard layout, but if you do a dutch cut (or combo cut) you can do two cards sideways and fit 6 to a sheet. I know PSL Jetletter doesn't do dutch cuts, and Fiery Impose doesn't either, so it's a useful feature that doesn't have much support.
 

A common issue for example is 4x6 postcards only fit 4up on a 12x18 sheet with a standard layout, but if you do a dutch cut (or combo cut) you can do two cards sideways and fit 6 to a sheet. I know PSL Jetletter doesn't do dutch cuts, and Fiery Impose doesn't either, so it's a useful feature that doesn't have much support.
Okay. I understand that the important thing then is to make the most of the page. Would the order matter?

Today, it could be done in PnPink with the powerful "@1" page positioning functionality ( see Page - PnPInk Documentation ).
First, 400 cards are printed on 100 pages with special margins, leaving free space on one side {A4 b=[10 70 10 10]}. Then, another 200 cards are created begining in page 1 again, in the space with {A4 b=[10 10 10 130] @1}. (Im talking in mm)


It's a bit manual and you lose control of the order on the page... I understand that ideally PnPInk would manage the space automatically in the best way, being able to rotate cards if necessary, right? It wouldn't be difficult to implement.
 
Last edited:

A common issue for example is 4x6 postcards only fit 4up on a 12x18 sheet with a standard layout, but if you do a dutch cut (or combo cut) you can do two cards sideways and fit 6 to a sheet. I know PSL Jetletter doesn't do dutch cuts, and Fiery Impose doesn't either, so it's a useful feature that doesn't have much support.
After reading the post above this response, you nailed it. This is the way... Thank you for bringing it up.
 
Okay. I understand that the important thing then is to make the most of the page. Would the order matter?

Today, it could be done in PnPink with the powerful "@1" page positioning functionality ( see Page - PnPInk Documentation ).
First, 400 cards are printed on 100 pages with special margins, leaving free space on one side {A4 b=[10 70 10 10]}. Then, another 200 cards are created begining in page 1 again, in the space with {A4 b=[10 10 10 130] @1}. (Im talking in mm)


It's a bit manual and you lose control of the order on the page... I understand that ideally PnPInk would manage the space automatically in the best way, being able to rotate cards if necessary, right? It wouldn't be difficult to implement.
If we figure out the "It's a bit manual" pain point, you've got something here. I use SmartStream and it can do this sort of automatically but it is not as intuitive on certain things. It creates two separate impositions on the sheet and the gap between those two impositions is kind of tricky to get exactly right, which is when Dutch cuts become a manual task.
Honestly, I am interested in your software as an imposition software at this point. Rapid VDP and impositions of any kind would be great.
Look up "Nesting" as it refers to printing, that one gets real complex but could be another thing worth pursuing. I am currently trying to make both of these module to be available online as cloud based software. I am the inverse of you I think, very little knowledge of development, over a decade in a commercial print shop running a prepress department. Would be an interesting match here...
 
If we figure out the "It's a bit manual" pain point, you've got something here. I use SmartStream and it can do this sort of automatically but it is not as intuitive on certain things. It creates two separate impositions on the sheet and the gap between those two impositions is kind of tricky to get exactly right, which is when Dutch cuts become a manual task.
Honestly, I am interested in your software as an imposition software at this point. Rapid VDP and impositions of any kind would be great.
Look up "Nesting" as it refers to printing, that one gets real complex but could be another thing worth pursuing. I am currently trying to make both of these module to be available online as cloud based software. I am the inverse of you I think, very little knowledge of development, over a decade in a commercial print shop running a prepress department. Would be an interesting match here...
Thanks, that's very useful feedback.

The "too manual" part is probably the biggest challenge right now. The engine can already handle some fairly complex VDP impositions, and making those workflows easier and more automatic is really achievable. Even now, much more complex things are being done.

At the moment I'm also spending quite a bit of time creating simple video tutorials. One thing I've learned is that many people don't realize what PnPInk can actually do unless they see it in action. My goal is to create short, practical examples that are easy to follow, while still giving an idea of the much broader possibilities behind the software.

My background is much more on the software side than the commercial print side, so insights like the SmartStream example are extremely valuable. If you come across other real-world imposition or VDP pain points, I'd be very interested to hear about them. Understanding where existing tools become difficult to use helps me prioritize what to work on next.
 
Thanks, that's very useful feedback.

The "too manual" part is probably the biggest challenge right now. The engine can already handle some fairly complex VDP impositions, and making those workflows easier and more automatic is really achievable. Even now, much more complex things are being done.

At the moment I'm also spending quite a bit of time creating simple video tutorials. One thing I've learned is that many people don't realize what PnPInk can actually do unless they see it in action. My goal is to create short, practical examples that are easy to follow, while still giving an idea of the much broader possibilities behind the software.

My background is much more on the software side than the commercial print side, so insights like the SmartStream example are extremely valuable. If you come across other real-world imposition or VDP pain points, I'd be very interested to hear about them. Understanding where existing tools become difficult to use helps me prioritize what to work on next.
I will certainly let you know. Thanks for getting this thing up and running. I look forward to connecting someday and working on some stuff with you.
 
   
Back
Top