processing / processing/processing-website
Generate `.pdez` files for each code example
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- MDX
- Estrellas
- 90
- Forks
- 122
- Merge medio
- 1 h 43 min
- PR fusionados (30 d)
- 3
Descripción
Context
As part of the effort to improve the Processing website and editor, a new feature has been introduced to allow users to open sketches and libraries directly in the Processing editor by clicking on a link. This will allow us to add a link to each example, opening the corresponding sketch directly in the Processing editor.
Problem statement
When browsing the examples page we want users to be able to run the examples in the Processing Development Environment (PDE). Currently, it can be time-consuming and confusing for users to manually copy and paste each tab of an example into the PDE and ensure that all required assets (e.g., images, fonts) are present.
The planned "Open in Processing Editor" feature aims to address this issue. However, it requires that each example have a .pdez file, which is not currently generated when running the script that copies examples over from the processing-examples repository.
Proposed solution
To address this issue, we can modify the existing updateExamples script that copies Processing code for each example from the processing-examples repository to the Processing website. Specifically, we can update the script to automatically generate .pdez files for each example and add them to the corresponding example folder in addition to the existing .pde files and any other files that are already being copied over.
Benefits
This change would greatly benefit users who want to quickly run examples from the website without having to manually copy and paste each tab into the PDE. By automating the process of generating .pdez files for each example, we can improve the user experience and make it easier for people to get started with Processing.
References
The process of updating examples on the website is described in details here:
https://github.com/processing/processing-website/blob/main/docs/examples.md
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza con scripts/updateExamples.js y lee docs/examples.md para entender cómo funciona el proceso de copia de ejemplos. Rastrea cómo se gestionan las carpetas de ejemplos y los archivos existentes, y después verifica que cada ejemplo copiado reciba un archivo .pdez junto a sus archivos .pde y otros recursos. Confirma que los archivos generados admiten los enlaces previstos “Open in Processing Editor”.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- javascript
- Área
- tooling
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bien especificado
- Aptitud para principiantes
- 38/100