I'm working on a Cocoa GUI for FUSE (currently called MacFusion).
The idea is that it loads plugins for supported filesystems (working right now on SSHFS, NTFS-3G and FTPFS at first).
The plugins provide a configuration interface and code to mount/unmount. I'm hoping that this GUI will make FUSE goodness easily accessible to non-technical non-console people. In the future, it should be simple to support encfs, gmailfs, etc.
This will be a FOSS project once a first build is ready.
Anyone who wants to help is welcome, as are suggestions of any kind on the features/interface.
While i see that KDE seems to have a different perspective than gnome in terms of desktop environments, I think in the long term the linux community needs to look to unify the two. I think that having two widgets toolkits, two architectures, two "worlds" on the desktop is a fundamental problem to the adoption of linux as a commonly used desktop environment... even for people who i consider power users. Why does the same thing always need to be coded twice for gnome and then for kde? Is kwrite not identical to gedit? Does gnome settings not have many of the same tools as control center? I think that developer hours need to be used effectively by the linux community and code duplication like this should be eliminated.
Slashdot Mirror
I'm working on a Cocoa GUI for FUSE (currently called MacFusion). The idea is that it loads plugins for supported filesystems (working right now on SSHFS, NTFS-3G and FTPFS at first). The plugins provide a configuration interface and code to mount/unmount. I'm hoping that this GUI will make FUSE goodness easily accessible to non-technical non-console people. In the future, it should be simple to support encfs, gmailfs, etc. This will be a FOSS project once a first build is ready. Anyone who wants to help is welcome, as are suggestions of any kind on the features/interface.
While i see that KDE seems to have a different perspective than gnome in terms of desktop environments, I think in the long term the linux community needs to look to unify the two. I think that having two widgets toolkits, two architectures, two "worlds" on the desktop is a fundamental problem to the adoption of linux as a commonly used desktop environment ... even for people who i consider power users. Why does the same thing always need to be coded twice for gnome and then for kde? Is kwrite not identical to gedit? Does gnome settings not have many of the same tools as control center? I think that developer hours need to be used effectively by the linux community and code duplication like this should be eliminated.