Quote Originally Posted by dmiceman
Quote Originally Posted by sheldonl
However, it seems that some recipies are not without their problems. For some reason some programs don't work properly. e.g. ksirc doesn't save my preferences or anything. I think that the IO Slave is of much more utility if a recipe is *not* a shell script, but a series of MACRO actions that are interpreted into actual actions on the file system by the daemon. These MACRO's could be defined by plugins to the daemon (service) and be written in shell, perl, python, c, c++ etc. I could probably use the plugin and MACRO code from lineakd to do this but it's a pretty large undertaking, it involves completely standardizing, codifying and reingineering the klik system. However, then each distribution can write macros that are specific to them and you don't have to put platform specific code into the the recipie.
That is bring up another question: how much infrastructure should be on target computer when it trying to handle klik: link. If recipe will be macro, then there should be some sort of package manager installed already on computer which can process incoming recipe into instructions like: get this file, register some mime type handler, etc, etc.. That is not bad, but it is more difficult task. And it is require much more specifications, definitions, etc..
Of course, it is more work, but consider what would happen if we use kommander scripts as MACROs that can be leveraged within recipies for KDE applications. We could very well have nice installers/uninstallers for applications.