Charles Whittington

An alternative would be to leave widget properties essentially as they are, but give a value source the ability to link to and modify any arbitrary attribute of any object,...

> If you instead linked a Slider to a TextInput, it would be unclear whether the type of the value was a number or a string. I guess this would...

> Secondly, the introduction of a Container is effectively a "breakpoint" in layout calculations - the container gets a size as a part of the layout it's a part of;...

> That was my initial thought... but I'll completely defer to someone actually looking at the code :-) Point taken. 😄 Initial vibe check accomplished, I'll report back if/when I...

I've been looking into this (and #2928), and I've noticed an inconsistency. Remember that `_IMPL_NAME` property I stuck on widget classes in my first pass on widget initialization in #2942,...

> Agreed - my initial impression would be that using the `_create()` approach from #2942 would at least be consistent. Sounds reasonable. Even if things ultimately become something different, at...

> A single installable package is easy to set up and explain, but complicates the process of defining and installing dependencies. Multiple installable packages (mirroring the Toga repo setup) is...

This seems highly relevant to #2938.

+1, as I'm running up against what I think is an example of this... although I've only just started using Lektor (and Jinja, for that matter), so it's possible that...

> If you want to indent the rendered HTML without escaping the tags, try (also untested) `{{ item.description | string | indent(4) | safe }}`. I'm unsure what the point...