Andrew Sayman wrote:
>
> [I'm not really sure where I should have posted this, so any help
> pointing me to a better place is appreciated]
The .xpfe newsgroup would be a good place, since this is really a design
problem.
> I'm an active mozilla user and I constantly download nightlies and
> milestones. I've run into a problem with downloading skins/chromes.
> Mozilla always searches for skins inside of its own directory tree.
The add-on skins you're using were written to install to the global
location, but Mozilla could handle it either way. Skins from Netscape's
"Theme Park" install into your profile -- it's all up to the skin creator.
> When I have multiple builds of mozilla and something like ActiveState's
> Komodo builds that don't have the skin in it's subdirectories won't
> load. I couldn't get Komodo working for a few days before I realized it
> was searching for a skin I'd installed on a nightly.
Switching between two Mozilla builds, or Mozilla and Netscape 6 could have
the same problem.
> A simple solution to this issue would be to use multiple profiles, but
> I'd prefer not to do that.
If we can't find the user's chosen skin (or locale) we should probably fall
back on the global default skin (or locale). I just created bug 65530 since
I couldn't find another bug on the issue, although it seems like a known
problem.
> It seems like there should be a way to have a skin directory
> seperate from any mozilla build subdirectories. Possibly in the profile
> subdirectories.
It's already possible for skins to be installed in the user profile, but
most skin authors have not chosen this approach. I don't know why,
installing chrome into the user's profile solves several problems including
this one.
-Dan Veditz
