On Thursday, 29 December 2016 at 22:53:51 UTC, Chris Wright wrote:
On Thu, 29 Dec 2016 21:41:45 +0000, aberba wrote:
Styling is similar to CSS but different. Wished someone would
just go for a full blown CSS parser. CSS has proven its more
capable and loved for client side styling/decoration.
CSS is huge. It also brings in some assumptions about the
layout model.
Supporting a subset of CSS would be reasonable.
This, besides there are things in CSS that only makes sense for
it and not necessary for this. Like the way it certain styles are
depending on each other, the dependencies may act differently by
CSS, than it would by my library, because I do not render things
with the same mindset or goal as CSS. One thing that especially
is hard is the selector scheme as it's not based on styling a
marked up language nor any kind of language structure at all. So
the same kind of hierarchy doesn't exist with selectors like a
div with a div isn't a thing, it's just a container that has a
child component that's a container, but since this targets native
GUI development then I don't want styling to match such
inheritance and each component should be decoupled from each
other. I believe it's much smoother and easier to manage your
design. The only things that won't be decoupled from components
and their children and surroundings would be things like
positions, margins, paddings etc. all which doesn't affect the
design.
