myDSL Extensions (deprecated) :: Extension loading order



ooohh...so it's that particular filename (I'm guessing...i don't have dsl running at the moment) which is skipped intentionally? Very cool.
I purposely designed it that way so that the user's backup.tar.gz has final say on his system.
As it should, of course!  However, shouldn't a .tar.gz extension be able to modify the default behavior of a subsequently loaded .dsl module, at least in theory?

I'm trying to accomplish the same thing that almostX-theme.tar.gz does to fluxbox when auto-loaded from the root.  The problem most likely did not occur with fluxbox, since it is already exists when .tar.gz files are loaded.  I can do the same thing with xmms, which pre-exists, but not with icewm, mplayer or xine which are .dsl modules.  :(

I'm guessing that's why icewm-blue includes icewm again instead of being just the theme.
Quote
However, shouldn't a .tar.gz extension be able to modify the default behavior of a subsequently loaded .dsl module, at least in theory?

i dont think so. extensions should be build as standalones with reasonable default.
i think its a clear patern.
1. load all the extensions
2. then use backup.tar.gz to adjust the default to your need



Quote
I'm guessing that's why icewm-blue includes icewm again instead of being just the theme.

it is very well posible to create a theme.dsl for icewm withouth including the whole icewm again. i think the icewm-blue.dsl is more of a snapshot form the builders desktop.
i just tied two options.
1. created a theme.tar.gz from my /home/dsl/.icewm/themes and have i loaded at boottime before icewm.dsl is loaded
this can be a *.tar.gz as it writes in /home

2. created a theme (1in1-xp.dsl) from /usr/share/icewm/themes and have i loaded at boottime before icewm.dsl is loaded (just because for the alphabetic order)
this must be a *.dsl as it writes in /usr
There will always be more than one way to skin a cat, but this is beside the point.

Quote
1. created a theme.tar.gz from my /home/dsl/.icewm/themes and have i loaded at boottime before icewm.dsl is loaded
this can be a *.tar.gz as it writes in /home


Yes, but try to  make it the new default theme for icewm (without using restore) like almostX for fluxbox does.  Anything can be set as default using restore, but then your backup.tar.gz is dependant on certain extension modules being loaded.  I have found that this can have other unforseen consequences so I don't use it at all... yet. :)

Quote
2. created a theme (1in1-xp.dsl) from /usr/share/icewm/themes and have i loaded at boottime before icewm.dsl is loaded (just because for the alphabetic order)
this must be a *.dsl as it writes in /usr


Thanks, this illustrates the problem pretty well.  According to the IceWM documentation (IceWM Manual) this is improper.  A user's personal add-on themes belong in $HOME/.icewm/themes whereas only the default built-in themes should be found in /usr/share/icewm/themes OR /usr/local/share/icewm/themes.  I had to move some of the ones I'm working with to $HOME/.icewm so I was aware that not everyone "plays by the rules."  But breaking the rules in this way can make your theme incompatible with later versions of IceWM and/or other themes.

In essence, this is the problem, just in reverse.  The default settings in icewm.dsl were placed in $HOME/.icewm, instead of /usr/share/icewm where they belong.  If moved, and the .dsl is rebuilt, everything will work as it should.  I have personally verified this only with icewm-blue at this point, still need to test the base version.

Again, thanks for the feedback!  Hopefully, you're helping me to clarify the issue as I see it.
Next Page...
original here.