Dne 25. 09. 18 v 11:13 Stefan Hundhammer napsal(a):
Should we decide to drop that completely, we will have to come up with an alternative which in all likelyhood will work in a very similar way; the UI interpreter needs some container classes for transporting the UI terms from the application layer (no matter if it's YCP, Ruby, Perl or Python) to the UI C++ classes.
There are Ruby bindings for libyui [1], but IMHO that would be too low level. There was a hackweek project about using a specific UI DSL [2] with slim-like [3] template support. This would be a better approach IMHO.
Having said that, I don't believe those YCPValue-related classes will go away in the forseeable future.
Yes, just like with the Ruby-YCP code. We are slowly replacing that with the native Ruby but some parts will never be touched and stay like that forever (or until dropped from the distro). Ladislav [1] https://github.com/libyui/libyui-bindings [2] https://github.com/libyui/ruby-ui [3] http://slim-lang.com/ -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org