Hi Cies, As stated, Yast is modular, so that would be an addition, not a replacement. Btw, is remote system administration useful? I mean, it would only be good for a subset of the modules. But I guess it could open doors to diagnostic tools, and be really helpful to help someone on the site. On the concerns, according to their features pages, it seems Wt has been tested on all major browsers, and it can communicate through HTTPS. With regard to authentication, I think that's work for the server side framework we would need to work on anyway. One possible problem is the layout. According to them, Wt differs from your usual toolkit and operates more similar to CSS here; obviously, we can't have YUI doing the layout for us. Like, yast-gtk we can do the layout on the interface, but even for yast-gtk containers had to be implemented to shape the thing to fit both sides; we need to see if this would be doable for Wt. I think that just honoring the relative positioning of the widget would be good enough; relative stretching would just be a bonus. About ditching YCP for Python, yeah, I would like to see that. ;) Cheers, Ricardo Sex, 2007-04-27 às 05:20 +0200, cies escreveu:
(i'm afraid this mail might get quite long)
i just get home from a party, and read an announcement that yast is now 'community'. the party was good though.
well..
i loved suse, but not anymore. mainly because of yast. to me a distro is 3 things: - a good package manage system - an integrated product - some sane defaults everywhere
suse from 10 onward was (imho) lacking all. yast basically didn't change; it also was not very 'community'.
now there is the *ubuntu family that kind of save all of us by being the cool debian, and all of a sudden yast is not longer a 'strategic advantage' but a large disadvantage.
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.
and i think that is the logical next thing to do.
i think novell understands that people will not write the core of their distro for them. so some investment is needed.
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).
the solution can be new: why not do the configuring from a webpage (that at the same time has a command line interface)?
reasons why: - no gnome/kde/whatever dilemma - today with AJAX we can make very good looking interfaces. - webpages are easier to 'fix' (usability wise) - more people can help - ...
features: - plugin based - written in ruby (or python) ((biased? who, me?)) - stylesheets can be used for theme creation - a command line interface (new to the locally served web page) - runs on gecko/khtml (with the accompanying javascript engines) - put in a specially crafted browser, to look very clean - ...
strategic: - try to cooperate with other distributions - share the development - seek cooperation with openusability.org - uniformize linux configuration -- users benefit - novell shows that it is really interested in the community as a whole (sorry guys, you kind-of let the free software community -- besides your own userbase -- down by signing that MS deal: you could have know) - ...
conclusion: obvious to me: re-write.
please think big!
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org