> several that aren't available that I'm
> ending up having to build from scratch.
Yes, I do that a bit, but we need a better
way to 'capture' and preserve that work
so that others can enjoy the same...
For a very long time I have been wanting
a better way to make simple 'recipes' for
those scattered applications.
I tried using
gentoo.org for a while, thinking
'ebuild' was exactly what I needed.
But after too much struggle, I finally gave-
up on that amazing but difficult distro.
Wow, that is extensive. I'm very far behind ;)
> Am currently running Openbox rather than IceWM
I've settled on IceWM for the (maybe silly
to some) reason that I know how to assign
the 'Windows' key to open the 'Start' menu.
I want to make a desktop that competes in
performance against Windows XP, and want
the keyboard shortcuts to do what the user
expects if they have used Windows before.
A longer-term goal that I have thought about
for quite a while, but do not have any code
for is "Install And Launch When Attempted".
The high-level view of IALWA is a Start-Menu
filled with all the applications you could ever
possibly install, but not yet actually installed.
There would be no separate package-manager
because the Start-Menu seamlessly manages
packages and launches those same programs.
Each entry might be slightly greyed-out if the
app is not yet installed.
I envision the icons, reviews, screenshots,
and other heavy data could be retrieved over
the network (and cached) when the user
pauses over that menu entry.
Once the user tries to use that program, the
package-manager would be invoked to install
that package and any dependencies, and then
the program would be launched, and the menu
entry would be updated to show it is installed.
Right-clicking the menu-entry would allow the
user to uninstall or configure or complain about
bugs or suggest new features, or go to an
online forum, etc.
The window-manager should also be enhanced
to add another button (maybe a '+') that would
be another way to access the features given
when right-clicking the menu-entry.
A global configuration file would contain settings
such as "prompt before install", "uninstall app
after X days of disuse", "sort menu entries
by popularity", etc.
Patrick Anderson
http://SocialSufficiencyCoalition.BlogSpot.com