processing / processing/p5.js-web-editor
Adding examples preview
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 1.7k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 8
Description
Increasing Access
I think as a user when you scroll through the examples section, the User is generally confused by such a number of examples and cannot determine the actual behaviour of each shape; in other words, it is not very visually appealing; if the user is unsure of any shape he will have to check each sketch one by one, And it will take time as it will always redirect to the code editor, I am sure that would not be a very pleasant experience as a user. There should be a preview button. There is already an existing dropdown button which contains the download button. But it can be updated with a [+] expand view. It will display the preview, increase user accessibility, and make it easier to use.
Feature request details
In this feature, We will update the down arrow section, as shown in the screenshot. It will then expand the div where the preview of the sketch will be running, displaying the animation of the shape the div will also contain three buttons on the left side or right side,
- share button (to share the shape)
2)Copy(To copy the default code)
3)Download
Making this feature will save users time, and it can be implemented, and the code would be running on click, so it will be convenient too.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the examples section and its existing dropdown and download control. Trace how an example opens in the editor, then determine where an expandable preview and the share, copy, and download actions would fit; done means the preview displays the sketch on demand and all three actions work as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100