Quote Originally Posted by probono
You do not understand what klik is.
klik is _not_ an installer. Its philosophy is = "1 app = 1 file".
cmg files do not need to be "installed", and that is their biggest advantage.
Just think of them like mp3 files, you don't "install" those either in oder to use them, do you?
No, we understand this. Currently there is server-size package manager which do all the job, but please forgive me, i can`t believe what this is possible to live without introducing client-size helper -- some sort of package manager in other terms. Someone need to take care of new .cmg files (make in known to system) and deleted .cmg files (remove all traces of it from system). By the way, corresponding code in .zAppRun does not work for me, don`t know why yet.

Quote Originally Posted by probono
As for the "macros", what do you think a klik recipe is? What you describe is already there.
They are programs If there will be something more intelectual on client site than currently used sh, it can cause problems because it is neary impossible to know what job this script designed for without running it. On the other side, i do not argue for using something like xml recipes which should be parsed and executed by rich client-side package manager (yet)

P.S. Right now i was tried to get some klik recipe to look at it closer, but klik.atekon.de become an unknown host!

P.P.S. Many peoples, including me see similarity between klik and Java Web Start technologies. What do you think about it?