chore: the project could use some refactoring

[Nitish-bot]

The whole project is currently contained within a ~4k LOC L5.lua file. This makes the dev experience less than ideal by having everything mashed into one file instead of being separated into modules introduced in lua 5.1

The folders structure could be simply as it is in other processing repos (ref: libprocessing)

We don't really export any tables, everything we do is global. So I imagine all the smaller components going into an L5 folder, and the top level L5.lua file would look something like:

  require("l5.color")
  require("l5.shape")
  require("l5.typography")
  ...

The current L5.lua already has section headers. Those section headers are basically our future modules:

• runtime
• input/events
• transform
• shape
• color
• rendering
• vertex
• math
• typography
• system
• media/loading

This is the safest refactor as of yet, but in the future I think it makes sense to have a segregation between the internals like local state/functions and the global public APIs like size.

[Nitish-bot]

This would be a big refactor and could break things, I also noticed we don't have any tests. I will try to research other processing libraries to see how they test and open an issue on it soon. That should be a priority before this one.

[lee2sman]

Thanks for the suggestion and looking into this. One other consideration is the added complexity of a build process. Ideally, if breaking into modules we can make this as simple as possible.

[Nitish-bot]

There is no build process with seperating the code into modules, unless you meant testing which is surely going to add to the complexity but making the code more resilient to breaking is worth the cost in any case.