PixelPAD Vision and key factors driving direction
Getting Started Quickly
Any unnecessary steps that do not contribute to learning was abstracted. This means users can immediately run their project without spending time setting up their environment.
The Start and Loops being separated on PixelPAD is because of this key point.
The first iteration of PixelPAD had the start and loop as separate methods, requiring users
to create their own classes that inherit the start and loop.
It also required users to have knowledge of Python indentation syntax, class creation syntax, and inheritance. All of this before the user got started.
So this was extracted away, and presented the start and loop into separate sections, allowing users to have an immediate impact using one line of code!
Power users can still make use of creating their own classes and inheriting from PixelPAD's super class if they wanted. This is done like this: