1 Aug 2004 01:02
KAdmin
Frans Englich <frans.englich <at> telia.com>
2004-07-31 23:02:01 GMT
2004-07-31 23:02:01 GMT
For long buzzed about is KAdmin, similar to KControl but does only contain server administration functionality(which KControl have in addition to user preferences), and has KParts as content instead of KCModules. KAdmin would have kernel configuration, boot manager, "pseudo modules" linking to web admin interfaces, kuser, KIOSK(no, that's nothing you need as a regular user) -- all integrated under one roof. KAdmin would typically be installed on servers only. Why is KAdmin needed and what problems does it solve? * Administration software is more than simple configuration options -- it's a working area. Some understandable needs toolbars, menus and so forth, and have tried implementing it in KCModules(QWidget) and it doesn't work -- it's like squeezing an elephant through a key hole. Administration functionality needs the flexibility KParts offers; a widget in a dialog is insufficient. * It is hard to design a KControl when it has such a wide role and demands on flexibility and expandability. When administration functionality is taken care of elsewhere, its scope is narrow, and designing the content(categories etc.) and representation(the GUI) gets easier. KControl can become a simple application for user preferences. * As noted above, administration stuff lives between KCModule and standalone apps -- the former to small, the latter usually overkill. KAdmin would reduce the number of entries in the KMenu, group related together and bring consistency -- like KControl. A unified way of handling root permissions, and less code.(Continue reading)
RSS Feed