raylib: base widget class

[sshane]

continuation of #35483, goal is to make rl ui more static, less one-off pattern decisions I see around the UI

[sshane]

@deanlee do you like render or draw better?

[deanlee]

@sshane I'm not entirely sure — it's honestly a bit inconsistent right now. Generally, I use render when the function involves not just drawing but also handling input like mouse events or other logic. For purely visual output, I tend to use draw. there might be a better naming convention we can adopt.

[sshane]

There can be update and draw/render. For now, keeping both combined might be the simplest

[sshane]

BTW something like handle_mouse_release we can put in the base class.

Sidebar does this:

def render():
  self._handle_mouse_release()

and settings does this, not consistent:

def render():
  if rl.is_mouse_button_released(rl.MouseButton.MOUSE_BUTTON_LEFT):
    self.handle_mouse_release(rl.get_mouse_position())

[deanlee]

Nice design. Actually, the only window we still need to implement is the Pair Device popup—everything else is pretty much done. So maybe there's no need to rush into switching to a virtual function–based approach just yet.

[deanlee]

@sshane: Would it be possible to merge #35446 and #35437 soon? Development is moving quickly, and constantly resolving conflicts is becoming a bit of a headache.