What | Removed | Added |
---|---|---|
CC | shundhammer@suse.com |
IMHO the most robust approach would be to create a minimalistic UI component class derived from YUIComponent and use that one in the RSpec case. It doesn't need to do much, but it has to comply with the requirements of those UI components, such as providing a UI plugin (a shared lib) that can be loaded with dlopen(). Maybe a few shortcuts are possible to avoid writing a full-blown UI. We'll need to research that. Back then, this YUIComponent magic was introduced to integrate with the Y2ComponentBroker that managed the YaST2 components in the YCP world. We might not need all of that, but - unless we want to rewrite major parts completely - we'll have to fulfil at least the minimal parts of those call protocols.