Hi Monty, > guilty as charged.... heeheeheee.....
Well - I made a VERY rudimentary 'themeinst' search that allows you to remotely install a theme in much the same fashion as 'httpinst' (in fact, it's based on httpinst). Many thanks to Kim for providing the code to work from. :) Anyway here's themeinst: http://reliableanswers.com/x/dqsd/themeinst.xml You can install the 'spiffy' theme by using: themeinst http://reliableanswers.com/x/dqsd/spiffy.xml PLEASE allow me to WARN YOU IN ADVANCE that the CSS changes were like a ten second change just to see if the themeinst search itself worked. I DO NOT consider myself to be one of those 'interface geeks' either, so it's not pretty, just a demonstration of what CAN be done. There isn't currently a way to 'revert' to the original style, but the original search.css *IS* backed up as backup.css - and getting back to the 'real' style is as simple as renaming it back to search.css I was really just trying to get something together for Monty to play with. :) So - download the themeinst.xml file (you can use httpinst to install it) and then look at the source for spiffy.xml It's pretty straightforward: <?xml version="1.0" ?> <theme> <name>Spiffy</name> <author>Shawn K. Hall</author> <resource file="search.css" url="http://reliableanswers.com/x/dqsd/search.css" /> <resource file="searchme.gif" url="http://reliableanswers.com/img/searchme.gif" /> </theme> Description: <name> does absolutely NOTHING at this point, but could be used later on to present a list of themes to the user or generate the theme folder and stuff. <author> does pretty much the same. In fact, the only thing that has any bearing at all at this point are the <resource> tags, which each have two attributes: url : the url of the file to download file : the filename to be used locally for the file (it WILL be stored under dqsd\themes\%themename%\ ) %themename% is the xml file name without the ".xml" portion. At least, for now. A <resource> MUST exist that is named 'search.css' otherwise it will obliterate the existing search.css and not replace it with anything. This is VERY ugly and can make using DQSD rather difficult. Anyway...I'd like to make quite a bit more out of this, but it's a good start I think. A lot of mods still need to be done, and it needs to be able to load themes that are already installed, too. I'm going to bed now, though. Maybe someone else will want to play with it? Thinking it over now, perhaps we should create a 'theme.css' file at the root of the dqsd folder that is initially empty. It will be overwritten by the theme that is installed, and the last line of the search.css file can be an import rule for the theme.css file. This way you only need to include the css mods in the theme that you want different from the defaults and since it *is* CSS the last-noted changes (iow, theme.css) will take precedence. On a related note, this type of thing could be used to install searches in addition to the graphics for the themes. I'm seriously considering revamping my floax search (which I now use about 1 in 5 times I use DQSD) so that it can be a 'theme' by default. I just realized I never actually published the floax search. Geez, how'd that happen? Oh well - maybe tomorrow. I'm tired. Regards, Shawn K. Hall http://ReliableAnswers.com/ '// ======================================================== 24 x 7 availability, 5 days a week! ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ DQSD-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-devel
