processing / processing/processing4

Allow naming main .pde file in `pde://sketch/base64/` schema

Open
#1,213 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
494
Forks
183
Avg merge
4h 39m
Merged PRs (30d)
3

Description

Most relevant area for this enhancement?

PDE

Feature to enhance

pde:// schema

Enhancement details
Enhancement description

Right now, when using pde://sketch/base64/<base64_encoded_content>, the main .pde file is always opened with a default auto-generated name like sketch_250816a.

There should be a way to explicitly specify the main tab name, similar to how additional tabs can already be defined with query parameters.

Example proposal:

pde://sketch/base64/pde=sketchName:<base64_encoded_content>
Benefits
  • Brings consistency with how secondary .pde files are already handled.
  • Accuracy with the original sketch naming.
Challenges
  • Need to decide on the syntax for naming the main tab.
  • Must stay backward compatible with existing links.
Additional context

Secondary tabs already support explicit naming via query parameters:

pde://sketch/base64/<base64>?pde=tab2Name:<base64>&pde=tab3Name:<base64>

The same flexibility should be extended to the main tab.

Would you like to help implement this enhancement?

No, I’m just suggesting the enhancement

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with SCHEMA.md and trace how the pde://sketch/base64/ format handles the main payload and secondary pde query parameters. Define a backward-compatible syntax for naming the main tab, then verify that existing links still work and that the main tab receives the requested name alongside secondary tabs.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
desktop, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.