Closed magland closed 4 months ago
If I’m reading this correctly it sounds like an alternative to #23 and #24, correct?
I think I would prefer using css classes that live outside the code files for as much as possible. Obviously if we need a computed value like a width we’re feeding in from the outside that may be a different story
If I’m reading this correctly it sounds like an alternative to #23 and #24, correct?
I think I would prefer using css classes that live outside the code files for as much as possible. Obviously if we need a computed value like a width we’re feeding in from the outside that may be a different story
Right now, css is not possible for handling positioning (left, top, width, height); in the future this could eventually change if we are able to do an overhaul. And I feel like yScroll belongs in the .tsx files because that's integral to the functioning and not really a style. But I could see the case for backgroundColor being in a .css file. What I'm proposing is a simplification of the existing system... and those other issues would still remain open.
I think #135 resolved the same issues in a different way
Since we are at a good point for sweeping through the codebase and making changes, I wanted to propose the following for simplifying all the absolute positioning and styling of divs throughout. This doesn't preclude doing a further overhaul down the road, but this should tidy things up a bit.
Put a "Div" component, in the components/ folder defined like this
Then for example
Would become
and
would become