On Mon, 2002-11-11 at 22:08, Ethan Benson wrote:
> On Mon, Nov 11, 2002 at 09:55:23PM +1000, Ben Martin wrote:
> > Basically its for multi desktop management.
> > eg. I have ~/.ego/desktopN/ which has a bunch of symlinks for desktop N
> > and a few special fake files for running raw scheme code. I may wish to
> > represent /tmp in two views, one with a small icon on the right hand
> > side of the screen just for convenience and on another desktop I might
> > want /tmp with a 64x64 icon and be more prominent on the screen at top
> > left. So as my code stands right now I store
> > user.ferris-icon-name
> > user.ferris-icon-x
> > user.ferris-icon-y
> > as EA on the object itself, be it a file/dir/symlink. This way the
> > symlinks can have different icons and locations.
> this is somewhat off-topic, but are you really sure EAs are the best
> place for this kind of info? please consider that UNIX is a multi
> user OS, in shared directories this method of storage will fall down
> as the various users accessing the data will either clobber each
> other's preferences for icon placement, or be annoyed by other users
> choices (it all depends on the permissions of the files/dirs).
Well, to solve multi user its easy to use
Of the usual suspects ie:
* efm style, using a .efm-meta file in the directory
* out of line ~/.myapp/icondata.db
* filename mirroring, fileX has a .fileX.meta
* GConf style
I chose to go with using EA for this because its easy to have multi apps
using the same data and IMHO its easier to administer because copy/move
can preserve metadata easier.
> Ethan Benson
In this world there are only two tragedies.
One is not getting what one wants,
and the other is getting it.
-- Oscar Wilde