On 3/16/21 11:57 PM, David Benjamin wrote: > As an outsider I wanted to create a YaST module to edit the config.txt > file used on a Raspberry Pi. But first I have learn how to get YaST to > just display a screen, and it turns out there are several options, but I > still don't know when to use things like wizards. I then have to learn > all the different widgets, and what about UI Shortcuts, they're just > wizards right?! Wait, should I be using CWM?
Yes, we have a mess of related but different technologies. And looks like most people fail to find the tutorial at[1] that explain exactly how to get YaST to just display a screen with some widgets. That tutorial should help. Still, it shows the basic technology but does not cover other possibilities like using CWM (which personally I'm not a big fan of) or creating a Firstboot client/dialog. > The questions go on and on. It would be nice to have a WYSYWIG > environment so I don't have to learn all of the intricacies of the YaST > UI. In my opinion this is a huge barrier for casual contributors. I > could be missing something here but drawing a dialog box in YaST is not > trivial. A full WYSIWYG editor would not solve that problem, in my opinion. If you still have to decide whether you want to just write a simple dialog like the one explained in the tutorial, or you want to use CWM (which implies a different approach to UI) or deal with wizards... I don't see how such tool would help in that. What we need is a simplified stack and better documentation with examples that is easy to find. It's amazing how often people claim there is no tutorial to start YaST development from scratch while the tutorial has been online and linked from the YaST homepage for years (it may be slightly outdated by now, but it's certainly there). Cheers [1] https://ancorgs.github.io/yast-journalctl-tutorial/ -- Ancor González Sosa YaST Team at SUSE Software Solutions
