Page Layout and Scroll Options in Our JavaScript Viewer

This Is a Title / H2

PSPDFKit for Web’s page layout options are based on the concept of spreads: Pages can be laid out one at a time or side by side in a double-page layout. For books and magazines that have a cover page, we support keeping the cover page in single-page layout, while laying out the following pages side by side in double-page layout. We call these groups of single- or double-pages spreads.

Spreads allow other view-related options to work with all layout modes.

We support changing between scrolling and viewing a single spread (single or double page) at any time. All configuration happens by updating the ViewState. Please see our view state guide for more information.

This Is a Title / H3

Testing here is extremely tricky; Apple saves absolute paths in the binary, so if you happen to have the same username on the build machine and your test machine, it might work, but it fails somewhere else. It also seems that LLDB uses the shared module cache, so you need to delete DerivedData on every run. And (see later in this article), where you store the example and which other files you store also play into this — dare I say, this was extremely confusing and frustrating to debug.

This Is a Title / H4

Testing here is extremely tricky; Apple saves absolute paths in the binary, so if you happen to have the same username on the build machine and your test machine, it might work, but it fails somewhere else. It also seems that LLDB uses the shared module cache, so you need to delete DerivedData on every run. And (see later in this article), where you store the example and which other files you store also play into this — dare I say, this was extremely confusing and frustrating to debug.

This Is a Title / H5

Testing here is extremely tricky; Apple saves absolute paths in the binary, so if you happen to have the same username on the build machine and your test machine, it might work, but it fails somewhere else. It also seems that LLDB uses the shared module cache, so you need to delete DerivedData on every run. And (see later in this article), where you store the example and which other files you store also play into this — dare I say, this was extremely confusing and frustrating to debug.

This Is a Title / H6

Testing here is extremely tricky; Apple saves absolute paths in the binary, so if you happen to have the same username on the build machine and your test machine, it might work, but it fails somewhere else. It also seems that LLDB uses the shared module cache, so you need to delete DerivedData on every run. And (see later in this article), where you store the example and which other files you store also play into this — dare I say, this was extremely confusing and frustrating to debug.

code-text

code-text(opens in a new tab)

1. First item
2. Second item
3. Third item
4. Fourth item
5. First item
6. Second item
7. Third item
   1. Indented item
   2. Indented item
8. Fourth item

• First item
• Second item
• Third item
• Fourth item
• First item
• Second item
• Third item
  • Indented item
  • Indented item
• Fourth item

puts "Some code here."