Shape path creation #8
Labels
Improvement: Enhancement
New feature or request
Improvement: Feature
Requests a new feature
Improvement: Optimisation
Performance or accessibility improvement
Currently, the library's render methods follow the following instructions:
This is great for quick rendering as it means the user does not need to deal with managing paths, but it causes serious decreases in performance once the number of objects exceeds a trivial number.
Instead, the library should offer two functions per shape: one function for creating the desired path, and another for creating and rendering the path automatically. For example, rather than having just a
evgRect(...)
function, we should have aevgMakeRect(...)
andevgRect(...)
function, where the latter function simply calls the former, renders the path, and destroys it.The text was updated successfully, but these errors were encountered: