processing / processing/libprocessing
`image()` does not match Processing API
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 69
- Forks
- 14
- Avg merge
- 15d 22h
- Merged PRs (30d)
- 3
Description
In libprocessing / mewnala, image() is used to load an image:
def image(self, /, file: str) -> Image: ...
In Processing, image() displays an image, while loading is done with loadImage().
Processing behavior
PImage img = loadImage("image.png");
image(img, x, y);
Expected
loadImage(path) -> Imagefor loadingimage(img, x, y, [w, h])for drawing
See also
Contributor guide
No contributing guide indexed for this repository
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 current image() entry point in libprocessing or mewnala and inspect how images are currently loaded and drawn. Compare that behavior with the linked Processing API references; done means loadImage(path) loads an Image and image(img, x, y, [w, h]) draws it with the requested sizing forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, computer-graphics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100