From: Christian Kreibich <kreibich@in...> - 2001-11-18 20:31:46
"Carsten Haitzler (The Rasterman)" wrote:
> On Sun, 18 Nov 2001 00:57:02 -0600 Corey Donohoe <cdonohoe@...> babbled
> > Wouldn't this be better to store in efsd meta data, or in a db itself.
> > Didn't it work with metadata at some point before?
> e17 still does this - problem is there is no way to get a message / event that
> metadata changed at the moment - there is for files in a dir. so u can still use
> the metadata to set the path to a bg.db
Mhmm I thought we had agreed on having background definitions in
separate dbs for ease of moving them around etc, and when we have
libebg. So I think what should be implemented is this:
* No metadata entry /view/background?
No problem, use system-wide background by setting.
* User wants to set background in a view
This case depends on whether or not a background will be set with an
external tool or by e17 itself. In the former case, efsd needs a
mechanism to monitor metadata keys, or e17 will notice the new
background only next time a directory is viewed. In the latter, e17 can
handle that fine by itself, just set the /view/background key to the new
db, and switch the background. Next time you come to that view, the
metadata entry is set, and there you go. Notice that the value of
/view/background currently is only queried, never set.
In any case, e17 should monitor the currently used background file,
because that might change also without changing its location and thus
the /view/background value.
I'll see what I can do about the metadata monitoring, but I cannot make
any guarantees on when I'll have time to implement anything at the
moment. I'd say give me about a week.
Get latest updates about Open Source Projects, Conferences and News.