Linked by Thom Holwerda on Mon 5th May 2008 21:00 UTC
Thread beginning with comment 313140
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-09-17
How about making a "configuration" the user interface object the user interacts with, rather than a "program"? So you add, run, and remove a particular configuration of a program, rather than the program itself.
e.g. I add a "configuration" of Firefox ("Firefox 3 + loads of plugins") to my desktop. It's like an AppDir, except it contains the settings, plus a link to the program.
If I want to add another one (e.g. "Firefox 2 with no plugins" for, say, on-line banking) then I add one of those too. I now have two icons / menu entries in my GUI, one for each configuration.
Deleting a configuration loses its settings, which therefore no longer need to be hidden.
Programs themselves can be installed and garbage collected automatically. No need to bother the user about that. Shared libraries, dependency hell, multiple versions, automatic updates, non-root install, etc are easily solved for most software (http://0install.net, as others have mentioned already).