Panel Studio
Panel Studio is the editor for Panel apps inside PlaidCloud. It shows the app’s files next to an editor, builds a private preview you can open, and publishes the app when you are ready. You don’t need a git repository to start.
Open Panel Studio
Section titled “Open Panel Studio”- On a project’s Home board, choose Open in Studio on a Panel app.
- In My Panel Apps, choose Open in Studio on an app’s row.
To start a new app, choose Create app in either place.
Create an App
Section titled “Create an App”The Create app dialog starts you from one of five places:
| Start from | You get |
|---|---|
| Blank | A minimal app with an app.py and a requirements.txt. |
| Table | An app built on the table you pick. |
| View | The same, built on a project view. |
| Template | A ready-made app from the Panel App Kit. |
| From the gallery | A copy of an app your workspace has listed in the app gallery. |
Name the app, pick its Project, and choose Create. Studio opens the new app with its files listed on the left.
Pick a file in the list to edit it in the editor. List your Python dependencies in requirements.txt, one package per line. They are installed when the app builds.
Choose Ask Weave to have Weave write or change the app for you. See Build Panel Apps With Weave.
Save, Preview and Publish
Section titled “Save, Preview and Publish”Save stores your changes as a draft. The live app does not change, and nobody else sees the draft.
Preview
Section titled “Preview”Preview builds your saved draft as a private copy and opens it. Only editors of the app can open a preview.
- A preview is removed after 24 hours without a save.
- A workspace can have up to 10 previews at a time.
- Save again and choose Preview to see your latest edits.
Publish
Section titled “Publish”Publish replaces the live app with your saved draft. It requires edit permission on the app’s project, and Studio asks you to confirm first.
If someone else published a change after you opened the app, Studio reports a conflict instead of overwriting their work. Reload the app, bring your edits across, and publish again.
Build Status and Errors
Section titled “Build Status and Errors”The Build tab shows the status of the latest build, and updates as it runs. When a build fails, the tab lists each error with its file and line number, so you can go straight to the line. Dependency problems in requirements.txt come with a hint about the fix.
Errors and warnings are also marked on their lines in the editor, so you see a problem where it is.
For what each status means once the app is published, see Using a Panel App.
History and Restore
Section titled “History and Restore”The History tab lists every published version of the app, newest first, with its build status. Choose Load more to see older ones.
To go back to an earlier version, choose Restore on it and confirm. The restored version becomes the live app and rebuilds. Your unsaved draft is not lost: it stays in the draft and goes live on top of the restored version the next time you publish. If the app already matches that version, Studio says so and changes nothing. If someone published while you were restoring, Studio restores nothing and asks you to try again.
Insights
Section titled “Insights”The Insights tab shows how people use the app and how quickly it responds. Choose the last 7, 14 or 30 days.
| Section | Shows |
|---|---|
| Views per day | How many times the app was opened each day. |
| Page load | The median load time, and the time that 95 percent of loads beat, from the page loads in the period. |
| Slowest queries | The queries that took longest, with how often they ran and their median, slow-end and slowest times. |
| Errors | What went wrong in the period, by the kind of error and where in the app it happened. |
When a period holds more activity than Insights can read, it says the figures are partial. When page loads go over the app’s performance budget, Insights warns you how many did and which queries were slow. Insights never shows the data a query returned or the names of the people who opened the app.
Both tabs need the app to be assigned to a project; an unassigned app shows a prompt to assign it.
Alerts and Digests
Section titled “Alerts and Digests”Choose Alerts & Digests to set up notifications that watch a number in the app’s data and tell you when it crosses a limit, or send a summary on a schedule. See Alerts and Digests.
List an App in the Gallery
Section titled “List an App in the Gallery”Choose Gallery… to list the app as a template anyone who can view its project can create their own app from, or to take it out of the gallery. See The App Gallery.
Pin to Home
Section titled “Pin to Home”Choose Pin to Home to add the app to the project’s Home board, and Unpin from Home to remove it.
Delete an App
Section titled “Delete an App”Deleting a Panel app asks you to confirm first. In My Panel Apps, use the minus icon on the app’s row. Unpublishing also asks you to confirm.
Next Steps
Section titled “Next Steps”- Build Panel Apps With Weave — describe the app and approve the exact change.
- The Panel App Kit — the components Studio’s table, view and template starts use.
- Alerts and Digests — notify people when a number crosses a limit, or on a schedule.
- The App Gallery — share an app as a starting point for others.
- Using a Panel App — logs, usage and rebuilds after you publish.