On 4/27/07, Benji Weber <b.weber@warwick.ac.uk> wrote:
On 4/27/07, cies <cies.breijs@gmail.com> wrote:
it already became a problem when suse got some strong gnome forces on board. toolkits are a religious discussion; i agree. ;) yast is a more kde'ish app that stands bad in a gnome environment (true).
so yast is a problem, and ZEN* is apparently not the solution. so now suse tries to go 'community' with yast.
No, yast is a development platform, the modules developed on it can be displayed using any of the available toolkits without modification. Currently this includes Qt, Ncurses, and GTK+.
i didnt know about GTK+... i have the (unfounded) believe that is might be due to yeast supporting so many backends that it is a little user-unfriendly. but i dont know this for sure -- and maybe with some fixes (on all the back ends) it might end up very user friendly ;) with user-unfriendly i mean: many dialogs, many popups, no search, help function is not very integrated with the tool, little or no use of wizards (which would help out a lot)
the problem is old: the desktop linux user community needs a standard way configure their computer (the configuration/ system settings windows on other OSes). and preferably we also want console access (besides the GUI) to some of the features (like y as).
We have ncurses widget set for yast2, it is also possible to expose functionality of yast modules to a true command line interface.
i know and knew and think this is a very important feature.
the solution can be new: why not do the configuring from a webpage (that at the same time has a command line interface)?
We could in theory have a web-widget set for YaST, which would give web access, whether this happens depends whether anyone is interested enough to do it I suppose. iirc a web widget set for YaST using Wt was even suggested as a SoC project.
i still think a solution with web/command-line i'faces only would be less hassle and can end up more polished that yast.
reasons why: - no gnome/kde/whatever dilemma
This doesn't exist at present, yast is toolkit independent.
why are the GTK-only replacements for yast funtionality then? and why have these replacements been pushed so hard (i think i can say against the will many users)
Please realise how great and extensible the YaST platform already is.
i did (suse pre 10 dayse), but then (suse post 10 days) i started to dislike it. anyway, you gave me a bit more hope for yast in its current shape. thanks!
p.p.s: did i mention that it might also be a good moment to drop RPM in favor of DEB? (this might even create a strong cooperations between suse and the debian/ubuntu/etc.)
LOL
yep, funny. still i have much better overall experience with DEB, an i truly wonder: why? it seems so much faster, and more clever... maybe my perception is a little distorted. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org