[dev] theme support in other apps

[Eric Rostetter]

Quoting Jan Schneider <jan@horde.org>:

> Btw, application specific themes work as soon as you add a theme directory
> on the application's config directory.

I find this to be true in most cases.  But sometimes it just doesn't work
with a particular page of an app.  Like in nag, when I put my theme files
in and go to the page, then the page shows my theme colors.  But the
javascript code to change the colors when the mouse passes over them doesn't
work unless I add code to the list.php file in nag.  I'm not sure if this
is intended behaviour or not, but it is the demonstrated behaviour.  In
some apps (kronolith) I simply need to add a theme file.  In others (nag)
I need to add code...

> It just doesn't make sense to add
> this directory to every application unless the actually is a theme file in
> it as it would be pruned by cvs -P anyway.

Yes, but otherwise I create my own outside of cvs, and then get to watch
cvs "complain" about it all the time (update, diff, etc).  And then I have
to convince others using my module that it is really okay to create this
directory, here's how, etc...

Maybe we can toss a README file or something in there to keep it from
being pruned, *if* we want to precreate them.

Now that kronolith and nag support my theme, I'm not so worried... ;) So
I'm willing to be more flexible now ;)

> Jan.

-- 
Eric Rostetter
The Department of Physics
The University of Texas at Austin

"TAD (Technology Attachment Disorder) is an unshakable, impractical devotion
to a brand, platform, product line, or programming language. It's relatively
harmless among the rank and file, but when management is afflicted the damage
can be measured in dollars. It's also contagious -- someone with sufficient
political clout can infect an entire organization."

--"Enterprise Strategies" columnist Tom Yager.