On Tue, 23 Feb 2021 11:21:35 +0100 Ancor Gonzalez Sosa <[email protected]> wrote:
> On 2/23/21 10:08 AM, José Iván López González wrote: > > On 2/22/21 4:14 PM, Ancor Gonzalez Sosa wrote: > >> [...] > >> > >> That leaves us only with the option discussed on TL;DR, which implements > >> a custom button labeled "Help" that opens a simple regular pop-up to > >> display the help text (eg. no searching box). For that, it uses the > >> commodity method Yast::Wizard.ShowHelp, which does simply that - opening > >> a regular pop-up (not based on QY2HelpDialog) to display some text. That > >> ShowHelp method is not connected to the default mechanism of the > >> standard "Help" buttons. It's only executed if called explicitly and > >> only displays the passed text. It's used seldomly to create custom > >> additional "Help" buttons (eg. in a pop-up that is not really part of > >> the Wizard). > > > > Yes, we also faced that problem when implementing such help in the > > Services Manager. Maybe this is a good time to open the door to a new > > CWM widget to manage the help? > > Not CWM, please. > > In fact, the Yast2::Popup module would already serve as a good starting > point. Its approach is quite valid and there is quite some logic that > could be shared with an hypothetical Yast2::HelpPopup. We can do it in fact other way round and use that new HelpPopup in CWM to show help. Josef > > Just if we want to go that road, which is not still clear to me. > > >> I was kind of tempted to test the Services Manager approach in order to > >> add limited hyperlinks support for the Partitioner help... but I'm not > >> convinced it's worth it. > >> > >> Still, the investigation was interesting and I'm writing my findings > >> here for my future self. > > > > Thanks for sharing it! > > It was unfair to keep all the fun for myself. > > Cheers.
