Sorry, this post is slightly OT, since I defend the general idea of AppDirs here.

user unknown, please look at the general architecture of klik on http://klik.berlios.de/architecture/ - klik does all of that today already. The only thing I propose is that KDE should have a way to start the wrapper automatically when the AppDir is clicked.

Quote Originally Posted by user unknown
The last time I used a Mac is more than 10 years ago, and I never owned a Mac myself. So I don't know to much of its inner technics.
A lot has changed since then, the Mac OS is now Unix.

Quote Originally Posted by user unknown
When resources (?) are installed with the application in a folder, how are multiple users handled?
AppDirs allow users to install apps in userspace. But you could of course also install them to /opt, making them available system-wide.

Quote Originally Posted by user unknown
What's about shared resources, like libxml, libjpeg, ...?
The common ones stay where they are. The less common ones go into the AppDir of the application that needs them. That way each app can have its own matching version of libraries without the danger of messing the whole system. /dev/modem is a systemwide thing, but libtiniweeny-0.6.so not (since not many apps use it).

Quote Originally Posted by user unknown
Will the data be stored in the same folder?
The data that belongs to the app: yes (such as help pages, icons etc), userdata: no (goes still to ~)

Quote Originally Posted by user unknown
Can the technic handle multiple versions like 3.14-stable, 4.0-beta?
Yes!

Quote Originally Posted by user unknown
When I run a program, I call its name - no need for browsing and clicking.
You could still do this, but you are not the average point-and-klik user.

Quote Originally Posted by user unknown
I never use konqueror to start an application.
You don't have to, but I would like to. As a fluxbox user, you are completely unaffected by the progresses in KDE