#Nizar’s amazing layout library

32 messages · Page 1 of 1 (latest)

burnt fulcrum
#

Star me pls there is a lot of work to be done still

#

The todolist also includes cascading styles and string style parsing

#

Dyamic rendering and dynamic states with signals and event handlers

#

And many more

flat stirrup
burnt fulcrum
#

i added a flexbox

#

this is the rendering of the flexbox using the raylib renderer backend

#

i also added a slab allocator for dynamic allocations of ui nodes

#

next step: dynamic rendering, signals, event handlers, and cascading styles

hard steppe
#

if its just a layout library why does it come with a buttload of notlayoutisms?

#

strange commit history too

burnt fulcrum
#

The layout logic is decoupled from the rest of the logic

#

Meaning it can be used in various contexts

burnt fulcrum
#

its kind of like clay, its a layout library in its core, but also provides some backends out of the box which is what i plan to do

hard steppe
burnt fulcrum
burnt fulcrum
#

alright

#

i added event listeners for current available elements

#

moved the raylib backend in include/backends

#

added examples

#

added dynamic rendering

#

the todolist currently:

  • string ids that map id to ui element
  • cascading styles
  • text wrapping
  • margin computation
  • sizing based on parent percentage
  • add more components
  • parsing styles from string .
hard steppe
#

whats the difference between css support and cascading stylesheets?

burnt fulcrum
#

wait i typed it correctly

#

yes so implementing the cascading styles on the ui elements themselves where setting display_font property would actually affect all tree

hard steppe
#

css == cascading style sheet

#

so redundant things on your list

burnt fulcrum