Skip to main content
Starting with version 9, the PitchPrint app is instantiated in a separate iFrame to sandbox it from your product page as well as prevent styling conflicts with the hosting page. To do this, we created two classes, the PitchPrintClient which is instantiated inside the hosting page and a PitchPrintFrame which lives in the iFrame. The PitchPrintClient class is your entry point into the app. This is the class that handles the creation of the iFrame and some other initialization procedures.
If you are on any of the cart frameworks, you can use the; designer ready method to hook your events
PitchPrint is built on T3 Javascript Framework and adheres to its core philosophy of modular design. To this end, everything on the PitchPrint app is actually a module and are loosely coupled, which means modules don’t talk directly to each other. They simply broadcast events and any interested listener can plug in and perform an action based on the event. On the PitchPrintClient class, you listen to events with the “on” method and fire by calling the “fire” method on the class.
Or talk to the app by firing an event!

Events you can listen for

List of events your app can listen for

Events you can fire

List of events your app can dispatch to PitchPrint

Designer ready method

Hook your custom code into the editor once the designer is ready.

Initialization Options

All the options you can pass when creating a PitchPrint client instance.