On Fri, 24 Jul 2020 14:55:50 +0200 Ancor Gonzalez Sosa <ancor@suse.de> wrote: Hi Ancor, thanks for meeting minutes, I found that always very useful.
One idea regarding the previous point: define widgets once and then get TUI + GUI + Whatever widgets that you can customize further: Abstract Factory -> Backend-specific Factory -> Backend-specific widget
Another idea in the same line: compared to libYU, it should be easier to redefine how some things work in a particular widget compared to its "base widget".
One more idea I have. Something like gem2rpm or kind of how swig works. Define universal code ( description of UI ) and then have specialized code and as result it will generate code in target UI framework. It should work without specialized part. Advantage of this way: 1. you can easily write in target language like in swig 2. it ensure that basic UI looks same as widgets are generated from same base. 3. backend stuff should be done on universal part and query for widget result. So all fancy specialized features just helps with manipulation, but should not affect final result.
3.3 Other Topics
The meeting often drifted to other more or less related topics:
- Colaboration with manatools https://github.com/manatools/python-manatools
- The lack of separation of UI and "business logic" in YaST in general, which maybe is currently perceived by many YaST Team members as the most limiting factor to any UI-related discussion, beyond the UI framework itself.
What I miss and maybe something we should do for next meetings is plan how to move forward for next meeting.
Cheers.
Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org