On 12/9/20 4:56 PM, josef Reidinger wrote: > 1. have auto wrapping just for Yast2::Popup and has Yast::Popup just as > deprecated legacy class. And if bug report appear about long unreadable line, > just use newer API. > > 2. Remove stretches from Yast::Popup. It can possible break layout somewhere > and probably openQA would need to be adopted. > > 3. similar to 2. just instead of adapting layout, use from Yast::Popup calls > to Yast2::Popup and keep it just as legacy backward compatible layer. > > As there is a plan to do some changes that affects openqa in January, I think > that deadline to the end of December is good enough. My preferred solution is > 1 as it basically start converging to one API.
I would probably prefer #3 as... - We expect openQA changes anyway - Deprecated classes usually live forever anyway - #1 can start and never finish JM2cents Lukas -- Lukas Ocilka, Systems Mgmt & Consulting Team Leader & YaST Product Owner SLE Department, SUSE Linux I don't know everything I don't know _______________________________________________ YaST Development mailing list -- [email protected] To unsubscribe, email [email protected] List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/[email protected]
