Kim Gr�sman wrote:
Hi Monty,
Nice!
It'd be cool if we could put them in a submenu called Skins or Themes, so
it's more obvious what they do.
Yeah I need to work on that.
Also, it shouldn't be too difficult to make the change permanent by copyingYeah I changed the routine to this -
and renaming files.
function loadcssfile (cssfilename)
{
var install_dir = DQSDLauncher.InstallationDirectory;
link = document.getElementsByTagName( "link" )[ 1 ];
link.href = install_dir+'\\'+cssfilename;
var cssContent=readFile(install_dir+'\\'+cssfilename);
writeFile(install_dir+'\\localsearch.css', cssContent);
}
It works, but this has the negative effect of over-writing the users localsearch.css file.. If they had any custom css styles in it, they would be lost.. I cant over-write search.css because it has many settings the toolbar needs that is not in the localsearch_xxx.css files.. Should we go the route of loading an intermediate css file - search.css, theme.css and then localsearch.css ? Is this necessary? Is anybody making custom css changes? I have been copying the theme css file to localsearch.css and running as-is.., but I dont know if this is what everyone does..
Monty
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel
