ruby-ui was a hackweek project with jreidinger to make libyui (YaST text/graphical engine) usable from pure-ruby without going through YCP.

We experimented a bit extreme trying to make the usage of SLIM templates possible. It kind of worked.

You could figure the best API and make it ready so that YaST can use it

https://github.com/dmacvicar/ruby-ui

Examples: https://github.com/dmacvicar/ruby-ui/tree/master/examples

Looking for hackers with the skills:

yast ruby c libyui

This project is part of:

Hack Week 11

Activity

  • almost 11 years ago: mvidner liked this project.
  • almost 11 years ago: dmacvicar added keyword "yast" to this project.
  • almost 11 years ago: dmacvicar added keyword "ruby" to this project.
  • almost 11 years ago: dmacvicar added keyword "c" to this project.
  • almost 11 years ago: dmacvicar added keyword "libyui" to this project.
  • almost 11 years ago: dmacvicar originated this project.

  • Comments

    • jreidinger
      almost 11 years ago by jreidinger | Reply

      I think it is better to link upstream project (https://github.com/libyui/ruby-ui) then own fork ;)

    Similar Projects

    pudc - A PID 1 process that barks to the internet by mssola

    Description

    As a fun exercise in order to dig deeper into the Linux kernel, its interfaces, the RISC-V architecture, and all the dragons in between; I'm building a blog site cooked like this:

    • The backend is written in a mixture of C and RISC-V assembly.
    • The backend is actually PID1 (for real, not within a container).
    • We poll and parse incoming HTTP requests ourselves.
    • The frontend is a mere HTML page with htmx.

    The project is meant to be Linux-specific, so I'm going to use io_uring, pidfs, namespaces, and Linux-specific features in order to drive all of this.

    I'm open for suggestions and so on, but this is meant to be a solo project, as this is more of a learning exercise for me than anything else.

    Goals

    • Have a better understanding of different Linux features from user space down to the kernel internals.
    • Most importantly: have fun.

    Resources