openframeworks / openframeworks/openFrameworks
OF next ideas
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
here some ideas I would like to discuss / work next.
Sharing here in the hope more people engage in discussion and code if any of this subjects is of interest.
- test PR where download_libs.sh actually downloads from github apothecary release - https://github.com/openframeworks/openFrameworks/pull/7128
- separate cairo files, and have some define set to include cairo in the project, so it can be disabled per project, if needed. https://github.com/openframeworks/openFrameworks/pull/6985
- moving cairo functionality to a core addon - https://github.com/openframeworks/openFrameworks/pull/7326
- remove Appstore from xcode schema and substitute it with the right define. - https://github.com/openframeworks/openFrameworks/pull/7133
- simplify getting started ( so people who clone the OF repo can quickly get up and running )
- simplify and cleanup packaging process ( before we transition to GH Actions releases )
- the same for libfmod, including the rsync step, so we can have smaller binaries / faster build if needed.
- Now fonts have correct metrics, we can work on a scale factor so it can be used seamlessy on retina.
- work on of::filesystem to get it totally working. OF jumps back and forth a lot in filesystem::path to string, so I'm trying to minimize that - https://github.com/openframeworks/openFrameworks/pull/7110
- ios device / screen rotation
- Spend some time experimenting with Chalet to build OF (seems promising). Really nice with dependencies, if you are used to modern tools like platformio or rust crates.
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
This issue is a discussion list rather than a scoped task, and it names no file, test, or entry point. Start by selecting one unchecked proposal, read any relevant linked pull request such as #7326, and agree on a narrow scope and definition of done before coding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, mobile-dev, performance, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100