Duncan Mac-Vicar Prett wrote:
On Friday 27 April 2007 10:06:23 Lukas Ocilka wrote:
feature problems: - Ruby / Python or even Perl doesn't provide so much controllability as YCP does. It rarely happens that YaST is killed by some exception that is not handled properly, it's mainly because YCP has a very good syntax checker and doesn't allow you to make mistakes. If only I could say that about web-scripting languages :( How often an 'Internal Server Error' happens if you think that everything goes smooth?
Why not Wt, Wt is C++ and has the same classes as Qt.
- Stylesheets (CSS) si the problematic part of almost all web-browsers (almost all, because some of them just don't support CSS at all). Actually you can't find two web-browsers that would support CSS the same way as another one does. That's why using CSS might become rather a disadvantage. Yes, I know, that's life and we have to deal with it, CSS are cool :)
That is handled in part by the toolkit.
Yes, of course, Wt library used just as another optional UI (additionally to Qt/ncurses/GTK+) might work, but dropping all YaST and replacing it with something else doesn't make any sense. By the way, even when using that library, we would/will have to deal with more security problems than we do now. Web is very insecure by default. I wasn't talking about CSS from the toolkit/server side but from the client side - a browser. Every single browser handles CSS differently, some of them even don't support CSS at all. -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic