1.0: Finalize module split for basic definitions about picotui HOT 6 CLOSED

Picotui caters to be suitable for MicroPython too, so that may affect module split too. MicroPython would favor smaller modules, to let applications import only what they really need. But I'm not sure it would make a difference here, because almost every app would import both colors and keys. What would make a difference for MicroPython is splitting each widget class from widgets.py into own module, but that's too detailed, and I didn't really want to got that way, that's why I put all common widgets to a single module.

from picotui.

I almost decided on defs.py .

from picotui.

I almost decided on defs.py .

Now implemented in d0601ac & a3f56b5 .

Now in 0.10 there will be somewhat breaking change that these definitions won't leak thru screen.py, etc., and need to be imported explicitly.

from picotui.

Mostly addressed in 1.0.

from picotui.

These may require adjusting imports in applications, so adding "breaking changes" label and reopening to serve as a reference.

from picotui.

reopening to serve as a reference.

After 2 years, closing.

from picotui.