Slashdot Mirror

← Back to Stories (view on slashdot.org)

How To Deal With The Spatial Paradigm

Posted by timothy on from the tradedja-for-a-paratwenties dept.

PostThis writes that there's been "a lot of talk about Gnome's spatial Nautilus lately and so Christian Paratschek puts everything into perspective weighing in the pros and cons of this particular user interface paradigm. In any case, there are always alternatives."

2 of 38 comments (clear)

  1. The better question.... by Creepy+Crawler · · Score: 0, Offtopic

    Is how NOT to deal with SPatial paradigm..

    Apple's Quicktime is a great (horrible) example.

    http://homepage.mac.com/bradster/iarchitect/qtim e. htm

    Care of the "Interface Hall of Shame"

    --
  2. Re:The only mistake by embobo · · Score: 0, Offtopic

    Gconf + NFS = less hair.

    Solution: use Redhat's hack to put the gconf lock in /tmp. Result: race condition. Whoever writes to the config preference file last wins. Yay. User logs into computer A. Logs into another--B--, makes config changes on B, logs out of B, logs out of A, and then the changes are gone. Thanks.

    Solution two: run the gconfds on the NFS server, set "ORBIIOPIPv4=1" in /etc/orbitrc for all clients. Seems to work OK. Hope that doesn't FUBAR security. Wait, the NFS server runs Redhat 7.3 (and thus gconf-1). What about those new workstations that run RHEL3 (gconf-2)? They're fucked. "Just upgrade gconf-1 to gconf-2 on the file server," you say. After all, the GNOME developers say that gconf-2 handles gconf-1 clients transparently. (Interlude: descend into dependency hell to get gconf-2 installed--in a maintainable way--on a Redhat 7.3 box.) Oh, wait, gconf-2 doesn't actually handle gconf-1 clients properly. Thanks.