The document couldn't be opened.
if (passwordUrl === url) returnLoading the document…
if (loadState.status === 'ready' && openedUrl === url) returnLoading the form…
return ( ) } function TextField({ widget }: { widget: TextWidget }) { // Typing here and typing into the field in the main view update the same value. const [value, setValue] = useWidgetValue(widget) return ( ) } ``` ### What to know [#what-to-know-6] * **Fields are live.** Under `PDF_VIEWER`, users fill fields in the page; under `PDF_PRINTER`, widgets are read-only, the closest match to an image. * **Values are shaped like HTML form controls:** `text` and `choice` are strings, `checkbox` and `radio` booleans, and `multiChoice` the selected option indices. Every widget with the same field name shows and synchronizes the same value. * **Values follow the document.** Filling in the main view and undo/redo show up as they happen. `useWidgetValue` binds one widget per hook call. * **Display switches.** `hideAnnotations` on `PageCanvas` hides annotations and form widgets together, like `-dShowAnnots=false` with `-dShowAcroForm=false`. In `Viewport`, the content policy levels `annotations: 'hidden'` and `widgets: 'hidden'` leave them out separately. `-dPrinted` has no equivalent. * **The filled PDF comes from the browser.** `prepareDocument()` returns the document with the entered values; see [Saving and downloading](https://sdk.pdf.net/docs/v1/migration/from-ghostscript#saving-and-downloading). * **Date fields.** A text widget's `format` exposes Acrobat date formats as `FormatType.DateTime`, recognized without running scripts; see [`FormatType`](https://sdk.pdf.net/docs/v1/reference/FormatType). ## Saving and downloading [#saving-and-downloading] ### Before: Ghostscript [#before-ghostscript-7] The download is the stored file, or a copy that `pdfwrite` rewrites on the way out, such as with a `-dPDFSETTINGS` preset: ```sh gs -dSAFER -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -dPDFSETTINGS=/ebook \ -sOutputFile=/var/cache/downloads/42.pdf /srv/files/42.pdf ``` `pdfwrite` doesn't edit the input: it builds a new PDF from what the interpreter draws, which should look the same as the original while its insides differ. ### After: @sdk-pdf/react [#after-sdk-pdfreact-7] [`useDocumentSaving`](https://sdk.pdf.net/docs/v1/reference/useDocumentSaving) applies the changes recorded during the session to the original document. `prepareDocument()` returns the bytes for your server, and `downloadDocument()` saves them on the user's device: ```tsx import { useRef, useState } from 'react' import { useDocumentRevision, useDocumentRevisionGetter, useDocumentSaving, } from '@sdk-pdf/react' function SaveControls({ uploadUrl }: { uploadUrl: string }) { const revision = useDocumentRevision() const getRevision = useDocumentRevisionGetter() // The revision on the server: the loaded document's revision until the first save. const [savedRevision, setSavedRevision] = useState(revision) // One save at a time, so an overlapping save can't mark a failed upload as saved. const isSavingRef = useRef(false) const { prepareDocument, downloadDocument } = useDocumentSaving() // Every edit changes the revision; undoing back to the saved state restores it. const hasUnsavedChanges = revision !== savedRevision async function saveToServer() { if (!hasUnsavedChanges || isSavingRef.current) return isSavingRef.current = true try { // Edits made after the save starts may be missing from the saved bytes, so only // this revision becomes saved. const startRevision = getRevision() // The buffer goes to fetch, so don't hand out the loaded document's original // buffer. const bytes = await prepareDocument({ returnOriginalIfUnchanged: false }) // The server stores the file and runs its Ghostscript jobs on it. const response = await fetch(uploadUrl, { method: 'PUT', body: bytes as BodyInit }) // A failed upload keeps the unsaved-changes state. if (!response.ok) return setSavedRevision(startRevision) } finally { isSavingRef.current = false } } return (