On Fri, 23 Nov, 2007 at 18:06:22 -0800, Robert Smits wrote:
On Friday 23 November 2007 03:17:40 Thomas Goettlicher wrote:
Hi everyone,
we want to redesign the YaST Control Center. Therefore we are looking for a radical new design.
This is your chance to share your ideas regarding YaST Control Center.
Please feel free to contribute with mockups and (unconventional) ideas here: http://en.opensuse.org/YaST/Development/New_Control_Center
Hi, Thomas. Thanks for asking us about what we'd like to see.
Indeed, thanks for that.
All I really want is for YAST to be faster, especially at downloading updates from repositories. And why does it have to download a whole new list if I used it earlier in the day?
Agreed.
I'm not convinced I WANT a radical new design. I don't, as a rule, care all that much for change for change's sake, but if you give me a better Yast, I'll learn it.
Me too, though 'better' *is* kind of a subjective experience I guess :)
In other subthreads there are discussions on a variety of aspects. My take
on a couple of them:
[architecture]
I agree that a server/client sort of thing might be nice. There was some
discussion about ssh -X vs. NX and 'going https://'
To me the speed of ssh vs. NX seems irrelevant. If we're talking about
server/client - then the traffic would mainly consist of 'control-messages'
anyway, right?
server> "here are the options"
client> "do this"
server> "ok"
vs:
server> "bitmap bitmap bitmap"
client> "mouse click on coordinates such and such"
server> "pixel pixel pixel"
So what's needed is a networked YaST *protocol*, encapsulated in strong
encryption, rather than a way of transporting a locally generated gui
somewhere else (or rather; a remotely generated gui transported to 'here').
https:// ?
please don't:
Next thing you know it, I'm going to need javascript or mono or something,
in order to administrate remote boxes...