Hi, today I use my innovation time to check possible improvements for UI. After yesterday discussion I start with checking at first what we already have - libyui ruby bindings. It is just thin layer on top of libyui, but it is already there. As starting point I do two things that we can use to start discussion:
1. fix libyui-bindings to provide usable rpm ( do not create project yet in OBS ) - simply run `rake osc:build` to get rpm that you can install.[1] 2. try to port one real dialog. I pick very simple one because I do not want to face layers built on top of UI module and also because I expect obstacles.[2] So how it ends? libyui-bindings looks working for me in ncurses. In qt I am getting segfaults and also for examples in libyui-bindings itself. From a quick view it looks like for me again some pain with a way how we destruct objects. It need probably some expert view why it segfaulting as I do not see anything obvious using gdb or valgrind. Adapted dialog in yast2-cio ( you can try it yourself if you use manual_run directory and do some symlinking to bin as with recent secure change to drop custom PATH it does not longer works out of box ) looks reasonable simple for me. Only bigger code is for replace widget which is implemented in ycp-ui-bindings and is non-trivial operation. Maybe something to backport to libyui itself? So if you are interested please see both pull requests and try to use it yourself. And if there is qt expert, then checking why ruby bindings segfault would be useful. Josef [1] https://github.com/libyui/libyui-bindings/pull/32 [2] https://github.com/yast/yast-cio/pull/34 -- To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org To contact the owner, e-mail: yast-devel+ow...@opensuse.org
