Linked by Thom Holwerda on Wed 14th Feb 2007 18:49 UTC, submitted by Dolores Parker
Thread beginning with comment 213014
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Well, I wouldn't say it's completely different...Klik's cmg may be seen as a file, but it's really a compressed image that is mounted with cramfs, at which point it is treated as a folder.
Remember, in *nix everything is a file. A folder is a file, and a compressed image is a file that becomes a folder once mounted.
So, yeah, I wasn't being really accurate when I said it was "more or less" what they did in OSX, but I wasn't totally off either. The principle is the same, even though it's handled differently. I have to say I do prefer the Klik way, myself.






Member since:
2005-07-07
a) Isin't that more or less what OSX does with foo.app?
Yes.
No!
Approach is completely different.
On Apple .app is a folder not file. On klik it is really just one file.
Apple just hides everything under .app and shows it as it would be one file only (if you don't believe just start terminal and go into app folder your self), while klik mounts application file as loop device on execution and then executes contents.
Apple approach has been used in ROX for ages.
p.s. I'm not sayng that Apple approach is bad, it is just not possible on linux. There is just too many different vfs-fm approaches and one can't expect that every last one would support it. Klik goes around that, because it provides common execution and also provides support for a lot of fm out there.