What about cross application configuration?
It would be great if it would be possible to find a generic logical model for all configuration information of an application.
e.g. it should be possible to import existing apache configuration data, enable "exec cgi scripts" for "/myhomepage", and write the data back; and - oh, I dont like apache any more, I would like to switch to any other supported webserver and keep my configuration information. Ok, not every webserver supports the same features, but it should use all supported features.
Mozilla Crossplatform Desktop
I think one problem is that most tries of bringing
Linux to the desktop
result in writing programs (e.g. KDE/Gnome/almost
anything) that might be
good/better and different than the windows
programs. The enduser has to
learn how to do the same things different.
Why don't go the other way: Provide an easy-to-use
for some open problems in the windows world.
I'm thinking of a Mozilla based crossplatform
The user gets a CDROM which
-provides the basic applications to work (Mozilla,
and some other Mozilla-based tools - sorry, no
KDE, no Gnome!)
-can run without installation via Windows autoplay
-can run without installation by booting Linux
from CDROM using Plug'n'Play
-can run without installation from an existing
Linux user account
-can be easily installed under Windows
-can be easily installed into an user account
-can easily install Linux as dualboot option
(also on a fat32 partition for unexperienced
users; system parts in an ext2fs image)
-provides good user profile (and data/mail)
syncronisation options via
network/floppy/zipdisk so that the unexperienced
user can work easily on
any computer in his common working environment
-provides some Windows compatibility under Linux
Couldn't this be a way for Linux to find new
friends? They first work
with the Windows part, and 20 bluescreens later
they try the Linux part
and find a high performance operating system which
is easy to administrate
(of course using the Mozilla GUI)!
Waiting for comments.