openframeworks / openframeworks/openFrameworks

Suggestion/discussion: modularize oF

Open
#4,929 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

development-strategy feature
Dominant language
C++
Stars
10.4k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
9

Description

Hello,
I saw you are restructuring oF quite a bit. I'd like to suggest to make oF more modular. Right now it is one bit framework and I use it for lot of different programming jobs. But lets say I am building a command line tool or a simple server, then I like to keep it as minimal as possible, without graphics and audio stuff.
Ideally I could just use the modules, which are really needed. Maybe we could split it into modules/addons like core, audio, graphics, network, ...

Also things like ofSerial and the firmata classes could live as an addon. I think ofxOsc is used more often than ofSerial and it is an addon. Do other classes depend on ofSerial? I don't see why one is an addon and the other one part of the core.

Here are some advantages I see:

  • Apps would be less error prone.
  • Probably easier to maintain, test, debug.
  • oF could be used even on non supported devices, by just not using critical modules, e.g. graphics module on micro computers.
  • oF modules could be used inside other frameworks, e.g. oF core inside Qt

I know this would be a big change, but I would like to know your opinions. What are the cons?

Thomas

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 by reviewing the proposed separation of core, audio, graphics, and network modules, including whether ofSerial and the firmata classes should become addons while ofxOsc remains an addon. Done would require an agreed modular architecture and resolved dependency and support implications for command-line tools, servers, and unsupported devices.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.