* Johannes Meixner <jsmeix@suse.de> [Jun 20. 2013 10:52]:
Regardless how it will be implemented, what you say is basically:
Even after YCP was replaced by Ruby in YaST, arbitrary contributors cannot just do Ruby programming as usual to contribute something to YaST.
Exactly. You still cannot use 'puts' or 'printf' to output a string to the UI, you need UI-specific calls. And the backend is no difference. Where I agree with you, is the need to explain to contributors the reason behind this decision.
Therefore I like to have it discussed here in advance if it is possible to drop the whole idea behind SCR.
And replace it by what ? Ruby printf to write (arbitrarily complex) config files ? The idea behind SCR was to provide a simple API hiding the complexity of config files from the programmer. I strongly believe this idea is still valid. Klaus -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org