Gwenview is a fast and easy to use image viewer/browser for KDE. All common image formats are supported. Standard features include slideshow, full screen view, image thumbnails, drag'n'drop, image zoom, and full network transparency using the KIO framework. It also provides image and directory KParts components for use in applications such as Konqueror. Additional features are provided by the KIPI image framework.
A folder hierarchy suggestion
IMHO, final users (=parents) shouldn't have to build
applications, but they should be able to install
binary packages. These packages should be easy
to install and uninstall without getting the system
filled with unused files from previous installs.
Furthermore, the "curious-but-not-geek" user
should be able to find everything (doc,
binaries,data) about an application easily.
I like the idea of application folders but don't want
to bloat the PATH variable. Therefore I suggest a
folder hierarchy like this :
"/apps" would be filled with symlinks to
"/app_files/<app_folder>/bin" for easy access from
bash. This would avoid PATH variable bloating as
"/apps" would be the only folder in it.
"/libs" would do quite the same, but for libraries.
Libraries can be seen as "apps' apps" : the user
execute code in apps to perform something, apps
in turn execute code from libraries, which might
execute code from other libraries...
With such a structure, you would easily know
where everything about an app is and manual
uninstallation would be as simple as "rm
/app_files/<app_folder>", then running a script to
remove broken symlinks from "/apps".
Note that I don't address devel packages in this
hierarchy, but it must be possible to find a similar