Except that if you want to write an app to switch themes its now going to have to check theme keys to determine if whats in the directory returned in the theme path is actually a theme or if its a background.
If there separate you can just return the theme path along with the background path when they call bg-list then a theme program knows that everything in the theme paths are themes. Otherwise, some of them could be background. Just seems like the wrong way to do it. dan On Mon, 2005-05-16 at 07:53 +0800, Stafford Horne wrote: > Dan, > > I understand that they could be separate, and that bg directories may > not contain any themes. But if they need to be separate then the > background path should not be hard coded. I did this on the assumption > that theme dirs can be background dirs. If you add a path to the theme > directory you will want to have programs, such as emblem, look for bgs > in that directory. This way there is no need to double the paths, as the > theme dirs in most cases are a subset of the bg dirs. > > If we want to have another path for backgrounds it should be > configurable and stored in e_config. This is pretty easy to do, but I > really see no need as the theme directory already serves a similar > purpose. > > Stafford > > On Sun, 2005-05-15 at 11:35 -0400, dan sinclair wrote: > > A background dir isn't a theme dir tho. > > > > dan > > > > On Sun, 2005-05-15 at 15:05 +0800, Stafford Horne wrote: > > > Hello, > > > > > > I have done some work on exporting all of the paths through IPC. > > > > > > These are the current paths. > > > E_Path *path_data = NULL; > > > E_Path *path_images = NULL; > > > E_Path *path_fonts = NULL; > > > E_Path *path_themes = NULL; > > > E_Path *path_init = NULL; > > > E_Path *path_icons = NULL; > > > E_Path *path_modules = NULL; > > > > > > Implementation: > > > The search path is now implemented by using two evas lists, one for > > > hardcoded directories and one for user directories. The user > > > directories are stored in e_config and can be manipulated through IPC > > > (enlightenment_remote). The user directory of an E_Path is a reference > > > to the path in e_config and should be associated while initializing a > > > new E_Path. > > > > > > example commands: > > > > > > -theme-dirs-list > > > -theme-dirs-remove <OP> > > > -theme-dirs-append <OP> > > > -theme-dirs-prepend <OP> > > > > > > [EMAIL PROTECTED] bin]$ enlightenment_remote -display :0.0 > > > -theme-dirs-list > > > REPLY: BEGIN > > > REPLY: THEME DIR="/home/shorne/.e/e/themes" > > > REPLY: THEME DIR="/home/shorne/.e/e/backgrounds" > > > REPLY: THEME DIR="/home/shorne/local/share/enlightenment/data/themes" > > > REPLY: END > > > > > > [EMAIL PROTECTED] bin]$ enlightenment_remote -display :0.0 > > > -theme-dirs-append > > > ~/misc/Pictures/ > > > [EMAIL PROTECTED] bin]$ enlightenment_remote -display :0.0 > > > -theme-dirs-list > > > REPLY: BEGIN > > > REPLY: THEME DIR="/home/shorne/.e/e/themes" > > > REPLY: THEME DIR="/home/shorne/.e/e/backgrounds" > > > REPLY: THEME DIR="/home/shorne/local/share/enlightenment/data/themes" > > > REPLY: THEME DIR="/home/shorne/misc/Pictures/" > > > REPLY: END > > > > > > > > > Notes: > > > I have gotten rid of the -bg-dirs-list, the background dirs are now part > > > of the theme dirs. The good thing is this does not break libe things > > > like emblem. > > > > > > Stafford > > > > > ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
